fix(items): port retail useability and autowear rejection

Use the exact low USEABLE_NO-bit predicate so reset/zero-valued direct-use items such as Blackmoor's Favor reach the ordinary Use request. Port AutoWear's clothing-priority blocker lookup and exact named system notice through the shared activation owner.

Co-authored-by: Codex <codex@openai.com>
This commit is contained in:
Erik 2026-07-23 08:33:31 +02:00
parent 60387668d0
commit f71f947475
13 changed files with 289 additions and 57 deletions

View file

@ -15,11 +15,14 @@ assessment information, equipped-child picking, vendor browsing, and
server-authoritative vendor transactions. Slice 1's DAT-authored arrow-only
favorite-spell scrollbar, fixed 18-cell capacity, authored arrow sides/media,
and persistent manual offset passed the connected gate. Slice 2 is active: the
status hand now follows canonical selection/object notices, ghosts empty and
unusable selections, and routes enabled weapons, direct-use items, and
use-on-target tools through the existing interaction transaction and cursor
owners. Its connected hand-state gate is pending; the magnifying-glass Assess
command follows in the same slice.
status hand follows canonical selection/object notices, ghosts empty and
explicitly unusable selections, and routes enabled weapons, direct-use items,
and use-on-target tools through the existing interaction transaction and
cursor owners. Its connected state gate passed. A named-retail correction now
treats reset/absent useability zero as usable, allowing Blackmoor's Favor to
send ordinary Use, while shared AutoWear reports the exact overlapping worn
item that must be removed. That correction awaits its connected gate; the
magnifying-glass Assess command follows in the same slice.
---