2 Commits

Author	SHA1	Message	Date
claude	872922e9e2	Fix boss jitter; add a settings screen for controls and volume ... The jitter had two causes, and the larger one is embarrassing: boss_state() handed back the newest snapshot raw while players and enemies both went through the interpolator. The boss therefore stepped at the 20Hz snapshot rate instead of the frame rate. Invisible for as long as every boss stood still, and the first one that moved looked broken. It is interpolated now -- but not across an instance change, where the previous snapshot describes a different fight in a different room and lerping to it would fling the new boss across the map for a frame. The smaller cause was server-side: a CHASE boss corrects by the SIGN of its distance error, so at the standoff the sign flipped every tick and the boss vibrated a couple of pixels at 60Hz. It has a dead band now. The settings screen covers rebindable controls and volume, reachable from both the main menu and the in-game menu. Bindings are stored as physical keycodes -- following key position, the choice setup_input_map.gd already made -- and labelled back through the active layout so an AZERTY player reads the letter on the key their fingers are on. A rebind replaces every event on the action rather than the first, because an action that kept its alternates would still answer to the key you just moved away from. A key already in use is refused and the clash is named. Reset restores what the PROJECT shipped, captured once before anything overrides it -- captured later it would restore the last session's choice, which is the thing being undone. Effects play on an SFX bus created at runtime, so both sliders are real mixer settings rather than a number multiplied into every play() call. Worth recording: the test suite AND the smoke test both passed while a client logged twelve engine errors on every startup. ConfigFile.get_value(s, k, null) does not mean "no default" -- it means the key is absent and no default was given, and the engine logs an error per action. Nothing caught it because the smoke refutations matched SCRIPT ERROR and friends, and a plain ERROR: is none of those. It surfaced from running the client and reading the output. smoke.sh now asserts no plain engine errors either, excluding by name the one line Godot prints on every clean exit, and reintroducing the bug makes it fail. One mutation caught nothing and should not have: the early return in linear_to_db_clamped was dead code, since the clamp beneath it already prevents negative infinity. Removed rather than left looking tested. check.sh clean, 439 tests, SMOKE PASS (23 assertions), all four diagnostics green, and a real client boots with zero engine errors. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-07 10:56:44 +02:00
claude	e0c1e0d5c6	Stage 5: bosses that move, attacks that warn, and a second boss ... Boss movement is a property of the PHASE, not of the boss -- a fight that stands still and then starts hunting you is one boss with two phases. Four modes (STATIC, ORBIT, CHASE, WAYPOINTS) handled generically in SimWorld._move_boss, so a boss that moves is still data. BossDef.stationary is gone rather than kept beside the phases: a flag claiming the boss stood still while a phase walked around would be a second source of truth and the wrong one, so moves() is derived. CHASE holds a distance instead of closing, because a boss standing on top of you is a boss whose bullets cannot be read. Waypoints are fractions of the arena so one phase works in rooms of different sizes. Every mode is speed clamped in one place -- ORBIT computes an absolute destination and would otherwise snap onto its circle on the first tick -- and movement slides against geometry so a boss cannot walk through the pillars its own arena was designed around. The room clamp moved to after movement, where it is finally load-bearing. It was a no-op while every boss stood still, which is exactly when an invariant is cheapest to establish: boss rooms deliberately do not lock, so walking out is always an escape, and that only holds if the boss cannot follow. TelegraphedStrikeEmitter marks spots and fills them a moment later. The moment between is the feature: a burst at your feet is a coin flip, the same burst with a second of notice is a question. It stays stateless like every other emitter -- they are shared resources and two bosses of the same kind must not stomp each other -- so strike positions are derived from the volley number and a test asserts the burst lands where the marker promised. Markers are drawn through fog and through walls, unlike everything else in the view, because a warning you cannot see is an unavoidable hit with extra steps. The Cantor of the Vault fights in the choir vault: static, then a four-corner circuit, then a chase, then orbiting while marking. It exists to prove the format stretched, and a test asserts it uses both new mechanisms. Which boss a run has now comes from its SEED rather than its depth. Depth is a dev flag nothing in play raises, so the arena was keyed to something no player can change and the second boss was unreachable in an actual game. Two things found while finishing: - tools/export_content.gd had a hand-maintained boss list and had already gone stale, silently not writing the Cantor. Content.ALL_ENEMIES and ALL_BOSSES now feed the export tool, the renderer and five tests that each kept their own copy. - diag_loot failed intermittently after another diagnostic. Taking over from the bot cleared its input queue but not its HELD input, so a starved server coasted on the bot's last movement vector for half a second and walked the player off the item it had been placed on. The press arrived correctly, which is why "the press reached the simulation" passed while everything it should have caused failed. check.sh clean, 409 tests, SMOKE PASS (19 assertions), all four diagnostics green. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-06 16:32:12 +02:00