On this page
Every action needs a response
The single most reliable way to make a game feel worse is to let an action happen silently.
A collected coin that produces no sound, no particle and no number reads as a bug even when the score went up — because the player's model of the game is built from feedback rather than from state. If nothing happened, nothing happened.
So every meaningful action here produces at least two of: a sound, a particle burst, a popup number, a screen shake, a colour flash. Not all five; two or three, chosen to match how important the action was.
Scale the response to the event
Feedback that does not scale is almost as bad as none, because it stops distinguishing between outcomes.
| Event | Sound | Particles | Shake | Popup |
|---|---|---|---|---|
| Collect a coin | Short tick | 7 | None | No |
| Raise a combo step | Rising arpeggio | 7 | None | No |
| Defeat a creature | Kill sound | 11-12 | None | Yes |
| Take damage | Hurt sound | 12-16 | 7 | Flash |
| Defeat a boss | Win fanfare | 44-60 | 16-18 | Yes |
| End a run | Descending tone | 16-24 | 9-12 | Flash |
The gap between eleven particles for a creature and forty-four for a boss is what makes the boss feel like a boss. Mechanically it is a health bar reaching zero; experientially it is the difference between an event and a moment.
Screen shake is a scalpel
Shake is the most overused effect in arcade games and one of the most effective when rationed.
Our rule: shake only for things that should feel heavy — taking damage, a boss slam, a giant landing, a structure collapsing. Never for collecting something, never for a successful action, and never continuously.
Magnitudes sit between 5 and 18 pixels and decay over about a quarter of a second. And it is disabled entirely when the player has requested reduced motion, because shake is the effect most likely to cause genuine discomfort.
Popup numbers do two jobs
A floating '+50' that rises and fades is doing more work than it appears to.
It confirms the action happened, which is the baseline. But it also teaches the scoring system without a tutorial: a player who sees '+50' and then '+150' for the same coin learns that something multiplied, and starts looking for what.
That is why popups show the awarded value rather than the base value. Showing the base would be more consistent and would hide the multiplier, which is the most important thing in the game.
Silence as punctuation
The counterpart to constant feedback is knowing when to stop.
The breather between waves has no spawn sounds. The moment after a boss dies has nothing but the fanfare. The pause screen is genuinely silent. Those gaps are what make the busy parts feel busy — a game with continuous feedback has no dynamics at all, and a game with no dynamics is exhausting.
The same logic applies to visual density. Every scene has a quiet band — plain ground, empty sky — that exists so the busy foreground has somewhere to be read against.
Feedback should tell the truth
One rule that overrides all the others: feedback must match what actually happened.
It is tempting to make a near miss flash, or to shake the screen when a player nearly took damage. Both feel exciting and both are lies, and a player who learns that the screen shakes for things that did not happen stops trusting the screen shaking at all.
The same applies to the reverse. An absorbed hit produces a visible shield burst rather than nothing, because a hit that silently did not count would be equally confusing. Feedback is a channel, and a channel with noise in it stops being usable.
The first ten seconds
More potential players are lost in the first ten seconds than at any other point, and almost all of it is avoidable.
Four things have to be true by the ten-second mark: the player has done something, something has responded, they know what the goal is, and they have not yet failed.
The order matters. Acting before understanding is fine and is how arcade games have always worked — you press a button, something happens, and the understanding follows. Explaining before acting is what loses people, because a wall of instructions is a wall regardless of how well written it is.
The corollary is that the opening must be easy enough that nobody fails it while still working out the controls. A death in the first ten seconds reads as the game being unfair even when it was entirely the player's doing, because they had not yet agreed to be tested.
Give the player something to be good at
The underlying principle beneath every technique in this guide: a game is engaging when there is a skill in it that visibly improves.
That requires three things. The skill has to be identifiable — the player can name what they are getting better at. It has to be measurable, so improvement is visible rather than felt. And it has to have room, so it does not top out after twenty minutes.
Games that fail to engage usually fail on the first. A player who cannot name what they are practising will not practise, no matter how much feedback, escalation or polish is layered on top — and no amount of reward schedule substitutes for a skill that is actually there.
Key takeaways
- An action with no feedback reads as a bug, even when the state changed correctly.
- Feedback must scale: eleven particles for a creature and forty-four for a boss is what makes a boss feel like one.
- Shake only for heavy events, never for success, and never when reduced motion is requested.
- Popups show the awarded value rather than the base, because that teaches the multiplier without a tutorial.
Frequently asked questions
Why does the screen shake when I take damage?
To make damage feel heavy. It is used only for heavy events and is disabled entirely under reduced motion.
Why do score popups show different numbers for the same item?
They show the awarded value after the multiplier, which teaches the combo system without a tutorial.
Can I turn off the effects?
Enable reduced motion in your operating system's accessibility settings. Particles drop, shake is disabled and parallax flattens.