[dalnar]

It appears Blizzard has removed the function of ignoring ambiguous MPQ files. You may once again load single or multiple MPQ's using the old naming template: "patch-x" without the use of the CFG.

[Pullefjun]

Pics or it never happened.

[dalnar]

Pics prove nothing as you could pack a bunch of edits into a single mpq anyway.

Try it yourself; Rename your mpq's to the old template, clear your .cfg file and use the exe to open WoW.

[merfed]

Reported. Wrong forum for discussion.

[dalnar]

Originally Posted by merfed

Reported. Wrong forum for discussion.

I am not explaining how the new method works, nor am I posting links to the files. I am simply letting everyone know that the "new" method is no longer necessary.

[Fault]

moved to discussion

[Tyler Durden]

Does this work? anyone confirmed this?
Does this mean that you no longer need the wowme thing? just old things?

[moreniu]

Trying right now.

Update: No, it doesnt work, at least my human - ud did not work without the me.

T_T

[trollpaxton]

Originally Posted by dalnar

It appears Blizzard has removed the function of ignoring ambiguous MPQ files. You may once again load single or multiple MPQ's using the old naming template: "patch-x" without the use of the CFG.

Wait...when could you -not- load ambiguous MPQs? There has long been a problem loading MPQs with m2s in them, but haven't regular old patch-x.mpqs worked as long as they only had blps in them...like forever?

[dalnar]

I am talking about mpq's with .m2 extensions in them. As long as you name the mpq patch-x, you can open WoW with the force .exe and you will have the patch-x applied. You don't have to put anything in the .cfg file. Which was required before.

As an example, I'm am currently running 4 different mpq files (with m2's) and my .cfg file is blank.

Point being, I bet if someone updated the old ModelEdit.exe for the live version, it would work.