Same or Separate Variables for Map Triggered Abilities?

[Dristitia]

If you guys make a defend map. do you guy make variables for every single abilities? like Skill HEAVY SLAP = HeavySlapCaster,HeavySlapTarget or it just Caster, Target,... ?

 

[claptomanic]

depends

if its an istant ability i use TempVARS because spell specific VARS are not needed.... if it not i use spell specific VARS.

 

[nedio95]

Only if it isn't instant (like uses loops or waits or is split on 2 or more triggers)
Otherwise use TempAbility, TempUnit, TempPoint etc. etc.

Edit// claptomanic was faster And its not only for defense maps but overal.

 

[Dristitia]

thank

 

[WaterKnight]

Local and scope variables of course.

 

[Dristitia]

Btw, What if i make a trigger like this

Unit - A Unit starts the effect of an ablities

Set - Casting Unit = TempUnit
If Level of ability (Dummy Unit) Equal 1
Then
Remove TempUnit
Else
Do nothing

 

[nedio95]

Edit//Deleted

Looks ok

 

[claptomanic]

no! it doesnt look good...

1. dont use casting unit use triggering unit.
2. remove the 'do nothing'

 

[nedio95]

Ah yes my whrong was thinking only generaly...

 

[Dr Super Good]

The correct programming approach is to use locals with names appropiate to their function. As JASS is useless junk though...

I recall that it was discovered that globals were faster than locals. This means that in theory it would be best if a precompiler were to automaticly replace local variables with "shared" or "static" globals where appropiate.

 

[baassee]

Local and scope variables of course.

This.