The first time we shipped a game without touching the audio brief, it was a harbor management sim — cranes, cargo ships, a little coastal town — and the coin-collect sound was a sine wave. Not because anyone chose it. Nobody had chosen anything; a placeholder "bloop" had gone in during early scaffolding and just never gotten swapped out, the way a stock photo survives into a finished website if nobody's watching. The graphics were fine. Hand-painted water, gulls, a warm little dock at sunset. Then you picked up a shipping container and the game made a noise like a 2007 flash game timer running out.
We pulled the build up on a shared screen to figure out what was wrong with it, and it took about four seconds of actually listening — eyes closed, someone insisted, half as a joke — before the room agreed: the whole thing sounded like a microwave. Every success chime, every UI tick, all synthesized on the fly, all made of the same thin electronic material regardless of what game they were attached to. A cozy harbor town and a cyberpunk shooter would've made identical noises. That's the tell. Sine waves don't know what world they're in.
So we went looking for the actual fix, and the actual fix turned out to be boring in the best way: stop generating tones and start recording instruments. Not sample packs licensed from somewhere, not synthesized approximations tuned to sound "warm" — real instruments, recorded, sampled across their range, so a note played back is a note a musician actually played. We built this out over a few weeks into a words-fail-me-sized library.
| Game feel | Instrument palette |
|---|---|
| Adventure | Orchestral strings and brass |
| Cozy puzzle | Plucked strings and mallet percussion |
| Arcade urgency | Drums and bass |
| Ambient, slow-burn | Pads and keys |
Alongside the instruments we recorded ambience separately, because a world needs air in it, not just a soundtrack:
- Rain
- Surf
- Wind
- Room tone
- The murmur of a crowd
We went back to the harbor game with the library actually available and rebuilt its sound from scratch. Water lapping under the docks, gulls somewhere off-mic, and when you successfully load a container onto a ship, a mallet — a real one, recorded hitting a real bar — plays the notes that used to be a beep. Same notes, same moment in the gameplay loop. Completely different game. That comparison is the whole argument in miniature: a chime played by a marimba and the identical pitches played by an oscillator are not interchangeable outputs of "make a success sound." They're different products wearing the same function.
Once the library existed, the harder problem showed up, which is that a library doesn't compose itself. The instinct would've been to build a folder of stock stingers and let every build grab from the same pile, and we specifically didn't do that. The design director's brief that sets a build's color palette also sets its audio palette, so the composition happens per game — a noir detective game and a farm sim don't get handed the same instrument set any more than they'd get handed the same font. Sound effect placement follows the same logic down to individual objects: what's the object, what surface is it hitting, how big is it, what mood is the scene in. It's the same specificity we'd insist on for a sprite or a piece of UI copy, just applied to something people are used to treating as an afterthought.
And because "an afterthought" is exactly how audio regresses, we didn't leave it as a style guideline that hopes to survive contact with a deadline. It's part of verification now — the in-browser check that runs before a build ships actually listens to it, and a world layer that's silent, or effects that quietly fall back to a bare oscillator because a sample failed to load, fails the pass the same way a broken button would. Not a note in a review doc, a defect. One of our own builds got flagged and auto-fixed for exactly that not long ago; the mechanics of how that catch works are in How builds verify themselves.
