There are 4 elements of game mechanics: quantity ,spatial ,state , andaction . The following chart defines each of them and provides some examples of each. After the chart is an application of the framework using 2D Mario games.To demonstrate how you might use this framework, let’s say that we’re writing up the documentation for the health system in a 2D Mario game. We can start with the metaphor, as that’s always the most visible aspect:Mario turns big when he eats a mushroom. When Mario is big, if he takes damage, he turns small, and when Mario is small and he takes damage, he dies.

4 Elements of Game Mechanics

<img alt="arrow" src="https://twimgs.com/gamasutra/images/icon_blogs.png" width="22" height="20"><div dir="ltr">
 by <a href="https://www.gamasutra.com/blogs/author/StephenTrinh/1019232/" dir="ltr">Stephen Trinh</a> on 06/15/20 11:08:00 am 
 
 
 </div><div dir="ltr"> 
 
 The following blog post, unless otherwise noted, was written by a member of Gamasutra’s community. 
					The thoughts and opinions expressed are those of the writer and not Gamasutra or its parent company. 
 </div><h1 data-selectable-paragraph="">A technical framework for understanding game mechanics in systems.</h1>As the subtitle states, this is a framework for a technical understanding of game mechanics in systems — not so much a creative one. I’ve been developing it while working on design documents for various projects, and I feel like it might be useful other designers out there. Its purpose is to help analyze mechanics and give an organized format for breaking down mechanics into their most basic forms. I use it most often when I need to write up comprehensive docs for a game mechanic or system. I also use it to develop new mechanics for an existing system.<h2 data-selectable-paragraph="">4 Elements of Game Mechanics</h2>There are 4 elements of game mechanics: quantity, spatial, state, and action. The following chart defines each of them and provides some examples of each. After the chart is an application of the framework using 2D Mario games.<figure><img height="282" src="https://miro.medium.com/max/801/1*S6QkxltA6pDSSeBq_x3Xcg.png" srcset="https://miro.medium.com/max/276/1*S6QkxltA6pDSSeBq_x3Xcg.png 276w, https://miro.medium.com/max/552/1*S6QkxltA6pDSSeBq_x3Xcg.png 552w, https://miro.medium.com/max/640/1*S6QkxltA6pDSSeBq_x3Xcg.png 640w, https://miro.medium.com/max/700/1*S6QkxltA6pDSSeBq_x3Xcg.png 700w" width="551"><figcaption dir="auto">Any given mechanic can (and most likely will) be made up of more than one element. The example column shows how you can further classify mechanics.</figcaption></figure>To demonstrate how you might use this framework, let’s say that we’re writing up the documentation for the health system in a 2D Mario game. We can start with the metaphor, as that’s always the most visible aspect:<BLOCKQUOTE>Mario turns big when he eats a mushroom. When Mario is big, if he takes damage, he turns small, and when Mario is small and he takes damage, he dies.</BLOCKQUOTE><figure><img height="240" src="https://miro.medium.com/max/240/1*wSwN4ndAgcVW5g1NGXpxVg.png" width="240"><figcaption dir="auto">Big and small Marios [Super Mario Maker 2 2019]</figcaption></figure>This might be enough for others to understand, especially if they’ve played a 2D Mario game before, but it poses several questions. How does Mario eat a mushroom? What does it mean for Mario to be big or small? How can Mario take damage? When you need to start examining the underlying mechanics, the framework comes in handy.We can break out the mechanics into their elements, beginning with big or small. Mario’s size indicates how many hits he can take before he dies (quantity) — 2 when big, 1 when small. His size also affects how tall he is when he is standing (spatial) — 2 blocks vs 1 block. And because his size adds an additional rule to the player, i.e. they cannot grow any bigger while big, we can consider it to be a state mechanic as well.Eating a mushroom and taking damage are mechanically very similar. First off, they are action mechanics: they change Mario’s state from small to big or big to small to dead. And second, they both require another entity to collide with Mario (spatial). What differentiates gaining health and taking damage depends on what that other spatial entity is. If it’s a mushroom, Mario will become big; if it’s an enemy, Mario will take damage.<figure><img height="203" src="https://miro.medium.com/max/838/1*GZHbUECpRXw5RMbUCKn9Fg.gif" srcset="https://miro.medium.com/max/276/1*GZHbUECpRXw5RMbUCKn9Fg.gif 276w, https://miro.medium.com/max/552/1*GZHbUECpRXw5RMbUCKn9Fg.gif 552w, https://miro.medium.com/max/640/1*GZHbUECpRXw5RMbUCKn9Fg.gif 640w, https://miro.medium.com/max/700/1*GZHbUECpRXw5RMbUCKn9Fg.gif 700w" width="569"><figcaption dir="auto">Changes in Mario’s state [Super Mario Maker 2 2019]</figcaption></figure>Using the framework to break down the health system in a 2D Mario game gives us this summary:<BLOCKQUOTE>Big or small are state mechanics that (1) apply to Mario, (2) visually represent Mario’s health points (quantity), and (3) affect how tall Mario is when he is standing (spatial). When Mario collides with another entity (spatial), that entity may change Mario’s health state to big, to small, or to dead (action).</BLOCKQUOTE>Being able to convert metaphors into mechanics is an important skill to have when analyzing systems. Mario’s health may appear to be straightforward on its surface, but by using the framework, it becomes clear how Nintendo was able to innovate. It is not purely a quantity-based system, where a number counts up and down. It’s a system that affects Mario’s size which affects whether or not he can run through a 1 block gap, or whether that fireball would’ve instead passed over his head if he were small.This breakdown does not cover all aspects of the system. Obviously, it does not examine other power-ups like the flower. However, there is still analysis to be had on what’s here. For example, how is the spatial problem solved where Mario is still colliding with an enemy immediately after taking damage? Does Mario get hit again? Using the 4 elements will help you find answers to these questions.In a future post, I may explore my other uses for this framework such as how to use it to come up with new mechanics for existing systems. But in the meantime, let me know what you think here or on <a href="https://twitter.com/stephentrinha" rel="noopener nofollow" dir="ltr">Twitter</a>! I’m always trying to improve it.-- Stephen Trinh (<a href="https://twitter.com/stephentrinha" dir="ltr">@stephentrinha</a>)<h3>Related Jobs</h3><img src="https://d1506sp6x4e9z7.cloudfront.net/gamasutra/uploads/AU358.gif" alt="Sucker Punch Productions" width="120" height="101"><div dir="ltr">
 
 Sucker Punch Productions — 
 Bellevue,
 Washington,
 United States
 
 [05.14.21]
 
 
 <a href="https://jobs.gamasutra.com/job/senior-systems-designer-bellevue-washington-34936" dir="ltr">Senior Systems Designer</a>
 </div><img src="https://d1506sp6x4e9z7.cloudfront.net/gamasutra/uploads/AU358.gif" alt="Sucker Punch Productions" width="120" height="101"><div dir="ltr">
 
 Sucker Punch Productions — 
 Bellevue,
 Washington,
 United States
 
 [05.14.21]
 
 
 <a href="https://jobs.gamasutra.com/job/senior-games-writer-bellevue-washington-34938" dir="ltr">Senior Games Writer</a>
 </div><img src="https://d1506sp6x4e9z7.cloudfront.net/gamasutra/uploads/AU358.gif" alt="Sucker Punch Productions" width="120" height="101"><div dir="ltr">
 
 Sucker Punch Productions — 
 Bellevue,
 Washington,
 United States
 
 [05.14.21]
 
 
 <a href="https://jobs.gamasutra.com/job/combat-designer-bellevue-washington-34946" dir="ltr">Combat Designer</a>
 </div><img src="https://d1506sp6x4e9z7.cloudfront.net/gamasutra/uploads/AU358.gif" alt="Sucker Punch Productions" width="120" height="101"><div dir="ltr">
 
 Sucker Punch Productions — 
 Bellevue,
 Washington,
 United States
 
 [05.14.21]
 
 
 <a href="https://jobs.gamasutra.com/job/senior-concept-artist-bellevue-washington-34947" dir="ltr">Senior Concept Artist</a>
 </div>

