Map crashes when a modified .w3u file is imported into MPQ

[worldmapper]

Ok, this is strange because I haven't seen a map protected like this before.

I've used MPQMaster to extract war3map.w3u and imported it into Object Editor on World Editor. No problem so far.

Then I went ahead and changed the max health value of one unit from 200 to 201 in WE. Extracted w3u, imported newly changed w3u into the map.

When I try to load the map in Warcraft 3, the map crashes saying that the file data is corrupted (war3map.w3u).

I went ahead and tested for multiple units and changed only one value slightly, such as sight range from 700->701. Same issue. I'm thinking the map has some sort of special protection that potentially checks byte by byte on the modified w3u (very unlikely) or it has some sort of checksum value that Warcraft 3 checks (more likely).

To make sure that world editor wasn't messing up my modified w3u, I went ahead and did a hex compare of both the original and modified w3u. Needless to say, only a single byte that I've changed was modified.

I've also tried a similar thing for w3a, .j file (added a single space), same issue. I've never seen any maps do this before.

What kind of protection mechanism does this? How can I bypass this?

The map in question is TKOK Eastern 3.3.0f by the way.

[flavius13]

Why you dont rebuild arhive first?

[Xirizo]

Last time he logged in was the time he made that thread so this guy is not serious about his question.

[haxorico]

make sure you delete the (attributes) file?...