My Map is Ruined! After Months of work!

For some reason unknown. Every time I try to test or even run my new map it crashes like at 80% loaded and I receive an error. This just started today. I tried re-saving the map but still no luck. This is horrible! I spent so much time on this map...it cant be ruined.

please help!

heres a pic of the error.



THIS HAS BEEN SOLVED. I JUST CHANGED THE NO PATHING.

If you have a loading screen enabled, disable it.

That exact thing happened to me.

Another thing that might cause it is corrupted (or basically unliked) unit data, which also happened until I fixed some random field on some random unit.

i have the same problem i have no clue why mines does
and i gave up on it so if anyone wants it

another problem is regions that are only 1 line high or wide and buildings with not pathing map.

Check for any Infinite loops that is what did it for me of if you have a building with no patching texture

thats it!

Thank you so much!

NP glad to help :)

Hello

What if you need an infinite loop for the game? How can I make it work with the loop?

you should never ever need an infinite loop!

if you need something to happen all the time, just use Periodic Event - 2 Seconds or something.

So every 2 seconds the trigger fires, (or make it 0.5 whatever..)

just infinite loops just end up taking all the memory there is, especially if you use an integer thats is filled up every loop.
Ie Round = Round + 1 :P
then round will we infinite and take all memory and warcraft wont know what to do, and crash.

Yea to help solve your problem you could email me your map at [email protected] and i'll see if there are other solutions to your problem.

there is no infanite loop. wc3 will autostop at 1024 loop index (which also happens to be the max array size...)

That may be true but the loop still lasts long enough to crash the game because i've had it happen many times before. So wether it be infiniite or not is irrelvant

Having unbelievably fast increments.. .01 times.. still might mimic a loop and suck all the memory up.

looping to 1024 does not crash the game. I have made exitwhen errors that made a loop go though the full 1024 and it never crashed, although it did freeze for about 2 seconds

There are many factors that fall to play with this

1) Your computer
2)what it does constantly
3)if you use make the trigger infinite or you just tell it to run 1024 times

All these things may change the results making it sometimes crash and sometimes not.