A technical framework for understanding game mechanics in systems.

entertainment

Entertainment

product

Product & Design

As the subtitle states, this is a framework for a technical understanding of game mechanics in systems — not so much a creative one. I’ve been developing it while working on design documents for various projects, and I feel like it might be useful other designers out there. Its purpose is to help analyze mechanics and give an organized format for breaking down mechanics into their most basic forms. I use it most often when I need to write up comprehensive docs for a game mechanic or system. I also use it to develop new mechanics for an existing system.

There are 4 elements of game mechanics: quantity ,spatial ,state , andaction . The following chart defines each of them and provides some examples of each. After the chart is an application of the framework using 2D Mario games.

To demonstrate how you might use this framework, let’s say that we’re writing up the documentation for the health system in a 2D Mario game. We can start with the metaphor, as that’s always the most visible aspect:

Mario turns big when he eats a mushroom. When Mario is big, if he takes damage, he turns small, and when Mario is small and he takes damage, he dies.

This might be enough for others to understand, especially if they’ve played a 2D Mario game before, but it poses several questions. How does Mario eat a mushroom? What does it mean for Mario to be big or small? How can Mario take damage? When you need to start examining the underlying mechanics, the framework comes in handy.

We can break out the mechanics into their elements, beginning with big or small. Mario’s size indicates how many hits he can take before he dies (quantity ) — 2 when big, 1 when small. His size also affects how tall he is when he is standing (spatial ) — 2 blocks vs 1 block. And because his size adds an additional rule to the player, i.e. they cannot grow any bigger while big, we can consider it to be a state mechanic as well.

