Character Design in Games: Mechanics Should Emerge from the Character

1. The Core Problem: Where Do Mechanics Come From?

In game character design, there has long been a fundamental disagreement: should a character’s skills and stats first be derived from the character’s personality and logic, or should they first be determined by a balance sheet? The first approach treats the character as a person with internal logic, where mechanics are a natural extension of who that character is. The second treats the character as a container for an attribute table, where skills are simply materials used to fill in the empty cells.

Characters created by these two approaches may look similar in the data, but they can feel completely different to players. With the first approach, players can accept a loss and think, “That makes sense.” With the second, players may feel that they lost only because they were countered. This article argues that a character’s mechanics should be an answer to “Who is this character?”, not a product of the balance table.

2. The Core Principle: Mechanics Are the Character’s Answer

A successful character is one where every ability can answer the same question: “Who is this person?”

Take a close-range grappling character as an example. The character is extremely dangerous at close range not because a design formula says, “Close-range characters should be strong up close,” but because in the character’s setting, they are the finest grappling expert among similar characters. Close-quarters grappling is their home arena. When a player charges into their attack range hoping to gain an advantage, the frustration is reasonable—you have willingly stepped into someone else’s home arena. Once this logic works, the mechanics have a soul: what defeats you is not a number, but a person.

Now consider a controller or strategist character. Suppose they have an extremely fast light attack. Judged only by the numbers, this may feel inconsistent: why would a character known for strategy and ranged tools have such fast strikes? But if we step back and ask who they are: they are the hidden manipulator who toys with the entire battle. Spells and traps are merely tools; the character themselves is the real weapon. They do not need to rely only on long-range methods because close combat is equally lethal for them. Their ranged skills force the opponent into a difficult choice, but the character themselves is what truly finishes the fight.

Once this character logic is understood, the fast strikes become completely reasonable. They may even feel inevitable: this is simply the only kind of character they can be. This is the essential difference between mechanics derived from character and mechanics derived from a table.

3. The “Moat” Effect: Endogenous Defense

Good character design essentially creates an endogenous defensive structure. The character’s weaknesses are not manually patched by the designer; they are surrounded on all sides by the character’s own strengths. When an opponent tries to attack through a weakness, they often discover that the position has already fallen within the character’s range.

This matches the logic of top performers in the real world: the best people are not without weaknesses. Their strengths have simply become so dominant that opponents cannot go around them to attack the weaknesses. The more you try to attack their weakness, the more you are forced into the area where they are strongest.

A simplified model of this structure looks like this:

Strengths → cover → weakness entry → force the opponent in → within strength range

In design terms, this means weaknesses and strengths should be spatially coupled, not isolated from one another. An isolated weakness is exposed and easy to punish. A coupled weakness always remains within the protective radius of the character’s strengths.

4. Anti-Pattern: Why Quota-Driven Design Fails

The opposite of character-driven mechanics is a common failure mode: first create the table, then fill in the mechanics.

The process usually goes like this: the designer first defines an attribute table—“this character should be strong in A and weak in B”—and then reverse-engineers skills to satisfy every quota in that table. As a result, each skill merely fulfills an indicator instead of answering “Who is this character?”

// Anti-pattern: fill mechanics from the quota first
function designByQuota(role):
    table = { Attack: "Medium", Defense: "Low", Mobility: "High" } // The balance table comes first
    for attr in table:
        role.addSkill(fillQuota(attr)) // Skills exist only to fill quotas
    return role // Players see a set of attributes, not a person
// Better pattern: define the character first, then derive mechanics
function designByIdentity(character):
    identity = character.who() // Who they are: the strongest close-range grappler
    arena = identity.homeAdvantage() // Their home arena: close-range grappling
    skills = deriveSkills(identity) // Every skill answers "who they are"
    weakness = deriveWeakness(identity) // Weakness is derived naturally and protected by strengths
    return Character(skills, weakness) // The player faces a person

The direct consequence of quota-driven design is that players do not perceive a character. They perceive a group of attributes. When a match is lost, the defeat is blamed on “stat suppression” or “attribute counters” rather than “my opponent executed their logic better.” This kind of experience is less memorable and also makes players less likely to want to play again.

5. From Character to Match: The Compounding Value of Design Philosophy

The value of character-driven mechanics is not limited to individual characters. It also affects the quality of matches.

When both sides are characters with real internal logic, each pushing their own identity to the extreme, a match becomes a collision between two combat philosophies. Victory no longer depends only on who has higher stats or who counters whom. It depends on who executes their own logic more thoroughly. Such a result is meaningful enough to discuss, worth reviewing, and likely to make players want another match—because it rewards understanding, judgment, and execution, rather than combinations of attribute tables.

This creates a compounding effect in design: the “soul” of an individual character accumulates into the “depth” of the match system.

6. A Practical Design Checklist

To turn these principles into actionable practice, the following review checklist and process can be used:

1. Identity first: Before designing any skill, write one sentence explaining who the character is and where their home advantage lies. If you cannot write this sentence, the character is not yet fully formed.
2. Derive mechanics backward: Check every skill to see whether it can be explained as “because they are this kind of character, they behave this way.” Skills that cannot be explained are often quota fillers.
3. Validate weakness coupling: Confirm that the character’s weaknesses lie within the protective radius of their strengths, avoiding exposed weaknesses.
4. Run the attribution test: Imagine losing a match and ask whether players will blame the loss on the opponent executing better, or on being countered by attributes. The former passes; the latter needs rework.
5. Check philosophical consistency: Verify that the entire skill set points to the same combat philosophy, avoiding contradictions that dilute the character’s identity.

7. Conclusion

One sentence summarizes this methodology: Good designers create characters for players to compete with; poor designers create indicators and turn characters into disposable competitive material.

More concerning, poor design often believes it is correct—because in the short term, its key indicators may indeed be rising. The problem is that when the soul of a game disappears, the reports usually do not show it. Restoring mechanics to the answer of the character, and returning weaknesses to be guarded by the character’s own strengths, is the fundamental way to keep characters and the work itself alive in the long term.