Macro won't get executed

[Daffa]

The editor throws an error saying that the MPQ could not be opened. I'm running as an administrator.

 

[MindWorX]

Can you PM me the map perhaps? I'll give it a look, see exactly what tool is giving issues.

 

[Daffa]

It's not a personal map, it's a spell material.

Power Aura 1.0.1

The macro is from @Doomlord's Custom Stat System, which is used in his Inventory system (forgot the name)

 

[Swan]

I think I'm getting the same error, fresh install of Sharpcraft but on a map I have worked on and saved with sharpcraft before. I was using windows 7 when it worked and now windows 10.

 

[Daffa]

Oh yeah, that reminds me, I use Windows 10.

 

[MindWorX]

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.

 

[Daffa]

Sorry, forgot this thread. I guess that can be tested out, maybe when I got the interest. I'm not on a rush anyway.

 

[Swan]

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.

Didn't work for me unfortunately, got the same error message.
EDIT: Nevermind, I just changed the files in the wrong directory. That fix does seem to work.

 

[yatyfornetreg]

Same here. Works perfectly on my old vJass/Zinc map except for

//! external ObjectMerger

My Settings

WEX Version:

Both 0.1.2.9 and 0.1.3.0-FIX

D:\Applications\SharpCraft World Editor Extended Bundle

Warcraft 3 Version

1.28.5.7680 (Chinese simplified) Genuine

Fresh install, no other plugins installed, no other troublesome non-English mods/plugins installed. Compiles and works on my non-English vJass/Zinc map.

D:\Applications\Warcraft III

OS

Windows 10 Pro 1709

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.

Does not fix it in my case.

 

[MindWorX]

...

Would you be willing to share the map with me? If so, I can test and try and locate the issue.

 

[yatyfornetreg]

Would you be willing to share the map with me? If so, I can test and try and locate the issue.

Thank you very much, here are the maps.

 

[Wareditor]

Will this issue be resolved ?

 

[yatyfornetreg]

Will this issue be resolved ?

Never mind, I've already found an alternative solution: ChiefOfGxBxL/WC3MapTranslator.

 

[Wareditor]

Never mind, I've already found an alternative solution: ChiefOfGxBxL/WC3MapTranslator.

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.

 

[yatyfornetreg]

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.

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.

So, Object Merger still needs to be fixed.

 

[Wareditor]

Object Merger is working fine, the issue is WEX.

 

[Av3n]

Stumbled upon this thread as I was researching the error reported here. What is the current status quo about the fix?

 

[KILLCIDE]

Object Merger has always worked for me *shrug* I guess it had something to do with me fixing the registry a while back so I can get Magos to work

TriggerHappy also mentioned a fix for Object Merger here: //! ObjectMerger Calls broken in WEX

 

[Av3n]

I didn't think of that possibility.. Thanks for the link @KILLCIDE!