Operator delegated the placement call. Applied standard top-down-arena practice
rather than the first-pass ring scatter:
clear core (5u) the landing spot and dash room; props there cramp spawn
and cause dash collisions the player never asked for
band 6-13u solids live in KITING range, which is also roughly where
the diver's travelling light reaches. A prop outside the
lit radius reads as an invisible wall - the worst failure
mode in a dark game, so cover is pulled inward to where
it can be SEEN before it is hit
min spacing 2.6u enforced across clutter AND cover on ONE shared occupancy
list. This is a NAVIGATION guarantee, not an aesthetic:
enemies have no pathfinding, so gaps must stay wider than
a body. Rejection-sampled; a piece that cannot fit is
DROPPED rather than jammed into a gap movers can't pass
explosives >8u a barrel near the landing spot chains into you on spawn
Measured live, all three invariants hold:
17 solids, radius 7.89..12.95, min gap 2.79 (policy >=2.60), 0 explosives <8u
Nav re-validated on a CLEAN run: closest approach 1.40u, two enemies in melee.
Enemies cross the inward cover band and reach the player.
Correction worth recording: three intermediate readings showed "frozen movers"
and were WRONG. Teleporting the player around a long-running Play session
desyncs the predicted character controller and leaves stale AI state - the
server had the player back at (2.5,0) while I was measuring against (0,0), and
an earlier "all four frozen" reading was simply enemies that had converged and
were attacking. Only the clean, unmutated run is valid. Do not mutate server
state and then trust a movement measurement in the same session.
304/304 EditMode green.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
kronic
9f145e3a83