- Joined
- Jan 30, 2013
- Messages
- 12,440
The editor throws an error saying that the MPQ could not be opened. I'm running as an administrator.
Didn't work for me unfortunately, got the same error message.I'll see if I can dig into it, but it's likely caused by Blizzard changing how the MPQs work. War3patch.mpq doesn't hold the information it used to.
One thing you can try is create is rename war3patch.mpq => war3patch.original.mpq and then make a copy of war3x.mpq and name the copy war3patch.mpq.
This might fix the issue, since war3x.mpq now has all the war3patch.mpq files.
//! external ObjectMerger
MindWorX said:
I'll see if I can dig into it, but it's likely caused by Blizzard changing how the MPQs work. War3patch.mpq doesn't hold the information it used to.
One thing you can try is create is rename war3patch.mpq => war3patch.original.mpq and then make a copy of war3x.mpq and name the copy war3patch.mpq.
This might fix the issue, since war3x.mpq now has all the war3patch.mpq files.
Would you be willing to share the map with me? If so, I can test and try and locate the issue.
Would you be willing to share the map with me? If so, I can test and try and locate the issue.
Never mind, I've already found an alternative solution: ChiefOfGxBxL/WC3MapTranslator.Will this issue be resolved ?
Never mind, I've already found an alternative solution: ChiefOfGxBxL/WC3MapTranslator.
No, it just build w3a w3h w3u ... files from json or parse w3x files into json. You still have to import the w3* files into your map on your own.Can this be used directly inside WE ? If not then this issue is still important and is a problem for anyone trying to use Object Merger.