Imagine a companion spending their last healing charge on the player, then insisting it was simply efficient resource management. In a few seconds, that interaction can suggest competence, concern, and a reluctance to admit affection.
For a developer, this is a useful unit of character design: a situation, a decision, and enough feedback for the player to interpret it.
A character sheet might describe someone as proud, generous, or anxious. The production question is what those words change when the game is running. Which opportunity do they take? What do they sacrifice? How does the player notice?
A practical approach is to design personality as a pattern of priorities that players can learn, then give those priorities situations that make them matter.
We first need to be precise about “appeal.” Recognizing a character, understanding their motives, and caring about them are different outcomes. A distinctive silhouette can help with recognition. A readable decision can reveal a motive. Attachment depends on the kind of relationship the player develops.
In a qualitative survey of 213 players, Julia Ayumi Bopp and colleagues identified seven forms of emotional attachment to game characters, including excitement about gameplay competence, admiration, and concern for a character's well-being. These were accounts of players' experiences, so the findings describe different kinds of attachment rather than establish a recipe that causes it. Exploring Emotional Attachment to Game Characters, CHI PLAY 2019
That distinction changes a design brief. “Make this character lovable” leaves too many decisions unresolved. “Make players admire her skill while noticing how hard she finds accepting help” gives animation, combat, and writing something specific to work with. It also leaves room for players who understand her perfectly and still dislike her.
Choose the relationship you want to invite, then design the evidence players will encounter.
The MDA framework offers a useful bridge here. Hunicke, LeBlanc, and Zubek distinguish the rules and algorithms of a game, the behavior that emerges during play, and the emotional experiences those interactions produce. In their terminology, “aesthetics” concerns the player's experience, beyond visual style. MDA, 2004
Applied to character design, that suggests a working sequence:
Priority → choice under pressure → cost → visible response → later consequence
This sequence is a proposed design tool. Its purpose is to turn an adjective into something a team can implement and a player can interpret.
Consider Mara, a hypothetical companion who takes pride in fighting fairly but cares deeply about her partner.
| Situation | Mara's choice and cost | Evidence the player sees |
|---|---|---|
| A rival loses their weapon during a duel | She lets them recover it, giving up an opening. | She lowers her blade and steps back. |
| Her partner is endangered during that duel | She abandons the duel to help, surrendering the contest. | Her attention shifts immediately; the formal stance disappears. |
| Her partner later saves her | She accepts help despite discomfort with dependence. | A brief hesitation precedes a direct, quiet thank-you. |
The second decision gives the first one more meaning. Fairness matters to Mara, and her partner matters more. The change follows a priority the player can discover.
This is a useful way to write complexity: place two understandable values in conflict, then make the resolution observable. An exception becomes revealing when players can explain why it happened.
Cost matters because a choice says more when alternatives are plausible. A generous companion who gives away an unlimited resource reveals less than one who shares something scarce. The cost can be small: time, convenience, status, or the discomfort of asking for help. It does not need to become a dramatic sacrifice in every scene.
There is also a production constraint. A personality trait can create real friction for the person playing. If Mara repeatedly wastes scarce resources or causes mission failures, players may understand her priorities and still leave her at camp. Put the expressive cost where the intended experience can support it. A short hesitation, a changed stance, or a voluntary side interaction may communicate pride without turning routine assistance into a chore.
For a player-controlled character, decide how much behavior the player authors. A tightly authored protagonist can have explicit boundaries. A role-playing avatar may need dialogue options, incentives, and expressive moves that allow the player to choose those priorities. Automatically refusing an action can undermine a game that otherwise promises broad control.
The same personality also needs a readable performance. Joseph Bates's foundational work on believable agents draws on animation practice to argue that appropriately expressed emotion helps create an impression of life. An internal emotional state needs outward expression that an audience can perceive. The Role of Emotion in Believable Agents, 1994
For Mara, that means a hidden acceptedHelp flag accomplishes little by itself. The player needs a cue at the moment it matters: a glance toward her partner, a change in posture, or a line delivered after the action has settled. Several simultaneous effects may bury the very response that carries the character.
A small implementation can therefore begin with one tracked event, one later response, and a clear opportunity to notice the connection. Additional dialogue becomes useful when it adds another interpretation or relationship change.
Visual design and mechanics can also shape each other during development. In his account of D.Va's creation, Overwatch lead writer Michael Chu explains that the team iterated on the relationship between pilot and mech. He also describes an early cat theme becoming a bunny motif after the Boosters ability suggested a bunny hop. D.Va Deconstructed, 2018
That example suggests a practical habit: revisit the visual concept after the character's movement feels good. A movement pattern can suggest a motif, posture, rhythm, or attitude that the original concept never anticipated. The resulting coherence is something a team can discover through iteration.
Memory adds another layer, and some of it belongs to the player.
Ubisoft's retrospective on Watch Dogs: Legion describes the difficulty of writing a fixed personal arc when playable characters could be recruited, replaced, or lost. Recurring authored allies and villains anchored the story. Recruitment missions supplied personal episodes; the designers hoped players would remember these events and interpret later dialogue through them, even when the dialogue itself did not acknowledge what happened. How Watch Dogs: Legion Told a Story Without a Main Character, 2023
For a small team, this suggests a useful possibility. A shared experience can give a recurring interaction meaning even when the dialogue system is modest. An offer of help may feel different after a character has once refused it.
Choose where explicit acknowledgment is necessary. If the game creates a strong expectation that someone will remember a major event, an unchanged response may break the relationship. Smaller gestures can carry continuity with much less state. Decide which moments need the game to remember, and which ones the player will bring with them.
To test this approach, build a short encounter before expanding the biography. Remove the trait descriptions from the test instructions and watch what players infer.
Three prompts can separate problems that a single “Did you like the character?” question would hide:
- “What do you think mattered to this character?” Ask for the action that led to that interpretation. This checks whether the intended priority was legible.
- “What do you expect them to do in this new situation, and why?” Change the circumstances while preserving the underlying conflict. Look for a coherent explanation; players do not need to predict one exact animation.
- “Which moment stayed with you, and how did you feel about it?” Ask after another activity. This helps distinguish immediate recognition from a moment the player actually remembers.
Then ask whether any behavior made the character unpleasant to play with. A companion can be distinctive, understandable, and exhausting at the same time. Treat that as a design finding.
These prompts are a prototype workflow, not a validated attachment scale. Their value is diagnostic: they help a team locate a gap between intention, visible behavior, and player interpretation.
For an initial character prototype, try one central priority, one competing value, three situations, and one later acknowledgment. That is a manageable amount of content to revise when the player's interpretation differs from the brief.
A useful review question for every character asset is: What will this help the player understand, anticipate, or feel? A silhouette might answer it through recognition, a movement through confidence, and a remembered favor through trust. Together, those details give the player something specific to care about.
Which small behavior made a game character memorable to you, and what did it reveal about their priorities?
AI disclosure: This article was researched and drafted with an AI assistant. The hypothetical examples and proposed workflow are a synthesis of the linked research and developer accounts.
Top comments (0)