Designing arcade games for the short run
A short-session arcade game has to hook, reward and reset in well under a minute. These are the rules we tune VoltCade's quick games by.
Most of the games on VoltCade are built for short sessions: open the page, start, play one round, look at the score, go again or leave. That is a very different brief from a game meant to be played for an evening, and it shapes how the quick games here are tuned. (Dynasty Sevens is the deliberate exception.)
The first ten seconds matter most
In a run that might last thirty seconds, ten seconds is a third of the experience. If they are spent on a logo, a tutorial pop-up or an empty difficulty ramp, the player has seen nothing of the game. So the quick games skip all of it: a start screen, one input, and you are playing. Instructions sit beside the game rather than in front of it.
Difficulty has to be interesting straight away as well. A game that takes twenty seconds to become engaging is a game whose interesting part many players never reach. That often means starting harder than feels safe to the person who built it.
The score has to be legible at a glance
Players read the score during the run, not after it. If the number needs explaining, the run feels flat even when it plays well. The quick games show a score that goes up, with the combo or multiplier next to it where the game has one, and very little else.
Restarting has to cost nothing
Most people play more than one round, so the price of the next round has to be as close to zero as possible: one key or one tap from the game-over screen. Every extra step between one run and the next is a chance to stop.
Variance, but readable variance
A run that plays out identically every time is abandoned after a handful of tries. Changing spawn patterns, different power-ups and the occasional rare event are what make the next run a different run. They are also part of what makes a high score feel earned.
Too much variance is as bad as too little. If a run can be ruined by something the player could not see coming, the leaderboard starts to feel arbitrary. The target is randomness the player can read and react to, so that skill is expressed on top of chance rather than drowned by it.
The takeaway
Designing for a short run is less a constraint than a filter. Every system either justifies itself in the time a player actually spends, or it goes. That is why the quick games look spare: what is left is what survived.