K
Kevin
Guest
So I have a new question about stopping leaks.
A lot of my triggers reference the same exact point.
i.e.: center of Region A.
If I start adding a bunch of leak removal code (some of which won't be used), it'll make my map bigger.
What if I just make an map initialization trigger that pre-stores these centers of regions into global variables.
Then when I reference these centers of regions, I instead reference the variable.
That prevents the leakage right? Because the point being referenced is always going to be the same point and that's stored in the variable.
Also, same thing with special effects. Is it possible to store a special effect in a variable, then, call to function that variable to show the special and making it so it doesn't leak?!
A lot of my triggers reference the same exact point.
i.e.: center of Region A.
If I start adding a bunch of leak removal code (some of which won't be used), it'll make my map bigger.
What if I just make an map initialization trigger that pre-stores these centers of regions into global variables.
Then when I reference these centers of regions, I instead reference the variable.
That prevents the leakage right? Because the point being referenced is always going to be the same point and that's stored in the variable.
Also, same thing with special effects. Is it possible to store a special effect in a variable, then, call to function that variable to show the special and making it so it doesn't leak?!