On this page
- Game Rules and Mechanics in 60 Seconds
- What Are Game Mechanics?
- Core Mechanics and the Core Game Loop
- Game Mechanics Examples by Genre
- Mechanics, Dynamics and Aesthetics in Game Design
- How to Write a Game Mechanic Down
- Testing and Tuning Mechanics With Players
- Where Game Design Courses Teach Mechanics
- Game Jobs That Design and Build Mechanics
- Frequently Asked Questions
- Related Pages
- Sources
Game Rules and Mechanics in 60 Seconds
- A mechanic is a rule the player acts through. Find the verb. Jumping, drawing a card and reloading are mechanics, and a sword is not. Even game schools say there is no single agreed definition. Definition ›
- The core loop has to be fun first. Core mechanics are the actions players perform most often. The loop adds the reward that sends them back, and extra content can't rescue a dull one. Core Loop ›
- A mechanic spec answers seven questions. The action, the input, the rule, the numbers, the feedback, the edge cases and the decision it creates. Name every number so a designer can tune it without code. Writing It Down ›
- Cutting mechanics is a skill courses teach. MIT's game design course gave a whole session to adding and cutting mechanics. Each one costs build and balance time and asks players to learn something. Testing ›
- Game design programs teach mechanics first. DePaul's GAM 102 covers core mechanics and loops, and MIT's CMS.608 opened with a one-mechanic assignment. Courses often start with paper prototypes before code. Our data covers 354 programs. In School ›
Heads up The genre examples describe typical play, and individual games mix and change these mechanics.
What Are Game Mechanics?
A game mechanic is a rule that lets the player do something, together with the way the game responds. Jumping is a mechanic. So is the rule that a jump is higher if you hold the button longer, and the rule that landing on an enemy defeats it. Drawing a card, spending gold, placing a worker, reloading a weapon and hiding in tall grass are all mechanics. Each one has an action, a rule about what that action does, and feedback that tells the player it worked.
There is no single agreed definition, and game schools say so. Champlain College's guide to game mechanics points out that researchers haven't settled what mechanics include. In practice, designers use a simple test: find the verb. If the player can do it, or the game does something because the player did it, it is a mechanic. A sword is not a mechanic. Swinging it, and the rule for how much damage a swing does, are.
O*NET, the Labor Department's job database, uses the word in its description of what video game designers do. One task it lists is to "create core game features, including storylines, role-play mechanics, and character biographies for a new video game or game franchise." Another is to develop and maintain design level documentation, including mechanics, guidelines, and mission outlines. Mechanics are part of the official description of the job, alongside missions and story.
Mechanics, Rules and Systems
The three words overlap and people use them loosely, so it helps to pin them down. A rule is any statement about how the game works, including ones the player never touches, such as how fast a day passes. A mechanic is a rule the player acts through. A system is several mechanics working together, such as a crafting system made of gathering, recipes and an inventory limit. When a designer says a system feels shallow, they usually mean its mechanics don't create enough decisions.
What Makes a Mechanic Good
A good mechanic gives the player a choice that matters. Jumping is interesting because the timing and the distance are up to you, and a wrong guess costs something. A mechanic that always has one right answer stops being a decision and turns into a chore. Good mechanics are also easy to read: the player can see what happened and why, and can try again with a better plan.
The center of the gameCore Mechanics and the Core Game Loop
Most games have dozens of mechanics, but only one or two carry the game. These are the core mechanics, and Champlain's guide describes them as the actions the player performs most often. In a platformer that is moving and jumping. In a shooter it is aiming and firing. In a card game it is drawing and playing cards. Everything else in the game supports the core mechanic, gives it variety or rewards using it well.
The core loop, also called the core gameplay loop, is the core mechanic plus the reason to keep doing it. A typical loop has three steps: the player acts, the game rewards the action, and the reward makes the next action more interesting. Fight an enemy, earn experience, get stronger, fight a harder enemy. Mine ore, craft a better pick, reach deeper ore. The same guide is blunt about the stakes: if the core loop isn't enjoyable, the rest of the design can't rescue the game. Bigger games stack loops on different timescales: a gameplay loop that lasts seconds, such as a single fight, inside one that lasts minutes, such as clearing an area, inside one that lasts hours, such as finishing a chapter and upgrading your character.
Game programs teach this early. DePaul University's GAM 102, Mechanics of Game Design, is a course on designing and building core mechanics and game loops for real-time games. Students also study existing games to review and repurpose their mechanics, which is how many new mechanics start: an old one with one rule changed.
Primary and Secondary Mechanics
Designers often split mechanics into primary ones, which the player uses all the time, and secondary ones, which change how the primary ones work. Jumping is primary. A double jump, a wall jump or a jump pad is secondary. Secondary mechanics are where most of a game's variety comes from, and they are also where scope grows fastest, because each new one has to work with every mechanic already in the game.
ExamplesGame Mechanics Examples by Genre
Genres are largely defined by their mechanics. City College of New York's Games and Their History course teaches exactly this: how mechanics combine to form a genre. The table lists the core mechanic of common video game genres, a few supporting mechanics, and the decision each one asks the player to make.
| Genre | Core mechanic | The player decides |
|---|---|---|
| Platformer | Run and jump | When and where to jump |
| Shooter | Aim and fire | Which target, and when to reload |
| Role-playing | Fight and grow stronger | How to build the character |
| Strategy | Gather and spend resources | What to build first |
| Puzzle | Move pieces under fixed rules | Which move opens the next one |
| Survival | Gather and craft | What to risk on each trip out |
| Racing | Steer and control speed | How fast to take each turn |
| Roguelike | Short runs that end in death | What to risk before the run ends |
Read across a row and you can see why mechanics matter more than setting. A survival game set in space and one set in a forest play the same way if they share gathering, crafting and hunger. Change one mechanic, for example by making death permanent, and the same game feels completely different, because every decision now carries more weight.
Board Game Mechanics
Board games make mechanics easy to see, because every rule is written down and played out by hand. That is why game design courses start with them. Common board game mechanics include:
- Dice rolling, where chance decides an outcome and players manage the risk.
- Worker placement, where each player claims a limited number of actions and blocks others from taking them.
- Deck building, where players start with weak cards and buy better ones over the game.
- Card drafting, where players pick cards from a shared set and pass the rest on.
- Area control, where players compete for spaces on a map.
- Set collection and trading, where value comes from matching cards and from deals with other players.
Many video games use these directly. Deck building and drafting are common in digital card games, and worker placement shows up in management and strategy games. Learning board game mechanics is a cheap way to build a library of mechanics you can reuse, which is one reason the course work below starts on paper.
Mechanics, Dynamics and Aesthetics in Game Design
A mechanic on its own isn't the experience. What players feel comes from mechanics in motion: many players, many choices, and the game responding over time. Designers often use the mechanics, dynamics and aesthetics framework to keep those layers apart, and MIT's game design course gave it a full session. Mechanics are the rules the designer writes. Dynamics are the behavior that comes out when people play by those rules. Aesthetics are the feelings that behavior produces, such as tension, discovery or the satisfaction of a plan working.
The framework explains why designers can't simply write in a feeling. You can't add tension directly. You can add a mechanic, such as a timer or limited ammunition, test whether it produces tense play, and adjust it until it does. Players meet the game from the other end: they feel the aesthetics first and may never notice the mechanics underneath.
It also explains surprises. Players often find dynamics the designer didn't plan, from clever strategies to exploits that break the game. Some become part of the game's appeal. Others are bugs. Testing is how a team finds out which is which before players do.
On paperHow to Write a Game Mechanic Down
A mechanic isn't finished until it is written so that a programmer can build it and a tester can check it. O*NET lists documentation as part of a game designer's job, including documenting mechanics. A clear mechanic spec usually answers seven questions:
- What does the player do? The action, in one sentence, starting with a verb.
- How do they do it? The input: which button, card or move triggers it.
- What is the rule? Exactly what happens, including any conditions, such as "only while touching a wall."
- What are the numbers? Height, damage, cost, cooldown. Name each one, so a designer can tune it without changing code.
- What is the feedback? What the player sees, hears and feels when it works and when it fails.
- What are the edge cases? What happens at the edge of a platform, with zero resources or when two mechanics fire at once.
- Why does it exist? The decision it creates for the player. If you can't answer this, the mechanic may not belong in the game.
Keep each spec short, and keep all of them in one place. The game design document guide shows how a mechanics section fits into a full document and what studios and teachers expect to see in it. A spec this short is also easy to test: a tester can check each line, and a programmer can tell you which edge cases are expensive before you commit to them.
In playTesting and Tuning Mechanics With Players
A mechanic is a guess until people play it. Designers test mechanics the same way at every level, from a class project to a commercial game: build the smallest version that works, watch someone play it without help, write down what confused or bored them, change one thing, and test again. O*NET's first listed task for video game designers is to balance and adjust gameplay experiences to ensure the critical and commercial success of the product, and that tuning is mostly done through this cycle.
The cheapest test is on paper. A board game version of a combat system, made with index cards and dice, can show in an afternoon whether the choices are interesting. Digital prototypes come next, with placeholder art, so nobody hesitates to throw a mechanic out. City College's senior project course starts the capstone this way, with teams prototyping their core mechanics and testing their key assumptions before full production.
Cutting Mechanics
Adding mechanics is easy. Removing them is the harder skill, and MIT's course spent a session on it. Every mechanic costs time to build, test and balance against every other mechanic, and each one asks the player to learn something. A mechanic that rarely changes a decision, or that players ignore, usually makes the game worse by being there. Designers who can explain why they cut something are easier to hire than those who can only list what they added.
Tuning Numbers
Most of the time spent on a mechanic goes into its numbers rather than its rules. A jump that is a little too high makes levels trivial. A weapon that reloads a fraction of a second too slowly feels broken. That is why the spec names every value: designers change them between playtests, often many times a day, while the code stays the same.
Where Game Design Courses Teach Mechanics
Mechanics are usually the first thing a game design program teaches, and the courses look similar from school to school. City College of New York's Game Design Fundamentals introduces mechanics, difficulty, meaningful choice and system design. DePaul's GAM 102 covers core mechanics and loops. MIT's CMS.608 Game Design has students design, build and test their own games to understand how game rules interact and change, and its published calendar for Spring 2014 shows how a term is built around mechanics.
| Session | Topic |
|---|---|
| 1 | Assignment One, Single Mechanic |
| 2 | Meaningful decisions in gameplay |
| 3 | Altering rules and playtesting |
| 4 | Mechanics, dynamics and aesthetics |
| 14 | Adding and cutting mechanics |
The pattern is worth knowing if you are choosing a school or teaching yourself. Start with one mechanic, make sure it creates real decisions, test it with people, then learn to add and cut. The game design classes guide lists the courses ranked programs require, and how to make a video game walks through the same steps outside school. If you're comparing programs, our data covers 354 programs at 271 colleges, and the best game design schools ranking is the place to start.
CareersGame Jobs That Design and Build Mechanics
Mechanics are a team effort. A designer writes the rules, a programmer builds them, a level designer puts them in front of the player, and a tester finds where they break. The table shows each job's part and the federal pay for the occupation that counts it.
| Job | Median pay |
|---|---|
| Video game designer | $104,000 |
| Level designer | $104,000 |
| Game programmer | $135,980 |
| Game tester | $104,300 |
Game designers are counted with web and digital interface designers at $104,000, and game programmers with software developers at $135,980. Treat these as the market for each skill rather than a studio pay scale. The video game designer career guide covers how people get hired to design mechanics, and a portfolio that shows one mechanic tested and improved over several versions is one of the strongest things you can bring.
Showing Mechanics in a Portfolio
Hiring designers want to see how you think, not only the finished game. For one mechanic, show the short spec, the first playable version, what playtesters did with it, and what you changed as a result. Include a mechanic you cut and say why. A page like that proves you can write a rule, test it with people and improve it, which is most of the job. The game design portfolio guide covers how to present it for school applications and for studios.
Frequently Asked Questions
What Are Game Mechanics?
Game mechanics are the rules and actions a game gives the player and how the game responds to them: jumping, shooting, trading, drawing a card, building a wall. A useful test is the verb. If the player can do it, or the game does something because the player did it, it is a mechanic. Even game schools admit there is no single agreed definition, which is why designers judge a mechanic by what it lets the player decide. See the definition.
What Is a Core Mechanic?
A core mechanic is the action the player performs most often, the one the rest of the game is built around. In a platformer it is jumping, in a shooter aiming and firing, and in a deck-building game drawing and playing cards. The core loop is that mechanic plus the reward that sends the player back to it. If the loop isn't fun, extra content won't fix it, so designers build and test it first. See core mechanics and loops.
What Are Some Examples of Game Mechanics?
Common examples include jumping and wall-jumping in platformers, aiming, reloading and taking cover in shooters, skill trees and inventory in role-playing games, crafting and hunger in survival games, and resource gathering in strategy games. Board games have their own set, such as dice rolling, worker placement, deck building, card drafting and area control. The genre table on this page lists the core mechanic of each genre and the decisions it asks of the player. See examples by genre.
How Do You Write the Mechanics of a Game?
Write each mechanic as a short spec: the player's action and the input that triggers it, the rule for what happens, the numbers that control it, the feedback the player sees and hears, and the edge cases. Then say why the mechanic exists, meaning which decision it creates for the player. Keep the numbers as named values a designer can tune without a programmer, and keep the spec in the game design document. See how to write a mechanic.
Do You Learn Game Mechanics in a Game Design Degree?
Yes. Mechanics are usually the first thing a game design program teaches. DePaul has a course named Mechanics of Game Design, City College of New York's first game design course covers mechanics and meaningful choice, and MIT's game design course opened with an assignment built on one mechanic. Courses often teach them with paper prototypes and playtests before students write any code. Our data covers 354 game design and development programs. See how courses teach them.
Sources
- 1 MIT OpenCourseWare, CMS.608 Game Design, Spring 2014, calendar Course titles, descriptions and definitions, paraphrased from the page. Accessed .
- 2 MIT OpenCourseWare, CMS.608 Game Design, Spring 2014, syllabus Course titles, descriptions and definitions, paraphrased from the page. Accessed .
- 3 DePaul University catalog, Game Development (GAM) courses Course titles, descriptions and definitions, paraphrased from the page. Accessed .
- 4 City College of New York, Digital Game Development course descriptions Course titles, descriptions and definitions, paraphrased from the page. Accessed .
- 5 Champlain College Online, Game Mechanics 101 Course titles, descriptions and definitions, paraphrased from the page. Accessed .
- 6 O*NET OnLine, 15-1255.01 Video Game Designers Tasks quoted and paraphrased. Accessed .
- 7 BLS, Occupational Employment and Wage Statistics, May 2025 National median pay for the occupation that counts each game job. Accessed .