1.24 errors on empty map?

[Storyyeller]

Ok, so I understand that Blizzard messed up horribly and the script parser will often reject custom maps that don't use the return bug, but I am still at a loss to explain how a completely empty map with no triggers whatsoever still generates errors when saving in WE.

Could anyone tell me what is going on here? Yes, I'm using version 1.24 of the WE. Attached is the map, plus a screenshot of what happens whenever I try to save.

 

[saphiree]

Lol dunno what your prop is. Are you using the normal WE? When i tried to save it nothing happened, so i dont know whats the problem is. The map itself dont even have a script code as far as i can see.

 

[Storyyeller]

Exactly. One idea I had is that it might be using the wrong files for common.j and blizzard.j, but I can't figure out how that could possibly happen, or how to fix it if that is really the problem.

By the way, I am using the normal WE, and it is a completely empty map, generated by the WE with the new map option.


Edit: Nevermind. I figured out that any files placed in
C:\Program Files\Warcraft III\Scripts
automatically overrides the normal Warcraft Files (including those in War3Patch.mpq), regardless of settings. I fixed it by putting an up to date version of Blizzard.j in the scripts folder.

I thought that only script files imported to the map itself were parsed, but I guess it doesn't work that way.