Second level compression in files inside a mpq/w3x?

[ACDS2]

*deleted*

 

[Dr Super Good]

Sorry, this site does not support anything related to extracting stuff from protected maps.

 

[ACDS2]

Sorry, this site does not support anything related to extracting stuff from protected maps.

No problem,I will edit out original post,maybe sites like wc3edit or thehelper forum is more appropriate for this kind of stuff.Sorry for breaking the rules.

 

[Dr Super Good]

I can tell you though that a lot of the files that WC3 uses to make its maps are data files, and thus do not have to be readable for them to be usable. Infact, often by reducing the readability, it improves the speed of loading the map as it is more compacted and such.

 

[ACDS2]

I can tell you though that a lot of the files that WC3 uses to make its maps are data files, and thus do not have to be readable for them to be usable. Infact, often by reducing the readability, it improves the speed of loading the map as it is more compacted and such.

Thanks for the info but it's not the problem I encountered.As a former/semi-active mapper I am particularly interested the inner works of modern Warcraft 3 custom maps,but unfortunately most of them are protected/corrupted by protect tools or optimizer.

I understand the specifications of slk files,they are sort of excel or CSV,even though they make little sense when viewed in notepad like tools,they are still understandable.But the files I got have some kind of encryption or compression I have never seen before in any protected/unprotected map,each of the first 4 bytes is well exceeded 0x80(ascii range),so that's not a magic header file of zip/mpq or anything I could recognize,I guess it is either mpq editor is fooled by the deliberately corrupted archive and extracted garbage data or the data itself is encrypted or compressed by an algorithm supported by Warcraft 3.