Tracker selection now survives a rescan. The scan is rebuilt every turn and
both lists are distance-sorted, so holding a bare index meant one step by the
player silently re-pointed the selection at a different rat. The tracker now
remembers identity instead -- the actor table for creatures, coordinates for
tiles -- and re-derives the indices in reanchor() after each rescan. Selection
is dropped only when the thing genuinely stops being reported (out of FoV,
killed, picked up), and the existing clamp then falls back to the nearest.
Ctrl+Home walks to the selection, reusing the exact shape of the game's own
click-to-path in ingame.mousepressed: calculatePathFromPlayer, then either
bufferInput or playerInput for a one-step path. Interruptions and threatened-
player truncation therefore behave the way a mouse click does. Most things
worth tracking stand on impassable tiles, which calculatePathFromPlayer refuses
outright, so we fall back to the cheapest of the 8 neighbours and say "next to"
rather than "to". Guarded on states.getCurrent() == "ingame": elsewhere the
input buffer belongs to another state and feeding it moves would be a bug.
Wall tones now follow the usual proximity convention -- a near wall is loud,
one out at radius is quiet. It was inverted, which read backwards in play since
a nearby wall is the more urgent fact. config.louderWhenFurther still flips it.
Testbed covers both: selection identity across a forced rescan, and that
Ctrl+Home moves the player without breaking out of the map.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Adds accessibility/README.md, the player-facing setup and keymap reference --
the thing to read before playtesting.
Brings the developer docs in line with what was actually built:
- docs/README.md rewritten as an index with current status and a one-paragraph
architecture summary.
- docs/scratch.md gains a HANDOFF section: state of play, the commands to run
after any change, the five traps that each cost real debugging time, what is
NOT verified and why, deliberate omissions, and how to rebase onto a future
game version.
- docs/03-implementation-plan.md gains a status banner listing where the
implementation deliberately diverged from the plan (menu narration pulled
forward as a blocker, levelCursorPopup not patched, tryInteract insufficient
as a tracker filter, testbed added, no settings UI built).
- docs/04-open-questions.md gains a resolution banner: Q6 and Q8 remain open.
Also records that the testbed check count varies between runs (23-26) because
some blocks are conditional, so what matters is zero failures rather than the
total.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Accessibility ModandClaude Opus 5