Phase 2: tile examination and surroundings

Game-file footprint unchanged: still one line in main.lua.

- describe.lua: shared spatial formatting. 8-point compass and Chebyshev
  distance, since the game moves 8-directionally and Euclidean would overstate
  diagonal travel. Verbosity setting, because sweeping eight neighbours and
  inspecting a single tile want different amounts of detail.
- states/ingame_observe.lua: narrates the game's existing examine cursor.
- surroundings.lua: probe one direction, scan all eight, or report location,
  without moving anything or touching game state.
- patches/popups.lua: wraps inventoryCursorPopup.set, covering inventory, craft,
  refine and trade in a single patch.

Q3 resolved as augment rather than relay: the game's descriptions carry no
position, which is fine on screen and useless by ear, so distance and direction
are appended.

Examine mode is polled rather than driven by levelCursorPopup. That popup is set
from an animation-completion callback, so unless the player has enabled the
game's quickExaminationPopup option the text arrives a full keypress late -- in
testing you heard the previous tile while standing on the next. Polling
level.cursorX/Y is same-frame and setting-independent.

hotkeys.isCtrlDown/isShiftDown are now overridable fields rather than direct
love.keyboard calls: real hardware state cannot be faked by love.event.push, so
without that seam every modifier-gated hotkey would be untestable.

11/11 testbed checks, history unit tests passing.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Accessibility Mod
2026-08-01 21:26:35 +02:00
co-authored by Claude Opus 5
parent da512fc67e
commit 8b1eb44c38
12 changed files with 559 additions and 6 deletions
+14 -2
View File
@@ -48,14 +48,26 @@ end
-- Modifier helpers
--------------------------------------------------------------------------------
local function ctrlDown()
-- Indirected through overridable fields so the testbed can drive modified
-- hotkeys. love.keyboard.isScancodeDown reads real hardware state, which a
-- synthetic love.event.push cannot influence -- without this seam, every
-- modifier-gated key would be untestable.
hotkeys.isCtrlDown = function()
return love.keyboard.isScancodeDown("lctrl", "rctrl")
end
local function shiftDown()
hotkeys.isShiftDown = function()
return love.keyboard.isScancodeDown("lshift", "rshift")
end
local function ctrlDown()
return hotkeys.isCtrlDown()
end
local function shiftDown()
return hotkeys.isShiftDown()
end
--------------------------------------------------------------------------------
-- Bindings
--