Moderator
M
Moderator
12th Dec 2015
IcemanBo: For long time as NeedsFix. Rejected.
08:40, 1st Jun 2011
Maker:
You should separate the visibility actions from the hashtable creation trigger since they're not part of the spell.
You don't have to use custom script for getting the handle. I'd prefer the GUI way since the spell is done with GUI. But you can leave it as it is.
For Powerslash you could use the handle integer also.
You can abuse Powerslash if you hit stop immediately after casting it, no mana cost or cooldown. You might have to change the event to Starts the effect...
You could store the ability level into hashtable and load it when dealing the damage.
You could use triggering unit instead of casting unit.
Instead of having several values in the or condition, you could have a real value that runs from 0.36 to 0 and check whether it is < 0. Or use an integer for even faster performance.
Leaks a region:
IcemanBo: For long time as NeedsFix. Rejected.
08:40, 1st Jun 2011
Maker:
You should separate the visibility actions from the hashtable creation trigger since they're not part of the spell.
You don't have to use custom script for getting the handle. I'd prefer the GUI way since the spell is done with GUI. But you can leave it as it is.
For Powerslash you could use the handle integer also.
You can abuse Powerslash if you hit stop immediately after casting it, no mana cost or cooldown. You might have to change the event to Starts the effect...
You could store the ability level into hashtable and load it when dealing the damage.
You could use triggering unit instead of casting unit.
Instead of having several values in the or condition, you could have a real value that runs from 0.36 to 0 and check whether it is < 0. Or use an integer for even faster performance.
Leaks a region:
- Set Temp_Loc_2 = (Random point in (Region centered at Temp_Loc_1 with size (320.00, 320.00)))