Well, my map leaks... (godamnit!)and it's impossible to figure out why (been months searching it).
When I test my map I push it very hard when compared to the actual game I intend ppl to play.
My map is a footman frenzy-like with 12 player and lots of units...
So I make sure that there is always at least 700 alive units in the map when testing it.
And so, I run the leaky trigger that handles with all units in the map 10x faster than in the normal gameplay.
I'd say that in one hour the trigger runs 240 times, and deals with units 168.000 times.
After 4 hours of game running, the game crashes because of the "not enough memory" problem...
By the way, at normal game speed, the leaky trigger would run 24 times...
The questions are:
So, can I conclude that it will be safe for ppl playing it without wasting effort of some hours of gameplay?
If this just happens after 4 hours of intensive trigger processing, do you think it's possible that is just a normal leak that's within "Warcraft 3" itself and not my programming?
thx for reply...
When I test my map I push it very hard when compared to the actual game I intend ppl to play.
My map is a footman frenzy-like with 12 player and lots of units...
So I make sure that there is always at least 700 alive units in the map when testing it.
And so, I run the leaky trigger that handles with all units in the map 10x faster than in the normal gameplay.
I'd say that in one hour the trigger runs 240 times, and deals with units 168.000 times.
After 4 hours of game running, the game crashes because of the "not enough memory" problem...
By the way, at normal game speed, the leaky trigger would run 24 times...
The questions are:
So, can I conclude that it will be safe for ppl playing it without wasting effort of some hours of gameplay?
If this just happens after 4 hours of intensive trigger processing, do you think it's possible that is just a normal leak that's within "Warcraft 3" itself and not my programming?
thx for reply...