| 01-05-2004, 10:12 PM | #1 |
Is there any way to resolve them. I opened my map in WE 1.13b Made a few minor changes Hit save And the compile error dialog box came up and DISABLED EVERY ONE OF MY TRIGGERS ONE BY ONE, saying "theres an error in the trigger and it needs to be disabled". Please tell me someone knows what would cause this and tell me how to fix it. The map opened and saved FINE in WE 1.12 |
| 01-06-2004, 12:08 AM | #2 |
This happened to me a few times. Does your map use any local variables? Usually when that happens it is a problem with one simple line (for me it was a misspelled variable), try checking what the last error displayed is and fix it. |
| 01-06-2004, 07:00 AM | #3 |
Local variables? I don't think I using any local variables. Last line? It said 6000+ compile errors. After it disabled my first 30 triggers (and there are FAR more) I Ctrl-Alt-Del end tasked the WE. As for misspelled variables, wouldn't that have cause the compile error to happen 1.12 WE too? Because it saved FINE in WE 1.12. |
| 01-06-2004, 01:50 PM | #4 |
Do you have functions in the custom script section?, if you do show them to us. The best thing you can do when you get that silly thing is to ctrl+alt+supr and close the editor (Congratulations blizzard) |
| 01-06-2004, 02:06 PM | #5 |
k let me say this.... i had exactly the same problem i had to look thru 132 triggers !! look them thru and u will see an action or a condition that says unknown.. then correct it and turn it on... by the way which kind of triggers was disabled =? in my map it was all orderstrings :/ |
| 01-06-2004, 04:48 PM | #6 |
Vex: No custom script at all. You have a copy of my map (though that copy crashes warcraft3 1.13b I think, if it doesn't then would you mind sending me a copy back.. maybe mine got corrupted or sumpin).. what I did was reverted my War3 to 1.12, opened the map in WEU, removed all WEU fuctions. Opened it in WE 1.12, added back WE versions of some of the WEU fuctions I removed, saved the map, it saved fine. Updated War3 to 1.13b, opened my map. Added 2 functions that were new to 1.13b that I used to have the WEU version of in my map (target of casting spell), and hit save.. And btw, ctrl-alt-del is exactly what I did... Chemo: None say unknown, and EVERY last one of my triggers was disabled, I have triggers that order units, triggers that do my voting system, triggers that give items to units, triggers that change owner ship of units, triggers that open/close my gates, trigger that give text to player when they type "-help", it even disabled my trigger that sets up my quest menu. BTW my map does have a custom Blizzard.j in it, put in it by WEU. Could this be related to my problem? (though I doubt it, if it was then I would have had problems saving in WE 1.12...) PitzerMike is in the process of releasing a new version of WEU, if he releases it soon I might just open my original map in it and see what happens. But until then, any more ideas? I looked at my triggers and most of them do not have anything in common with eachother. And it does disable everyone of them in the order that they are in the trigger editor. I never let if finish disabling them because I have a couple hundred and I don't feel like clicking "ok"/hitting the spacebar on 100+ dialog boxes that say "this trigger disabled due to errors". |
| 01-06-2004, 06:41 PM | #7 |
yes, It's the old blizzard.j file in your map |
| 01-06-2004, 06:44 PM | #8 |
So the problem is becuase my map has the OLD blizzard.j in it? Will your next version of WEU auto update old maps? |
| 01-06-2004, 09:05 PM | #9 |
yes with the updated files everything will work again as it used to |
