Cata Classic - 4.4.1.58158 dump bigger than expect and extreme slow parsing?

[TheSCREWEDSoftware]

I just did a run on 3 different clients and the difference of size was quite difference.

Vanilla and Cata were from Orgri (entrance) to each zepplin (vanilla outside, cata on top of orgri) to tristafal and walked (vanilla) and mounted (cata) to scarlet monastery (armory).

And retail was from dornagal to orgri to undercity portal (which took me at back in time npc outside of undercity) and i flew with dragon riding to scarlet monastery (which has the old armory dont recall the name now).

To in the end get to the end of the dungeon and interact with the plaques in.

Some how retail which loaded more information and gather more in theory than the other two. retail and vanilla had almost 1MB of difference in size (2MB (Vanilla) to 2.9MB (Retail)) and Cata had 7MBs and was taking much longer than the other two. (this data non-parsed)

Average time for vanilla and cata was 10 ish (cata was more like 8) mins and retail was 5 if not less.

If this is a intended behaviour be free to close this.

[Ovahlord]

This is because of hotfixes.

[killerwife]

Its also because shaurens parsing on retail works perfectly, and mine on vanilla is shoddy at best. Its especially visible on 3.4.3 parsing incredibly quickly without exceptions, and 3.4.1 and 3.4.2 being pretty crap cos i only did a makeshift solution for most important packets.

[TheSCREWEDSoftware]

Thanks for the clarification. I pressume the ones that are working (for cata) in this case are aware of this? if it's the case is worth keeping the issue opened?

[Ovahlord]

Cata Classic parses just fine

[TheSCREWEDSoftware]

It parsed the file fine. The question should If keep my issue opened as my oriignal question was answered. (related to the size difference and longer parsering) in the case if is not known to the maintainers of this case cata parser part of it.

[Ovahlord]

Keep it open for now.
The cata parsing is currently broken as a result of the recently added 1.15 changes which apparently were untested for 4.4.x. This will eventually get fixed