What comes first: game mechanics or character design? How to Achieve the Best Game Concept? Game Mechanics vs Character Design

Open original

A game developer's guide to how mechanics, worldbuilding, and character design depend on each other. The author argues that mechanics come first in practice, but character design shapes which mechanics feel believable and fun.

  • Game rules set boundaries, while mechanics are the feedback loop that teaches players how to act within them.
  • A character's silhouette, backstory, and collider should be designed with the intended mechanics in mind, since a boxy collider can make platforming frustrating.
  • Platformer tweaks like jump buffering and coyote time make games more forgiving without breaking immersion.

The article's central argument is that game mechanics and character design can't really be separated, and that the question of which comes first is less useful than it sounds. Mechanics, in the author's framing, are not the same as rules. Rules define the boundaries of the game world, like a map's edges or the physics that govern movement. Mechanics are the feedback loop built on top of those rules: the negative signal when a player strays out of bounds, the positive cue when they act the way the designers intended. The author uses Diablo as the example. Nothing technically stops a player from sprinting past every monster to the next area, but the mechanics (monsters dropping better gear, kills unlocking skills) are what make fighting the reason to play at all. Most games, the author argues, reduce to a handful of basic mechanics, such as point-and-click until you hit a goal, or move from A to B before a timer runs out. The middle section makes the case that worldbuilding and character design have to support those mechanics rather than sit beside them. A world needs consistent ground rules (gravity, lighting, how characters move) so the player trusts what the mechanics are telling them. The author contrasts the detailed world of Tolkien's Middle-earth with the deliberately sparse world of Minecraft, noting that both work if the rules hold. On character design, the warrior with a sword and shield signals a head-on fighting style, while a slender figure with a steel whip suggests stealth and vertical exploration. Early silhouettes set boundaries between character and environment, and stylized versus basic shapes hint at whether the setting is gritty and realistic or playful with odd physics. The author also says a fully finished design can reveal background and motivation, sometimes producing "happy accidents" that shape the game. The final section gets concrete about feel. Platformers are the clearest case: pixel-precise jump rules sound realistic but frustrate players who expect to double jump or chain jumps quickly. The fixes the author names are a jump buffer, which registers inputs slightly before landing, and coyote time, which lets a player jump a few milliseconds after walking off a ledge. Collider shape matters too, since a boxy collider snags on corners and ledges and makes platforming miserable. The author also flags a structural risk: if a character's arc calls for new mechanics late in development, bolting them onto a finished core game tends to go badly, so progression should be planned from the start.

Ask about this article