| 02-09-2003, 03:55 AM | #1 |
Guest | I tried to save my map recently and it gave this error. Line 559: expected variable name WHAT DO I DO? OH GOD IF I CAN'T FIX THIS I'M GONNA SNAP. I spent the last 3 days working nonstop on this map. |
| 02-09-2003, 04:18 AM | #2 |
Guest | That error indicates that a variable is missing. This could be caused by mispelling the name (case sensitive), not having defined it in the first place, deleting it out of the variable list, or not defining an index if that variable is an array. If you got this error, WE probally disabled the trigger and then saved it. |
| 02-09-2003, 04:27 AM | #3 |
Guest | Hmm mispelling it isn't possible cause I pick from a drop down list. I didn't rename any variabls. I guess i'll check if I accidentally checked the array box. |
| 02-09-2003, 04:28 AM | #4 |
Guest | I can't find anything wrong with any variables :\ |
| 02-09-2003, 04:46 AM | #5 |
this happens sometimes with wc3, i remember people complaining about this before, i belive the fix was to uninstall wc3 and reinstall.. =/ |
| 02-09-2003, 05:14 AM | #6 |
Guest | That had better be a joke. I cannot lose this much work because of some stupid bug. Can I use the line # to figure out where the problem is in any way? |
| 02-09-2003, 05:27 AM | #7 |
loose what, you reinstall wc3, you map is fine, its something inside the mpq (most likely the blizzard.j file) that is messing something.. this is just a guess, it could a number of things, if you not using any custom code, and all your functions are filled out with no missing data, that is probly the problem |
| 02-09-2003, 05:42 AM | #8 |
Guest | I've had something similar happen to me when I indexed and array element that was either not initialized or invalid. I would really check your code. You can switch to script mode in the trigger view with the Edit/Convert to custom text, then just hit the undo button to return to trigger view. Don't edit any of that text or you could create a real mess. But I have found in the past that what trigger mode shows a value set to is sometimes corrupt when you view it in text mode. So I delete that trigger and just make it again and it seems to fix it. Text mode is just a good way to find which one is screwed up. There are some weird things that happen with that editor at times for sure but as a whole, it's pretty stable really. |
| 02-09-2003, 05:51 AM | #9 |
Find the disabled trigger and look through it. It happened to me before and it was because it disabled my condition for some reason. |
| 02-09-2003, 08:12 AM | #10 |
Guest | Ok I fixed it. I delted the triggers I made most recently and then moved back from there till it stopped giving the error. Thanks for the help guys. |