The Core Mechanic Loop
The core mechanic loop β sometimes called the 'game loop' or 'core loop' β is the fundamental repeating cycle of actions that defines what a player does moment to moment. Every successful game has a core loop that is engaging enough to repeat thousands of times without becoming monotonous. Designing this loop well is the most foundational skill in game design, because every other system in the game wraps around and elaborates on this central cycle.
A core loop can typically be described as a sequence of three to five actions that cycle continuously. In a classic shoot-'em-up: Move β Aim β Shoot β Collect (power-up/score) β Repeat. In a city-builder: Survey resources β Place building β Wait for output β Reinvest output β Repeat. In a match-three puzzle game: Scan the board β Identify match β Swap tiles β Clear matches β Refill board β Repeat. The simplicity of this description belies the complexity of making each step in the loop feel satisfying.
Critical to core loop design is the concept of verbs β the actions available to the player. Every mechanic can be expressed as a verb: jump, shoot, craft, trade, build, explore, negotiate. The set of verbs available in your game defines its identity and its expressive range. A game with one verb (jump) must make that verb extraordinarily deep to sustain engagement. A game with many verbs must ensure they combine meaningfully rather than creating noise.
Designers also distinguish between primary mechanics (the main actions in the core loop), secondary mechanics (supporting systems that add variety without replacing the primary experience), and meta-game mechanics (systems that operate across multiple play sessions β account progression, unlockables, social features). A healthy game design typically has one strong primary mechanic, several well-chosen secondary mechanics, and meta-game mechanics that provide session-to-session continuity.
To test whether your core loop is strong, apply the 'one more turn' test: would a player who just finished a cycle feel compelled to start another immediately? If the answer is yes β if the end of one cycle naturally creates desire for the next β your core loop has the right structure. If the player feels satisfied to stop, you may need to introduce a hook at the end of each cycle: a cliffhanger, a partial reward, or an unresolved goal that persists to the next iteration.