so that means i need to set for every casting unit (here tornado) a point and for every special effect define a point to keep leaks small or what?
that would suck
It means that whenever you use a pointer (a variable that "points" to other variables, for example - a location points to two coordinates of x,y), you will have to destroy it later on UNLESS it points to values that will never change.
For example, pointing to a player is fine without destroying it, because player 1 will always be player 1.
Now, since we said a point (location) variable is a pointer, you will need to destroy it each time you use it.
When you use "
Position of(...)" , "Random
point ...", you actually MAKE a point (location) VALUE.
This means that you just made a pointer, without ANY way to ever touch it, which means that if the x,y of it changes, the pointer will stay there and the game engine will create a new one.
This is why you must make a variable for each pointer you use - so you can destroy it when it is not needed.
About your specific question - in GUI most people make two points. One at the unit's location, and one with Polar distance from it (that "x distance, y angle, from ---).
To destroy it, you use the custom script "call RemoveLocation(udg_LocationName)". Notice that this is case sensitive ("s" isn't "S" for example).
You must use that "udg" before any global variable you make (via the variable editor). A space is a downline "_", not " ".
And if you think this sucks, you might as well not do anything that was written here. Just don't wonder if no one will play your map because it would lag.
Actions
Special effect - Create a special effect at (Random point in (Region centered at (Position of tornado) with size (1500.00, 1500.00))) using Abilities\Spells\Human\ThunderClap\ThunderClapCaster.mdl
Set tornado = (Casting unit)
