Sam Sung 42db0b49d2 Party and raid getters read at each packet's place, as 1.12.1's do (#2435) ...

The party and raid family, read at each packet's place, for #2168. The group getters read live through the call host seam: count, leader, loot method, the `GetRaidRosterInfo` family, the `UnitIn*` tests and the `partyN`/`raidN`/pet token rows (`0x4e86d0`, `0x4bb560`, `0x4bb8c0`, `0x4e9130`, `0x4bb910`). The group tokens are rebuilt over the roster as of each packet. `READY_CHECK`, its answers and `UPDATE_INSTANCE_INFO` go on the party lane at their handlers.

On the way, it matches the bytes. The party slots are compact: a zero GUID leaves no gap (`0x4e82eb`), and our own entry is skipped (`0x5e6b88`). `UnitPlayerOrPetInParty`/`Raid` follow `0x4e8fa0` and `0x4bafd0`, matching members and their pets, never the player.

Tests: two group lists in one frame each read their own roster; each event reads the cells its reference store left; the zero-GUID and pet cases. They fail on main.

Part of #2217

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

2026-10-26 03:48:07 +07:00

..

CONTRIBUTING.md

Unattended logins answer a PIN from WOW_PIN or WOW_PIN_TOTP (#2386)

2026-10-25 09:46:06 +07:00

DEVIATIONS.md

Party and raid getters read at each packet's place, as 1.12.1's do (#2435)

2026-10-26 03:48:07 +07:00

MAP.md

Window input dispatches record by record, in arrival order (#2429)

2026-10-26 01:56:52 +07:00

METHOD.md

Test gates run under cargo-nextest, doctests beside them (#2036)

2026-10-20 10:27:18 +07:00