Game Mechanics

Open original

Dave Eng explains what game mechanics are, using a horse racing card game and Street Fighter as examples, and argues that mechanics both drive player engagement and carry the learning outcomes in educational games. He closes with advice on building a solid, repeatable core loop before adding secondary mechanics.

  • A mechanic is a rule that controls one basic part of the game, and the core loop is the main one players repeat. In the horse example, playing "Sprint" or "Trot" cards is the core loop, and changing hand composition adds a second layer of decisions.
  • Layering mechanics creates depth: Street Fighter's special moves came from combining directional and button inputs, which added mastery and variety beyond basic movement.
  • In learning games, the core loop must tie directly to the learning outcome. His job-interview example rewards relevant follow-up questions, since off-topic questions end the simulation early, and serious games need feedback and debriefing so players can see how their actions moved them toward the goal.

Game mechanics are the rules and procedures that govern what players can do and how the game responds. Dave Eng's core point is that a mechanic is more than a verb like "roll" or "move." It's the structure that turns an action into a meaningful choice, and the main mechanic forms the game's core loop and its primary feedback loop. He illustrates this with a tabletop horse racing game: a hand of five cards, one "Sprint" card that moves the horse three spaces and several "Trot" cards that move it one. Letting players add or remove cards from their hand introduces a second mechanic, hand building, which gives them more agency over speed. The takeaway is that good mechanics are layered, each one simple on its own but producing complexity when combined. Eng then looks at how mechanics shape player experience and learning. Scrabble is the example: drawing and placing letters teaches players that rare tiles like Q and P are worth hunting for, so strategy emerges from the mechanic itself rather than being spelled out. Mechanics need both constraint and agency. Constraints add nuance for experienced players, support fair play, and keep the game balanced, and these are design decisions the creator has to make deliberately. He points to Street Fighter as a case of layering: directional movement and button presses combine into special moves like the hurricane kick, which lets a character do something (move while attacking) that the basic movement mechanic can't. That layering gives players both autonomy and competence, which Eng ties to intrinsic motivation. The last section turns to learning games, where intrinsic motivation alone may not carry the design. Because the core mechanic accounts for most of the player's time, it also carries most of the learning, so designers have to tie the desired learning outcome directly to the core loop. Eng's example is a job interview training simulation in which the player, playing the interviewee, must ask follow-up questions that are relevant to the role, with high-quality questions advancing the simulation. Of the closing section on pitfalls, the excerpt provided is cut off before the article finishes, so its specific recommendations aren't captured here.

Ask about this article