TrinityCore / TrinityCore/WowPacketParser
Wrong Map ID in the SQL
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 522
- Forks
- 387
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 4
Description
I parsed a sniff and the mapID returned in the sql was wrong for spawns ( 0 instead of 571):
(@CGUID+137, 30273, 0, 210, 4504, 1, 1, 0, 0, 0, 6347.772, 225.4826, 393.7119, 1.151917, 120, 10, 0, 0, 0, 1, 0, 0, 0, 12340), -- 30273 (Area: 4504 - Difficulty: 0) (possible waypoints or random movement)
(@OGUID+38, 192965, 0, 210, 4504, 1, 135, 0, 6392.244, 440.5654, 511.2919, -0.1027641, -0.105731, -0.06836033, -0.05852318, 0.9903145, 120, 255, 1, 12340), -- 192965 (Area: 4504 - Difficulty: 0)
Area and zone ID are correct
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported SQL output from the parsed sniff and trace how spawn map IDs are generated. Compare the shown mapID of 0 with the expected 571 while preserving the correct area and zone IDs; done means the generated spawn SQL uses the correct map ID.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100