mirror of
https://github.com/Kelsidavis/WoWee.git
synced 2026-03-23 07:40:14 +00:00
fix: reject oversized MonsterMove spline and fix loot format comment
Change WotLK MonsterMove pointCount > 1000 from cap-to-1000 to return false. Capping caused the parser to read only 1000 of N points, leaving the remaining point data unread and misaligning subsequent reads. Also correct misleading loot response comment: Classic/TBC DO include randomSuffix and randomPropertyId (22 bytes/item, same as WotLK). The only WotLK difference is the quest item list appended after regular items.
This commit is contained in:
parent
64b03ffdf5
commit
0b33bcbe53
2 changed files with 4 additions and 5 deletions
|
|
@ -21253,8 +21253,8 @@ void GameHandler::unstuckHearth() {
|
|||
}
|
||||
|
||||
void GameHandler::handleLootResponse(network::Packet& packet) {
|
||||
// Classic 1.12 and TBC 2.4.3 use 14 bytes/item (no randomSuffix/randomProp fields);
|
||||
// WotLK 3.3.5a uses 22 bytes/item.
|
||||
// All expansions use 22 bytes/item (slot+itemId+count+displayInfo+randSuffix+randProp+slotType).
|
||||
// WotLK adds a quest item list after the regular items.
|
||||
const bool wotlkLoot = isActiveExpansion("wotlk");
|
||||
if (!LootResponseParser::parse(packet, currentLoot, wotlkLoot)) return;
|
||||
const bool hasLoot = !currentLoot.items.empty() || currentLoot.gold > 0;
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue