[Solved] Order rule of reading patches in Noggit

[Magnus]

I think Noggit (all versions) reads the patch files in a wrong order.

How to proof:
The only thing I want to change is an area name. F.ex. Quel'talas into something different. Therefore I change the AreaTable.dbc and make a patch patch-6.MPQ The patch I copy into the WoW Client data folder and to the server dbc folder. That works fine. If you go ingame the area has the new name.

But it doesn't work in that way in Noggit. I also copy the patch-6.MPQ into the data folder of my Noggit WoW client.
In Noggit still the old area name appears. Looking to the log, this is the order patches are read:

Code: [Select]

[Debug] Opened archive E:World of Warcraft - NoggitData/common.MPQ
[Debug] Opened archive E:World of Warcraft - NoggitData/common-2.MPQ
[Debug] Opened archive E:World of Warcraft - NoggitData/expansion.MPQ
[Debug] Opened archive E:World of Warcraft - NoggitData/lichking.MPQ
[Debug] Opened archive E:World of Warcraft - NoggitData/patch.MPQ
[Debug] Opened archive E:World of Warcraft - NoggitData/patch-2.MPQ
[Debug] Opened archive E:World of Warcraft - NoggitData/patch-3.MPQ
[Debug] Opened archive E:World of Warcraft - NoggitData/patch-6.MPQ
[Debug] Opened archive E:World of Warcraft - NoggitData/enGB/locale-enGB.MPQ
[Debug] Opened archive E:World of Warcraft - NoggitData/enGB/expansion-locale-enGB.MPQ
[Debug] Opened archive E:World of Warcraft - NoggitData/enGB/lichking-locale-enGB.MPQ
[Debug] Opened archive E:World of Warcraft - NoggitData/enGB/patch-enGB.MPQ
[Debug] Opened archive E:World of Warcraft - NoggitData/enGB/patch-enGB-2.MPQ
[Debug] Opened archive E:World of Warcraft - NoggitData/enGB/patch-enGB-3.MPQ
So I think my patch 6 is overwritten by one of the patches that apears after my one in the log.


Next step:
I copy my patch-6.mpq to patch-enGB-6.MPQ and put it in the enGB folder. After restarting Noggit the area name is shown correctly with my own custom name.

Looking to the log;

Code: [Select]

[Debug] Opened archive E:World of Warcraft - NoggitData/common.MPQ
[Debug] Opened archive E:World of Warcraft - NoggitData/common-2.MPQ
[Debug] Opened archive E:World of Warcraft - NoggitData/expansion.MPQ
[Debug] Opened archive E:World of Warcraft - NoggitData/lichking.MPQ
[Debug] Opened archive E:World of Warcraft - NoggitData/patch.MPQ
[Debug] Opened archive E:World of Warcraft - NoggitData/patch-2.MPQ
[Debug] Opened archive E:World of Warcraft - NoggitData/patch-3.MPQ
[Debug] Opened archive E:World of Warcraft - NoggitData/patch-6.MPQ
[Debug] Opened archive E:World of Warcraft - NoggitData/enGB/locale-enGB.MPQ
[Debug] Opened archive E:World of Warcraft - NoggitData/enGB/expansion-locale-enGB.MPQ
[Debug] Opened archive E:World of Warcraft - NoggitData/enGB/lichking-locale-enGB.MPQ
[Debug] Opened archive E:World of Warcraft - NoggitData/enGB/patch-enGB.MPQ
[Debug] Opened archive E:World of Warcraft - NoggitData/enGB/patch-enGB-2.MPQ
[Debug] Opened archive E:World of Warcraft - NoggitData/enGB/patch-enGB-3.MPQ
[Debug] Opened archive E:World of Warcraft - NoggitData/enGB/patch-enGB-6.MPQ
Now you can see that my patch patch-enGB-6.MPQ was the last one. But that's not the way wow is reading patches.

I think they should be read in this way (or similar):

Code: [Select]

Data/common.MPQ
Data/common-2.MPQ

Data/expansion.MPQ
Data/enGB/expansion-locale-enGB.MPQ

Data/lichking.MPQ
Data/enGB/lichking-locale-enGB.MPQ

Data/patch.MPQ
Data/enGB/patch-enGB.MPQ

Data/patch-2.MPQ
Data/enGB/patch-enGB-2.MPQ

Data/patch-3.MPQ
Data/enGB/patch-enGB-3.MPQ

Data/enGB/locale-enGB.MPQ

Data/patch-*.MPQ
Data/enGB/patch-enGB-*.MPQ


Hope you get the idea what I want to say  

[Steff]

You should put DBCs into a local patch. Also all interface stuff.

[Magnus]

After all I also found my way where to put patches into the different application folders.

It seems that TC mapextractor, Noggit and the WoW client reads patches in 3 different ways.

While TC claims not to be interested in client modding at all it may be ok for them.

However, Noggit should read patches exactly in the same way as the WoW client is doing it.

For me it works well with a single patch (f.ex. patch-6) including dbcs, interface, maps etc. However I use multilingual DBCs, means I use both column english and german.

[Skarn]

Locale patches have heigher priority than the usual ones. The loading order is similar to the game.

[Magnus]

Similar is not exactly ;-)

For example WoW reads the patch-6.mpq AFTER the patch-enGB-3, even the last one is a locale one.
IMHO patches should be read with this pattern:

Code: [Select]

/Data/common.MPQ
/Data/common-2.MPQ
/Data/expansion.MPQ
/Data/enGB/expansion-locale-enGB.MPQ
/Data/enGB/expansion-locale-deDE.MPQ
/Data/lichking.MPQ
/Data/enGB/lichking-locale-enGB.MPQ
/Data/enGB/lichking-locale-deDE.MPQ
/Data/patch.MPQ
/Data/enGB/patch-enGB.MPQ
/Data/enGB/patch-deDE.MPQ
/Data/patch-2.MPQ
/Data/enGB/patch-enGB-2.MPQ
/Data/enGB/patch-deDE-2.MPQ
/Data/patch-3.MPQ
/Data/enGB/patch-enGB-3.MPQ
/Data/enGB/patch-deDE-3.MPQ
/Data/enGB/locale-enGB.MPQ
/Data/enGB/locale-deDE.MPQ
/Data/patch-4.MPQ
/Data/enGB/patch-enGB-4.MPQ
/Data/enGB/patch-deDE-4.MPQ
/Data/patch-5.MPQ
/Data/enGB/patch-enGB-5.MPQ
/Data/enGB/patch-deDE-5.MPQ
/Data/patch-*.MPQ
/Data/enGB/patch-enGB-*.MPQ
/Data/enGB/patch-deDE-*.MPQ


[Skarn]

No, it does not. there are also some differences between different clients. For example, Russian client can't load DBCs and UI from data patches while US one does it perfectly.

[Magnus]

That's really verry strange.  :shock:

Well, I have tested it only for english and german clients.

And also only for 3.3.5a. Don't know how later versions handle this.

[Skarn]

Later versions use a different system of updates.