New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Broken parsing of 4.x sniffs #262
Comments
I have this error when trying to parse SQL file https://s17.postimg.org/rbkzwssfj/Capture.png |
@Flameshot: No idea how your comment is related to this issue but I'll fix that shortly. |
@DDuarte sorry if i posted wrong here but i didn't want to make a new issue for my problem so I saw this issue related to 4.x sniffs and I posted the crash I have here. You can fix the error that i encounter or the issue? |
@Flameshot: try after f6ff9a9 |
this bug is still valid? |
Yes, i have issue on 14480Ulduar_AllExceptLast2.pkt file
|
i have a sniff from # Detected build: V5_4_8_18414 |
Upload the sniffs in our forum so that I can take a look. |
upload link in forum, in section adb/wdb/sniff note: if i set my local git folder 7 month back in time, the wpp translate successful |
my initial clone of wpp was from 2014-2015 |
MovmentInformation is read incorrectly MovementHandler.cpp Change this:
to this:
|
This will solve 90% of you issues |
Still broken for 4.3.2 sniffs. |
open new issue. PS: MOVE_UPDATE not fixed anywhere |
Description: Some packets like SMSG_MOVE_UPDATE or SMSG_UPDATE_OBJECT are broken for cataclysm-era sniffs
Current behaviour: Random excerpt from a sniff:
Expected behaviour: The packets should parse correctly
Steps to reproduce the problem:
36712db
--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/37226405-broken-parsing-of-4-x-sniffs?utm_campaign=plugin&utm_content=tracker%2F457228&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F457228&utm_medium=issues&utm_source=github).The text was updated successfully, but these errors were encountered: