2 Commits

Include renames

Author	SHA1	Message	Date
claudeandClaude Opus 5	7b710471df	Make the arenas' cover actually stop bullets ... The player's muzzle was fixed last commit; every enemy and boss emitter has one too, and theirs reach further. A ring sits 46px out, an arc sweep's outer arms sit past 100px, and a wall-gap curtain spans the whole arena -- most of a curtain is nowhere near the thing that fired it. The pool samples geometry once per tick and never sees the jump, so all of those were spawning bullets on the far side of whatever stood between. That matters here more than it sounds, because both boss arenas are authored out of cover. The hall has pillars; the vault has barricades, and its own comment says they are there so that knowing where the Cantor is does not hand you a firing lane to it. A barricade blocks bullets and deliberately does NOT block sight -- so it is exactly the cover this bug cancelled. Measured before fixing: the Warden's curtain put 13 shots through a one-tile wall and its arc sweep 13 more; the Cantor's curtain, 16. Two checks, not one. The path test skips its own starting tile so a shooter in a doorway still resolves, and that skip let a telegraphed burst whose centre and ring sit inside one wall tile through -- born in the wall, announced to every client, dead on the next tick. The destination is now asked separately, so a bullet never exists inside geometry. A telegraphed strike passes its own marker as the source rather than the boss: that burst is born where the player was warned, and a pillar between the boss and the spot has nothing to say about it. A strike marked on cover is now simply a dud, which is cover working; pinned by a test so it stays a known shape. First attempt at this used a turret behind a barricade and proved nothing -- a turret's 24px offset cannot clear its own 16px radius plus a 32px tile, so the test could not have failed. Replaced with the two emitters that can reach, plus both real arenas. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-07 17:24:34 +02:00
claudeandClaude Opus 5	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