fix(interaction): publish pending keyboard pickups
Route F-key pickup through the same ItemHolder backpack placement entry point as double-click activation so the inventory reserves the destination slot before the request is sent.
This commit is contained in:
parent
047a4c83b5
commit
52dbb5749e
4 changed files with 43 additions and 17 deletions
|
|
@ -69,7 +69,7 @@ Copy this block when adding a new issue:
|
|||
|
||||
## #231 — F-key pickup omits retail pending destination-slot presentation
|
||||
|
||||
**Status:** IN-PROGRESS — isolated as Slice 1 corrective commit
|
||||
**Status:** FIXED (2026-07-21) — keyboard pickup uses the shared ItemHolder path
|
||||
**Severity:** MEDIUM
|
||||
**Filed:** 2026-07-21
|
||||
**Component:** selection / inventory / retained UI
|
||||
|
|
@ -98,6 +98,11 @@ destination/placement pending reservation, then sends one authoritative request.
|
|||
Server confirmation settles it; server failure removes it without speculative
|
||||
ownership mutation.
|
||||
|
||||
**Resolution:** `ItemInteractionController.PlaceWorldItemInBackpack` now owns
|
||||
the shared pending-placement notification and request dispatch. Both
|
||||
double-click activation and the F-key route enter that method, so they publish
|
||||
the same destination container and placement before the server request.
|
||||
|
||||
---
|
||||
|
||||
## #230 — Selection hits and deferred actions can cross live GUID incarnations
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue