![]() ![]() As an example and about the files linked in the thread you mentioned above, the v1.21b EN-GB full installer for RoC will install successfully on a W98SE VM client (and one can later update RoC to any of the patches up to and including v1.26a), *but* installing v1.21b EN-GB TFT linked in the thread above will fail on that OS. Those official full downloadable versions of the game may have their own set of issues, compared to their original retail CD-ROMs counterparts from 2002/2003. Slade: Well, the title of the thread says 'Downloaders', not Installers, while he just mentioned he found Portable versions of the Czech version (which are obviously unofficial ones, as Blizzard never made any portable version of the game) Some discarded legacy files were left out iirc in the new 'deprecated.mpq' file, for compatibility reasons (or for modders to integrate some of its contents into their maps, before these assets disappear for good?).Ĭlick to expand. I am guessing that this soon led in the deprecation/removal of war3patch.mpq, because it became useless. I am guessing this was because Blizzard was in the process of refactoring the contents of war3.mpq and of war3x.mpq, to create a new baseline for all locales I am therefore guessing it was the reason they launched the 1.28.x series of online updates/patches, for which one had to re-download the entire game with each new minor revision. I am guessing this proved to be impractical by using standalone offline patches, because any subsequent patch after 1.27b would probably have been almost half as big as the game itself. deleting those files and injecting compatible ones might make your map work (but its long shot and you have to be pretty adept at wc3 modding/editor stuff).Because each locale version of the game was developed kind of separately from each other afaik, I am guessing that v1.27.x was Blizzard's early attempt at normalizing/sanitizing the assets from all the locale versions of the game, to later fuse them into one single, cohesive baseline. ![]() ![]() In my research (new jass and 1.31 object editor data not counting), wtg, w3i, and wct files are the things that prevent maps from being back-compatible (or forward compatible in some cases). If the third party wc3 hosts abandon 1.26 in favour for shiny new 1.32+, then you could probably stop worrying about anything other than latest wc3 ver. A Silver lining is that Blizzard seems to try and fix back-comp issues but it will take several months just like it did with the 1.31 clown fiesta. ![]() This is where protected maps bury themselves with all the irony the 2006-8 internet can muster, since they cannot be opened with world editor and re-saved to new format (nice job protecting your maps guys-from-the-past that-are-no-longer-around-to-provide-new-version!). If your map is already not compatible with 1.26, and you don't want to hassle getting old ver or making map compatible with old ver, you'd have to recompile/resave it with new world editor. My prediction is that there would only be two standards, 1.26 (which is compatible with the third party nonsense), and whatever Blizzard shoves down our throats (just like they did with 1.31). ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |