• Listen to a special audio message from Bill Roper to the Hive Workshop community (Bill is a former Vice President of Blizzard Entertainment, Producer, Designer, Musician, Voice Actor) 🔗Click here to hear his message!
  • Read Evilhog's interview with Gregory Alper, the original composer of the music for WarCraft: Orcs & Humans 🔗Click here to read the full interview.

TempPoint Overuse?

Status
Not open for further replies.
Level 16
Joined
Mar 27, 2011
Messages
1,349
I have a variable in my map named "TempPoint" which is a point type variable. For nearly all my triggers, I use TempPoint. Since my map has been receiving random fatal errors, I wondered if its because a variable shouldn't be used so frequently, or even if a rare event happened that 2 triggers utilized the "TempPoint" at the same time by sheer chance?

Note: I never put a wait in between setting the variable and nulling the variable.
 
Level 19
Joined
Aug 8, 2007
Messages
2,765
no, it shouldnt.

just remember dont null it, remove it

set udg_TempPoint = null != call RemoveLocation(udg_TempPoint)
 

Dr Super Good

Spell Reviewer
Level 64
Joined
Jan 18, 2005
Messages
27,258
or even if a rare event happened that 2 triggers utilized the "TempPoint" at the same time by sheer chance?
As WarCraft III's Jass interpreter is single threaded this is physically not possible. Even if it was the case you could solve it by locking the WarCraft III process to a single thread using task manager.

If anything it is better to use a variable as much as possible as it will make more efficient use of the processor cache but the speed gains are minimal compared with the slow speed of JASS.
 
Status
Not open for further replies.
Top