- Joined
- Mar 19, 2008
- Messages
- 3,141
One of reasons that Integer A sucks (sorry, thats truth):
- it's default war3 global integer variable and if used within loops and differend functions can cause bugs, or ruin given instance.
Why? Because if you do so, functions share the same global, changing it's value dynamicaly thus, given loops/whatever can end/mess instances that it is currently executing, or cause other wierd things that shouldn't have happened. It's esspecialy unsave if you want to make MUI spells - one index change - ruins whole spell.
- it's default war3 global integer variable and if used within loops and differend functions can cause bugs, or ruin given instance.
Why? Because if you do so, functions share the same global, changing it's value dynamicaly thus, given loops/whatever can end/mess instances that it is currently executing, or cause other wierd things that shouldn't have happened. It's esspecialy unsave if you want to make MUI spells - one index change - ruins whole spell.