3 Commits

Author	SHA1	Message	Date
claude	b351bc2d55	Stage 4: upgrades, and a quartermaster to spend them at ... Every level banks one choice. Choices queue, and are spent at an NPC in the hub: walk to it, press E, take one of three weighted options. Seven upgrades, all data — split shot, glass cannon, spread, sniper, doubleshot, poison, eraser — and SimWorld gained no per-upgrade branch to run any of them. The four ambiguities in the brief were settled with the user first, since each changes what gets written: damage base x (1 + sum additive) x product multiplicative. The flat +5% every upgrade carries, spread's -10%, doubleshot's -50% and glass cannon's +100% pool; sniper multiplies on top, so two snipers is 4x and not +200%. glass half the LEVELLED maximum, multiplying if taken twice, so the price does not fade to a rounding error by level 15. poison independent stacks, not a refresh. split +/-45 degrees from the original heading. Independent poison stacks sound expensive and are not: every dose lasts the same number of ticks, so doses expire in the order they were added, the pending expiries are a plain FIFO, and PoisonTrack only ever looks at its front. O(1) per actor per tick however many are live. Stats are derived from the upgrade list and never stored, the way level is derived from experience -- a saved stat cannot disagree with the upgrades that produced it. Upgrade riders (split charges, poison, erase chance) travel on the bullet instead, because a shot in flight has to keep what it was fired with rather than gaining Poison because the shooter just took it. Two invariants this collided with, both now pinned: - bullet speed gained a ceiling. Wall collision samples once per tick, so anything over a tile per tick tunnels; two snipers asked for 2480 u/s against a 1920 threshold, and a tunnelling bullet looks like a bullet. - BULLET_INTEREST_RADIUS rose to 2900, because an upgraded player shot is now the longest-travelling bullet in the game. test_interest measured the worst case from static content, which upgrades quietly invalidated. Choosing is intent checked three ways: a choice must be owed, the index must name one of the three options the SERVER put on the table, and the player must be standing at the NPC. The offer is rolled once and persisted, so closing the screen is not a reroll and neither is a crash. tools/diag_upgrades.tscn covers level -> banked choice -> refused in a dungeon and refused across the room -> taken at the NPC -> new stats -> on disk. Bots never walk to the quartermaster, so the smoke test cannot. Known gap recorded in the roadmap: at PLAYER_BULLET_DAMAGE = 6, the +5% the first upgrade carries rounds back to 6 and visibly does nothing. It comes out right in aggregate, but the fix is a balance edit across content.gd and so is the user's call. check.sh clean, 357 tests, SMOKE PASS (18 assertions), all four diagnostics green. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-06 15:34:58 +02:00
claude	a943aa19f6	Add a second dungeon: the Proving Grounds, a test harness you walk into ... Two labelled portals now stand side by side in the hub. The Proving Grounds runs the same generator, the same rooms, the same enemies and the same four-phase Warden -- enemies at a fifth health, the boss at 288 instead of 3600, and trash dropping potions 80% of the time instead of 8%. A manual pass over loot, the inventory, dropping and every boss phase takes a couple of minutes rather than a quarter of an hour. It is multipliers over the shared content rather than a parallel copy: a duplicated Content would drift the first time anything was tuned, and "identical but easier" would quietly stop being true. And it is a portal rather than a launch flag, so the two can be compared back to back without restarting the server -- which is most of the point. Which dungeon you enter is resolved from the player's server-side position, and PORTAL_USED carries the answer. There is deliberately no client message that names a dungeon: one would let any client ask for the generous loot table and bring the results back to the hub. Instance matching compares dungeon ids too, so walking into one entrance can never drop you into the other's run on timing alone. SimWorld.portals replaces portal_pos/portal_enabled, enter_instance carries the portal list and the dungeon id (the client needs the latter to scale the boss bar's ceiling the way the server scaled the boss), and Protocol.VERSION goes to 7. Also pins what happens when two players reach for one item on the same tick: exactly one gets it -- the loop is sequential and the pickup erases the entity before the next player looks. The tie-break is join order rather than distance, which is arbitrary rather than designed, so it is recorded as such. Stale doc fixed while here: MapGen.build() still claimed the client rebuilds the map from the seed, which has not been true since map streaming landed and is the opposite of the rule. check.sh clean, 288 tests, SMOKE PASS (18 assertions, both dungeon kinds opened over a real socket), all three diagnostics green. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-04 21:34:41 +02:00
claude	7af439341d	Stage 1: tile maps, walls, fog of war, aggro, scrolling camera ... Replaces the fixed centred arena with per-world tile geometry, which is the foundation the remaining features sit on. - MapGrid: tile grid with three independent flags -- blocks movement, bullets, sight -- so a pit stops feet but not bullets or eyes, and a barricade stops feet and bullets but not eyes. Circle collision with per-axis sliding, and Bresenham line of sight shared by fog and aggro. - MapGen: rooms and corridors generated from (seed, depth), with hand-authored boss arenas from Rooms stamped in first so a corridor can never carve through a designed fight. Reachability from spawn to boss is asserted over 40 seeds -- "usually connected" is the failure mode that ruins one run in twenty. - Dungeons are populated at creation, per room, instead of gating on waves. You explore and choose your fights; the run ends when the boss dies, not when the map is swept. Boss rooms have no lock, so walking out is always available. - Aggro: enemies need range AND line of sight, so a dungeon stays quiet until engaged and cover actually protects. - Hard fog, scrolling camera, and terrain rendering. Maps are streamed per peer in chunks around that peer's player, and the seed is deliberately NOT sent -- a client holding it could regenerate the whole dungeon, which is a map hack for free. Stream radius (900u) is wider than view radius (460u) because the client predicts movement against walls and simulates bullets that die on them; the accepted cost is a cheater seeing a little further than the fog, never the floor plan. Partial map knowledge means wall deaths must be announced rather than derived. A test caught the subtle half of that: out-of-bounds tiles read as WALL by design, so checking geometry before bounds reported every bullet leaving the map as a wall kill. 128 tests (was 103); check.sh, test.sh and smoke.sh pass. 0.26 ms/tick with 4 players and a boss, ~65x headroom.	2026-09-03 20:49:27 +02:00