Sam Sung e8c5b60650 The quest log reads live at the call; its events fire at their packets (#2449) ...

The quest log's getters read copies pushed into the VM at frame end, and its events fired from a frame-end feed. A listener therefore saw the log as the frame's last packet left it, not as the reference's slot reads (`0x4dfa41`, `0x4e01df`) find it at the call.

Now the slots, held counts (`0x622130`), standing (`0x4d6370`), coinage and the timers' clock read live through the call host. Template landings and refusals, toasts with `QUEST_WATCH_UPDATE`, rank moves and time syncs fire on a quest events lane at their handlers' stamps. The LFG quest list reads the live slots too. The frame-end clock feed and most of the log feed are deleted.

Tests: five full-client and five VM tests cover the live reads and the event order at the packets, including a refused template. They fail with the live reads off or the events stamped late.

Part of #2217

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

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

2026-10-26 08:14:09 +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

The quest log reads live at the call; its events fire at their packets (#2449)

2026-10-26 08:14:09 +07:00

MAP.md

Account data syncs with the server, as 1.12.1 does (#2447)

2026-10-26 07:50:09 +07:00

METHOD.md

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

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