Devlog: A13

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-11-15 08:54:14 -05:00
co-authored by Claude Opus 5.5
parent 8142e39ab3
commit 4357861bd4
+73
View File
@@ -1734,3 +1734,76 @@ change; the lesson itself lives on the client.
reproduces.
3. Then the Finishing steps: README status, comments on R6 and R7, and disable the
task.
## 2026-11-15 (late morning): A13, gamepad and accessibility
The v1.0.0 release is still a draft with no binaries, so R5 still waits on Eric. This
run took A13 (#53), the last workable issue in a build milestone that isn't
priority/low. It is on `main` after the v1.0.0 tag, like M7 and A12.
**Gamepad.**
- `PadInput` reads pad events as the session is given them, not the Input singleton,
so tests drive it with simulated events and any pad works. One fixed layout, named by
position (South, East...): sticks move and look, triggers aim and fire, bumpers step
through slots or build pieces, clicking the left stick sprints until you stop, the
right stick toggles build mode, the D-pad does chart, drop and material, Start pauses.
- `ClientInput.poll(delta)` adds the left stick to the keys and turns the look by the
right stick (dead zone, response curve, its own speed setting; aim speed and invert
shared with the mouse). `pad.active` says the pad was used last, so the tutorial
names pad buttons.
- Menus: South chooses, East and Start go back (`PadInput.install_menu_actions()`),
the D-pad and left stick already move focus. East leaves a key rebinding. Start in
play opens the pause menu, and in the pause menu closes it.
- Finding: sliders and tab bars follow a pad only through Input's state, so the menu
tests feed events with `Input.parse_input_event`, the path a real pad takes.
`Viewport.push_input` moved the focus but didn't move a slider or change a tab.
**Aim assist** (`AimAssist`, on by default, a Gamepad tab option): friction (the stick
turns at 45% at an opponent's centre) and, while aiming and moving, a pull of at most
9°/s towards the chest of an opponent within 6° of the look, 90 m, with a clear line by
the world's own raycast. Never for the mouse, never through cover, and it only turns
the client's look, so the server's judgement is unchanged.
**Accessibility** (a new Access tab):
- Colour vision: `Palette.VISION_SIGNALS`, three sets of the four signal colours, read
through `Palette.ghost_ok()`, `ghost_refused()`, `warning()` and `own()`.
`test_palette` simulates protan, deutan and tritan vision (Machado 2009) and requires
each set's pairs at least 0.25 apart in Oklab. The standard ghost is only 0.18 apart
for deutan eyes; the red-green set makes it 0.37.
- Interface size: 90–130%, through the root viewport's `content_scale_factor`. At 130%
the HUD's hotbar collided with the health panel, so `Hud._fit_bottom()` now places it
between the side panels and narrows the slots when needed.
- Captions: `Captions` turns SoundDirector's cues into lines with a direction (the
tide's sounds, gunfire, hits, kegs, footsteps within 20 m, building), skipping the
player's own, refreshing repeats, fading after 3 s.
- Reduce motion: there is no camera shake, so it calms the aim zoom (62° not 48°, eased
over 0.3 s) and the hurt flash (35%).
**Tests:** new `test_pad_input` (10), `test_aim_assist` (5), `test_captions` (7), and
additions to `test_palette`, `test_game_settings`, `test_hud`, `test_menus` and
`test_client_session` (a pad walks the landed player, picks a slot and pauses through a
real offline session).
**Captures (software rendering), looked at:** `make access-captures`. The Gamepad tab's
layout first filled the whole panel, so it became a two-column grid in a scroll
container. The HUD captions capture first showed nothing (no sound near the player in
the staged second), so the scenario now plays on until something is heard: "Gunfire,
behind" and "Shot strikes someone, behind". Blue/orange ghost in the red-green set; the
aim view visibly wider with reduce motion; menus and HUD at 130% fit.
**Not verified:** no physical gamepad has been tried; aim assist strength is untuned by
play. Both belong to R6.
**Gates on 8142e39:** `make check` 780 tests and smoke ok; `make tutorial-check` 12/12;
`make match` ok, replay hash matches.
**Pace:** every build-milestone issue that isn't priority/low or `needs-eric` is now
closed, apart from #80, which hasn't reproduced in about 9,000 comparisons. The
schedule is no longer behind, so the deferred priority/low issues are workable again.
**Next run:**
1. If the release has its binaries, verify them and close R5.
2. Otherwise B4, editing placed pieces (#18): the first open milestone's issue. It
touches the simulation and the protocol, so it needs a soak before it is closed.
3. Then A3 character customization (#43), H10 bot follow-ups (#74), and H8 (#71),
which can only close with a real-GPU profile.