Files
moonwell-client-core/docs
Sam Sung 53bc8245b7 Every item action sends ahead of its cursor clear's and lock's signals (#2759)
Every item action queued its packet for after its Lua call, so the cursor clear's and the lock's listeners ran before the packet went out. In 1.12.1 each sends first, then clears or locks. Examples: `AutoEquipCursorItem` (send at `0x5e1757`, clear at `0x5e1763`), the split (`0x4f9e43`, then `0x4f9e4f`), `DeleteCursorItem` (`0x4898a3`, `0x4898af`), the bank and sale arms (`0x4fa305`, then the lock at `0x4fa312`), and the merchant sell (`0x4fb7a7`, `0x4fb7b3`).

Every item send now goes to the host in place, ahead of its clear's or lock's signals, and `Model::item_calls` is gone. The projectile unlock is decided once, from the item's record (`0x5d9f30`). A set refused with no control plays no pickup sound (`0x494b8d`).

Tests cover 16 paths, in the order each sends and signals. Each fails on main.

Fixes #2752

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-28 14:01:42 +07:00
..