If it did, you may find the map's contents in a folder of the same name located where the map usually is saved.
If not, you can try and repair the map's mpq somehow, try making a copy and then removing the doodads/destructable data since it kind of likes to get corrupted by itself.
I use 10.5.4 because my computer's dead and I'm using a borrowed laptop.
And I don't know how to use Time Machine, either.
Quote:
Originally Posted by Vexorian
Did it crash while saving?
If it did, you may find the map's contents in a folder of the same name located where the map usually is saved.
If not, you can try and repair the map's mpq somehow, try making a copy and then removing the doodads/destructable data since it kind of likes to get corrupted by itself.
It saved normally, let everything through... even when I pressed the "test map button" everything went through.
I used MPQ2K, the war3map.j was jumbled...
However that second idea is genius, my map crashed 50 times through the process of production and I have those all over the place (mostly in trash but not deleted).
To repair from as recently as possible, should I delete the corrupted war3map.j and replace it with a recent one?
I forgot to mention it was crashing on triggers' load (I'm really not sure if it can crash anywhere else, seeing as my WE crashes every 30 seconds... almost.)
EDIT!
For now I'll just try cutting out the war3map.j and importing it in without anything fancy.
EDIT!
Fanciful and wonderful news! I'll form it into a tutorial later. What you do to fix this problem:
1. Find the "temp folder xxxxxxx" with all the jumbled letters, odds are all the files there are not the most recent but they are safe
2. Get an MPQ editor and open up your corrupted map
3. Delete the war3map.j and the war3map.wtg inside the corrupted map
4. Import the war3map.j and war3map.wtg from the temp folder into your corrupted map
5. PROFIT!
EDIT!
6. Warning: The trigger that causes problems will crash your World Editor upon selection (happened running Mac OS X, 10.5.2 (apparently not 10.5.4))
Poor bastard. That happened to me once. The key is saving every few minutes, after you make a change to the map you don't want to have to rewrite or make again.
Now whenever I do something foolish and crash the editor, I am just a few minutes away from starting again where I left off.
If you save too often then your triggers will no longer work.
I've found this out on MY OWN MAPS!!
The triggers just don't work! They show up but not work!
