A game is a set of rules that talk to each other
Most people describe games by their surface: a jump button, a sword, a map, a shop. Designers and analysts often describe them differently, as a collection of systems. A system, in this sense, is a group of rules that takes some inputs, changes some values, and produces outputs. Movement is one. Combat is another. A shop, an inventory, a quest log and an enemy spawner are all systems too.
On their own, most of these are simple. What makes a game interesting is how they connect. The output of one system becomes the input of another, and the result is often more varied than anyone could list in advance. This idea is sometimes called systems thinking, and it is a useful way to understand why a game feels the way it does.
The basic parts of a system
Almost any game system can be described with the same few ingredients.
- State: the values the system keeps track of, such as health, gold, position, or whether a door is open.
- Rules: the logic that says how state may change, for example “taking damage lowers health, and zero health means defeat.”
- Inputs: what the player or other systems feed in, such as a button press or an enemy attack.
- Outputs: what comes out, such as a changed number, a sound, an animation or a new situation.
- Feedback: information shown back to the player so they can judge what happened and decide what to do next.
Thinking this way makes it easier to compare very different games. A health bar, a stamina meter and a hunger gauge are all state with rules attached. What differs is what the game lets those values do to each other.
How separate systems combine
Imagine a simple action game with only three systems. Movement lets you run and dodge. Combat lets you hit enemies and be hit. Stamina limits how often you can dodge or swing. None of these is complicated, but together they create a small set of decisions: do you attack now, or hold back to keep enough stamina to dodge?
Add a fourth system, such as enemies that react to how much health you have left, and the decisions shift again. Nobody wrote a rule that says “be cautious when stamina is low and enemies are aggressive,” yet that situation arises from the interaction. Designers often call behavior like this emergent: it comes from the combination, not from any single rule.
This is also why games with fairly small rule sets can stay interesting for a long time. Many strategy and puzzle games rely on a handful of rules that interact in many ways.
Feedback loops
Some of the most important connections in a game are loops, where the output of a system feeds back into its own input. Designers usually describe two broad kinds.
A positive loop amplifies itself. If winning a fight gives you better equipment, and better equipment makes the next fight easier, an early lead can grow. This can feel exciting, but it can also make a game feel decided too soon.
A negative loop pushes back. If falling behind gives you a small catch-up bonus, or if stronger opponents get tougher defenses, the game tends to pull results toward the middle. This can keep contests close, though if it is too strong it may feel like effort is not rewarded.
Many games blend both. Whether a particular blend feels fair is partly a matter of taste and partly a matter of testing, and it is rarely settled by theory alone.
Systems that most games share
Although every game is different, a few families of systems show up again and again. Each of them is covered in more detail elsewhere in this cluster, so this is only a map.
Saving and checkpoints decide how much progress a player can lose, which shapes how cautiously they play. Random rewards use tables of chances to decide what a player finds, and they connect to the way players judge fairness. Economies track how resources enter and leave the game, which affects what rewards are worth. Physics applies simplified rules to movement and collisions so the world behaves consistently. Progression paces the game through levels, unlocks and new abilities. Procedural generation lets code build levels from rules and seeds. Character builds let players specialize by choosing among branching options.
Each of these can be designed on its own, but a designer usually has to think about all of them together. A generous drop table combined with a weak money sink can quietly flatten an economy. A harsh save system combined with a long, unskippable stretch can turn a challenge into a chore.
Why designers care about interactions
A change to one rule rarely stays local. Making a weapon slightly stronger can change which builds players choose, which changes how enemies need to be tuned, which changes how quickly players progress. That is part of why teams build a game prototype early, so they can see how the pieces behave together before committing to content around them. It is also why quality assurance and playtesting matter: testers often find combinations that the people who wrote the rules did not anticipate.
Online games make this even more visible. When a balance change lands, players adjust, and the game meta shifts in response. Developers then read how the community behaves and adjust the rules again. In that sense, the players themselves become part of the system.
Reading a game as a set of systems
You do not need design training to try this. Pick a game you know and ask a few plain questions.
- What numbers does the game track, and which of them can I affect?
- What rules change those numbers?
- Where does one system feed another?
- Where do I see feedback, and how quickly?
- Which loops reinforce my progress, and which push back?
The answers often explain things that were hard to put into words, such as why a game feels tense, generous, grindy or forgiving. They also make it easier to see what a patch note really changes. When a change to one rule is announced, the interesting question is usually which connected systems will respond.
Systems thinking does not tell you whether a game is good. It gives you vocabulary for noticing how the parts relate, and that tends to make the rest of the topics in this cluster easier to follow.