How we handle examples
A finished game can demonstrate an audible relationship. It cannot, by itself, prove how that relationship was programmed. We distinguish observations and suggested exercises from documented tool behavior. Where technical details depend on software versions, we direct readers to the relevant official documentation.
Our examples include contrasting approaches rather than a ranking of “the scariest” games. A spatial clue in a stealth game and an environmental layer in a survival horror game can illuminate different design problems without being interchangeable solutions.
Comfort and access belong in the design
We do not recommend painful playback levels, unsupported frequency claims or essential clues available only to one listening setup. Captions, mix controls, mono checks and alternative signals are part of good communication, not an afterthought.
Emotional responses differ. An exercise can help you evaluate a decision; it cannot guarantee fear, immersion or accessibility for every player. Test with a range of people and take their descriptions seriously.
Corrections and useful questions
If an attribution, explanation or link needs correction, please identify the page and the specific passage. A reliable public source is especially helpful. You can prepare that information in the editorial note pad, then send it using your own email application.
Start with the room