fix(inventory): complete switches on wield response
Clear retail AutoWield on the matching authoritative WieldObject instead of waiting for unrelated rollback bookkeeping to drain. This prevents a completed switch from consuming the next weapon activation locally, including crossbows. Co-Authored-By: Codex <codex@openai.com>
This commit is contained in:
parent
ea5cf5b842
commit
3e84027885
9 changed files with 47 additions and 21 deletions
|
|
@ -459,8 +459,9 @@ include dungeons.
|
|||
primary weapon to the main pack, then any incompatible shield/ammo, waiting
|
||||
for every server move confirmation before wielding the requested
|
||||
bow/sword/caster/two-hander. The shared transaction works
|
||||
in peace and war, remains busy through final `WieldObject` confirmation, and
|
||||
prevents rapid switches from overlapping; ACE owns stance-specific motions and its PropertyInt 40 update
|
||||
in peace and war, remains busy through the exact final `WieldObject`
|
||||
acknowledgement independently of rollback bookkeeping, and prevents rapid
|
||||
switches from overlapping or remaining stuck; ACE owns stance-specific motions and its PropertyInt 40 update
|
||||
now drives the client `CombatState`.
|
||||
- **L.1c local attack receive path (implemented 2026-07-11; live gate pending)** —
|
||||
local non-autonomous mt-0 UpdateMotion now uses retail's wholesale interpreted
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue