Sam Sung d814179f7c Pet cooldowns flush at each packet's place, as 1.12.1's do (#2421) ...

In 1.12.1 the pet's cooldown list (list 1) flushes at each packet's own place. `PET_BAR_UPDATE_COOLDOWN` fires from five sites: `0x6e2e8e`, `0x6e3080`, `0x6e8601`, `0x6e95b9` and `0x6e971c`. The pet getters query that list live (`GetPetActionCooldown` at `0x4be03c`, plus the pet book and bar at `0x4b40dd` and `0x4e6cf7`). benilla flushed the pet's list once a frame and read it from the frame's final state.

Now the pet's list logs and replays like the player's (#2414), on its own lane in packet order, and the three getters read it live. A failed `CAST_RESULT` fires its GCD-clear pair (`0x6e167d`) before the pop (`0x6e2218`), so the cast slot and the targeting word change only at the pop.

The tests cover two pet packets in one frame, a player packet then a pet packet, and the GCD-clear pair seeing the cast still held. Each fails without its piece.

Part of #2217

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

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

2026-10-25 22:50:51 +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

Pet cooldowns flush at each packet's place, as 1.12.1's do (#2421)

2026-10-25 22:50:51 +07:00

MAP.md

The WMO audit's pin variables no longer share the login PIN's prefix (#2404)

2026-10-25 18:19:25 +07:00

METHOD.md

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

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