- Joined
- Jan 28, 2009
- Messages
- 442
This is not about the program crashing.
I use a couple arrays in a map. One called TilePoint (a point array) and one called TileValue (an integer array). Their sizes are now both set to 1681; because that's the maximum number of "tiles" I use (imaginary squares of size 128 x 128). TilePoint refers to the center of each tile, while TileValue is a value I assign to each tile, which can range from -2 to (Range). Range is used by many triggers in the map to calculate the number of tiles we are currently operating with.
The heaviest trigger in my map is a loop, in a loop, in a loop, in a loop, in a looping trigger, set to run until a variable becomes >= Range.
With this trigger, I run into a problem I can't solve. The trigger itself works perfectly, until I try to set Range (integer) to 18+. Then it won't get to the end of the trigger. A game message is supposed to report how many times the trigger has looped afterwards, and the textMessage doesn't show when Range >= 18.
I'm not going to write the whole trigger here because of its length
Why does it stop responding when I set a certain integer to 18 or higher? Is it some kind of limit that makes WC3 simply ignore the functions? Earlier the maximum were 6, now, after a bit of rewriting, it's 17. It's weird...
Is it simply because tons of conditions and actions being repeated referring to different locations and all, say about 6000 times in the trigger, is too heavy? Rep if you know what's causing this prob
I use a couple arrays in a map. One called TilePoint (a point array) and one called TileValue (an integer array). Their sizes are now both set to 1681; because that's the maximum number of "tiles" I use (imaginary squares of size 128 x 128). TilePoint refers to the center of each tile, while TileValue is a value I assign to each tile, which can range from -2 to (Range). Range is used by many triggers in the map to calculate the number of tiles we are currently operating with.
The heaviest trigger in my map is a loop, in a loop, in a loop, in a loop, in a looping trigger, set to run until a variable becomes >= Range.
With this trigger, I run into a problem I can't solve. The trigger itself works perfectly, until I try to set Range (integer) to 18+. Then it won't get to the end of the trigger. A game message is supposed to report how many times the trigger has looped afterwards, and the textMessage doesn't show when Range >= 18.
I'm not going to write the whole trigger here because of its length
Why does it stop responding when I set a certain integer to 18 or higher? Is it some kind of limit that makes WC3 simply ignore the functions? Earlier the maximum were 6, now, after a bit of rewriting, it's 17. It's weird...
Is it simply because tons of conditions and actions being repeated referring to different locations and all, say about 6000 times in the trigger, is too heavy? Rep if you know what's causing this prob