-
Notifications
You must be signed in to change notification settings - Fork 363
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
Wrong Map ID in the SQL #514
Comments
Which patch or build does the sniff have? |
3.3.5 12340 build |
bad news - mapid was added in 4.0.1 to updateobject, so we gotta hack a bit around to retrieve the map id. Like temporary saving the mapid after teleports and such. WowPacketParser/WowPacketParser/Parsing/Parsers/UpdateHandler.cs Lines 14 to 20 in 3b2e808
|
MapID is also broken in text output. It stays 0, confirmed with 1.13 sniffs. |
Classic also giving 0? |
This might be the reason in pre-cata versions - CurrentMapId has ThreadStatic attribute so each thread has different value if you are using multithreaded parsing WowPacketParser/WowPacketParser/Parsing/Parsers/MovementHandler.cs Lines 15 to 16 in b223e9f
|
I'm only using 1 thread, ofc i only tested 1.13 sniff |
It obviously won't work if you started sniffing after being in world and before being teleported |
1.13 is using bfa packets, that has mapid in UPDATE_OBJECT, it should output correctly |
Map isn't read correctly at all.
|
I parsed a sniff and the mapID returned in the sql was wrong for spawns ( 0 instead of 571):
Area and zone ID are correct
The text was updated successfully, but these errors were encountered: