[Trigger] Differences with/without variables

[sPy]

Solved

So, I was wondering..What is the difference is set variable in a trigger and not setting it. here's what I meant:

• Events
  • Unit - A unit dies
• Conditions
• Actions
  • Set TheUnit = Triggering Unit
  • Unit - Kill TheUnit

• Events
  • Unit - A unit dies
  • Conditions
  • Actions
    • Unit - Kill Triggering Unit

I don't think any of them leaks...But I'm not sure whether it affects gameplay perfomance..So, what do you guys think the differences between these two?

 

[GhostThruster]

There is none. Variables should only be used when you reference the stored data later on, or when you are removing leaks.

 

[Sadalbari]

If you use (triggering unit) many times in your trigger then using a variable will be faster.
If you use (wait) action, you must use triggering unit after the wait action because if the trigger runs again, your variable might be overwritten.

 

[Bribe]

Don't use Triggering Unit or Attacking Unit after the wait action. Those can bug because if the same event happens again, the internal-game variables are reset and you get hosed. Better learn some multi-instanciable tactics.

 

[GhostThruster]

If you add waits, the best way is to use local variables, it is explained in one of the tutorials.

 

[Super-Sheep]

Triggering unit is the fastest and for a some unknown reason triggering unit is also a local variable.

 

[Sadalbari]

Don't use Triggering Unit or Attacking Unit after the wait action. Those can bug because if the same event happens again, the internal-game variables are reset and you get hosed. Better learn some multi-instanciable tactics.

That's not true.

 

[sephiroth1234]

Don't use Triggering Unit or Attacking Unit after the wait action. Those can bug because if the same event happens again, the internal-game variables are reset and you get hosed. Better learn some multi-instanciable tactics.

Yep, that is not true. The 'Triggering Unit' cannot be overwritten like local variables do.

 

[Bribe]

I had a guy on these forums who was running a loop and after just a few iterations of the loop (not enough to crash the thread), the Triggering Unit was returning null. Changing Triggering Unit to a simple local variable fixed the problem and it never happened again.

 

[GhostThruster]

Which circles back to this.