Help please!!! *grovels*

I have no idea how this managed to happen, but a map I've been working on for 4 months now compiles with 1437 errors since this morning's compilation. The only two things I did was add music to the map, and edit 1 trigger to say the same thing it said before but just to double-check it. Every time I compile it says each individual trigger has errors (all of which worked yesterday) with 141 - 153 errors appiece, for a total of 1437 or thereabouts. Anyone know how to fix this? PLEASE let me know. Thanks


Soulcutter

Ahh... This happen to me 2. Is because you added music, That what i can say. If you remove the music everything should goto normal.

Awesome! Thanks so much, I removed ALL extra sounds I had put in (instead of just removing the added music) and that did it. That brings me to a related problem I wonder if you know about. I put in 4 castlevania musics to my map (A castlevania RPG map so it has a purpose), and randomly, the map will compile and the sounds function properly, and other times I compile and the music will not work, and editing the Sound Editor files of each music says that their length is now "00:00:00" instead of what they were before the compile. Any ideas how to fix this? Thanks again.

Soulcutter

There is an issue with sounds liek this. Don't remember exactly what causes it, but don't use Test Map.

I can't address the 00:00:00 bug, which has hit me as well, but a while back, I inserted into my map music with a long title, creating a long variable name (or maybe it had a reserved character in the title) which in turn caused WE to spew compilation errors at me, and disable every trigger I was using connected to that one. I fixed the problem by renaming the music variable to something much shorter and simpler, and my problem disappeared.

That actually makes a lot of sense, throughout my 4 weeks of map editing I've changed the root MP3 files into shorter variables too, just to see if that made a difference. It seems to help right now, at least, but during my next compile, who knows. =P

And Monk, I think your suggestion might be the problem, I know 'all' of my tests have been through the editor's "test Map" button except for 2 to see what the options were to the players on the startup screen.

Solution: DON'T USE THE TEST MAP FEATURE, LOAD YOUR MAP UP INSIDE WAR3 INSTEAD -- using the test map feature corrupts all your sound/music and makes it length 0:00:00 9/10 times.

Yes, never use the test map feature. If you have anything 'random' in your map, it will be the same everytime you test it. I always just have w3 minimized and open it when I'm gonna try a map.

I run WC3 in a window. Makes testing even easier.