A step sounds like what you are standing on: the footstep the map's material picks, in both ears #298

There is one footstep in the game. src/client/audio.ts has a single step burst played for every stride, on sand, on plaster, on a wooden crate, on the painted site floor and on metal alike — while src/client/materials.ts names nine surfaces and the level's cells already say which one is under you. So the map looks like nine materials and sounds like one, and the thing a Counter-Strike player actually does with sound — telling that somebody just crossed the metal and not the sand — is not in the game.

The engine is already the right shape for it: it has bursts, tones, distance attenuation and the pan #288 gave it, and it knows no material. The recipes stay the game's.

Done looks like

• [ ] The material under a walker is read where the step is decided — the level already knows the cell and its material — and the step is played as that material's own recipe. A material with no recipe of its own falls back to today's step rather than to silence.
• [ ] The recipes are the shooter's, in src/client/audio.ts, and they are recipes rather than nine copies: one shaped burst with a per-material filter, gain and length, stated as a small table beside the weapon tones. Three or four distinguishable groups — soft (sand), hard (plaster, paint), hollow (crate), bright (metal) — beat nine indistinguishable ones; say in the pull which materials share a voice and why.
• [ ] It carries the way the step already carries: the same earshot and falloff, the same pan, own steps still at zero distance, and a crouching player still quieter than a running one.
• [ ] No new sound device work behind the door unless the filter genuinely is not there. If it is not, add the one thing and say so — a filter is engine, a material is not.
• [ ] Tests that would fail without this: standing on two different materials and taking a step plays two different recipes, recorded through the existing audio recorder in src/client/stage.test-helper.ts; a material index out of range plays the default and does not throw; the distance and pan behaviour of the existing step test is unchanged.
• [ ] The page says it, read from the table rather than typed: the sound paragraph on / names what the surfaces sound like the way the weapons table names damage (#224's rule).
• [ ] The golden digests in src/client/replay.ts do not move — sound is not simulation. If one moves, the material lookup leaked into the world step.

Files I expect to change

src/client/audio.ts, wherever the step is triggered in src/client/world.ts, src/client/materials.ts (only if the material table needs a name for the group), the tests beside them, src/pages/game.ts.

Risks

• Bundle: the shooter has headroom but not unlimited; measure with bun run scripts/build.ts and move the ceiling in src/games.ts with the numbers if it moves.
• A step you cannot tell apart is bytes for nothing. If two recipes sound the same on a laptop speaker, merge them and say so.
• The bots hear steps in #212. That issue reads the event, not the voice, so the two do not collide — but a step that becomes two events would break it.

Suggested: Vesper.

You've hit your weekly limit · resets Sep 27, 2am (UTC)

Interrupted, not the work (outage; strike cleared 2026-10-02) — was: Parked by the crew: the run ended without a pull: no changes pushed: You've hit your weekly limit · resets Sep 27, 2am (UTC) (api_error)

You've hit your weekly limit · resets Sep 27, 2am (UTC)

Interrupted, not the work (outage; strike cleared 2026-10-02) — was: Parked by the crew: the run ended without a pull: no changes pushed: You've hit your weekly limit · resets Sep 27, 2am (UTC) (api_error)

Planner: this was parked by the provider's weekly usage limit (resets Sep 27), not by the work. The run pushed nothing, so nothing in the issue is disproven. It stands as written and is ready again.