Eating a mushroom and taking damage are mechanically very similar. First off, they are action mechanics: they change Mario’s state from small to big or big to small to dead. And second, they both require another entity to collide with Mario (spatial ). What differentiates gaining health and taking damage depends on what that other spatial entity is. If it’s a mushroom, Mario will become big; if it’s an enemy, Mario will take damage.

Using the framework to break down the health system in a 2D Mario game gives us this summary:

Big or small are state mechanics that (1) apply to Mario, (2) visually represent Mario’s health points (quantity ), and (3) affect how tall Mario is when he is standing (spatial ). When Mario collides with another entity (spatial ), that entity may change Mario’s health state to big, to small, or to dead (action ).

Being able to convert metaphors into mechanics is an important skill to have when analyzing systems. Mario’s health may appear to be straightforward on its surface, but by using the framework, it becomes clear how Nintendo was able to innovate. It is not purely a quantity-based system, where a number counts up and down. It’s a system that affects Mario’s size which affects whether or not he can run through a 1 block gap, or whether that fireball would’ve instead passed over his head if he were small.

This breakdown does not cover all aspects of the system. Obviously, it does not examine other power-ups like the flower. However, there is still analysis to be had on what’s here. For example, how is the spatial problem solved where Mario is still colliding with an enemy immediately after taking damage? Does Mario get hit again? Using the 4 elements will help you find answers to these questions.

In a future post, I may explore my other uses for this framework such as how to use it to come up with new mechanics for existing systems. But in the meantime, let me know what you think here or on <a href="https://twitter.com/stephentrinha">Twitter </a>! I’m always trying to improve it.

-- Stephen Trinh (<a href="https://twitter.com/stephentrinha">@stephentrinha </a>)

Gamasutra: Stephen Trinh's Blog - The 4 Elements of Game Mechanics

4 Elements of Game Mechanics

Hanung Purwaka's ideas are part of this journey:

Related collections

Similar ideas