How to Write Compelling Game Characters
Game characters face a challenge that no other storytelling medium creates: the player can interact with them in unpredictable ways and at unpredictable times. A novel character delivers their lines in the order the author wrote them. A game character might be encountered by a player who has already completed the main quest, or one who wandered into the area by accident before meeting the prerequisites, or one who has killed every other NPC in the game. The character must function, and ideally feel believable, in every scenario the game systems allow. This constraint shapes every aspect of how game characters are written.
Step 1: Define the Character's Core Want and Fear
Every memorable character is driven by a want and restrained by a fear. The want is what they are pursuing: revenge, safety, knowledge, connection, power, redemption, freedom. The fear is what they are avoiding: abandonment, irrelevance, loss of control, being exposed as a fraud, repeating a past mistake. The tension between want and fear creates the internal conflict that makes characters interesting, because it means the character is not a simple entity who always does the obvious thing. They hesitate, they contradict themselves, they make choices that reveal their internal struggle.
In games, the want and fear should be connected to systems the player interacts with. If a character wants to protect their village, the player should be able to help or hinder that goal through gameplay. If a character fears losing their independence, game events should threaten that independence in ways the player can observe. When want and fear are connected to gameplay, the character stops being a voice that talks at the player and becomes a person whose stakes are tangible within the game world.
Write the want and fear in one sentence each. Ellie from The Last of Us: wants to find meaning in a world that seems meaningless, fears being alone. Solas from Dragon Age: wants to restore what was lost, fears that restoration requires destroying what is. Hades' Zagreus: wants to escape the Underworld and find his mother, fears that he is fundamentally bound to a place he does not belong. If you cannot state the want and fear in simple sentences, the character concept is not clear enough yet. Simplify until you can, then add complexity through behavior and dialogue.
Step 2: Build a Character Voice Profile
Voice is how a character sounds on the page, independent of voice acting. It encompasses vocabulary level (does this character use simple words or academic language?), sentence structure (short and blunt, or long and winding?), verbal tics and patterns (do they always deflect with humor? Do they start sentences with "Look," when frustrated?), topics they gravitate toward (a soldier who frames everything in military metaphors, a merchant who measures value in coins), and topics they avoid or become uncomfortable discussing.
Build the voice profile by writing ten sample lines for each character across different emotional states: calm, angry, afraid, affectionate, deceitful, and surprised. These sample lines become the reference document that keeps the character's voice consistent across all their dialogue in the game. When you are writing conversation number forty-seven for a character and you cannot remember exactly how they would phrase something, the voice profile provides the answer. Without it, characters drift tonally across the game, sounding different depending on when their dialogue was written, which breaks the illusion of a consistent personality.
A practical test for voice consistency: take a line of dialogue and remove the speaker tag. If someone familiar with the characters can identify who is speaking from the text alone, the voice is distinct. If the line could belong to any character, the voices are not differentiated enough. In games where players can choose to talk to NPCs in any order, distinct voices are essential because the player may not remember which character they are talking to based on context alone. The voice itself must carry identity.
Step 3: Design the Character's Arc and Change Points
A character arc is the journey from who the character is at the start to who they become by the end. Not every character needs an arc (some characters are deliberately static because their consistency provides an anchor in a changing world), but the characters players care about most are usually the ones who change visibly over the course of the game. The change must be earned: it must result from events the player witnessed and ideally participated in, not happen offscreen or be declared in exposition.
In games, character arcs must account for player timing and pacing. A novel controls exactly when the reader encounters each stage of the character's development. A game cannot guarantee that the player will complete quests in order, talk to the character at every opportunity, or even encounter the character at all. Design arcs with checkpoints rather than continuous progression: the character is in state A until a specific trigger occurs, then shifts to state B. Each state has its own dialogue set, behavior patterns, and reactions. Triggers can be quest completions, story events, relationship milestones, or player choices. The checkpoint approach ensures the arc works regardless of how quickly or slowly the player progresses.
Map the change points explicitly. For each shift in the character's state, document: what triggered the change, what the player should notice differently (new dialogue lines, different attitude, changed behavior), and what the change means for the character's internal journey. A character who starts distrustful, warms to the player after being saved, then becomes conflicted when their loyalty is tested has three states with two transitions. Each transition should be a visible moment the player experiences, not a silent backend variable update.
Step 4: Write Reactivity Into Every Interaction
Reactivity is what separates a game character from a recording. A reactive character responds differently based on what the player has done, what they are currently doing, and what the game world's state is. At minimum, a character should have different greetings for first meeting, subsequent meetings, and meetings after significant story events. Better reactivity includes acknowledging player actions ("I heard you helped the merchants in town"), reacting to player equipment ("That is a fine sword you are carrying"), and adjusting attitude based on accumulated relationship ("You have been a good friend. I need to tell you something I have not told anyone.") .
The principle of visible reactivity is that the player should regularly encounter lines that feel specifically tailored to their playthrough. Even if the vast majority of dialogue is generic (the same for all players), strategically placed reactive lines create the illusion that the entire character is aware of and responding to the player's unique journey. Three reactive lines per conversation, well-placed and specific, create more felt reactivity than thirty generic lines that never reference the player's situation.
For web games with limited scope, a lightweight reactivity system works well: track three to five key state variables per character (relationship score, key choices the player made, quest progress), and use those variables to select between two or three variants of key dialogue lines. A character who says "Welcome back, friend" versus "What do you want now?" based on a single relationship flag creates meaningful differentiation for minimal production cost. Scale this approach as the game's scope allows, but even the most basic implementation is dramatically better than no reactivity at all.
Step 5: Test With Real Players and Revise
Character writing cannot be evaluated in isolation. A character that reads well on the page might feel flat in the game because the pacing is wrong, the player does not encounter enough of the character's dialogue, or the reactive lines do not fire often enough to create a sense of personality. The only way to evaluate game characters is to watch real players interact with them.
Set up playtests focused on character perception. After the session, ask players open-ended questions: describe [character name] in three words. What did you think of them? Did you want to talk to them more or less? Was there a moment where you felt something about them? The answers reveal whether the character is landing as intended. If you designed a character to be sympathetic but players describe them as annoying, the writing is not failing in the ways you expected, and the fix is not more exposition about why the character is actually sympathetic. The fix is changing the character's behavior and dialogue so sympathy comes through naturally.
Revision based on playtest data is where game characters improve dramatically. First-draft characters are almost always too expository (they explain too much about themselves), too static (they do not change enough in response to events), or too generic (their voice is not distinct enough to be memorable). Each round of playtesting reveals which of these problems is dominant, and each revision cycle tightens the character until they work in the actual context of gameplay rather than just on paper.
Character Writing for AI-Powered NPCs
LLM-powered NPCs introduce a new dimension to character writing: instead of scripting every line, you write a character definition that guides an AI model to generate dialogue in character. The character profile becomes a prompt: personality traits, speaking style, knowledge boundaries, emotional state, goals, and constraints on what the character can and cannot say. This is a fundamentally different writing discipline from scripting dialogue, because you are writing instructions for a system that will produce the actual dialogue, not writing the dialogue itself.
The skills that transfer from traditional character writing are voice definition (the voice profile becomes the tone section of the prompt), motivation (the want and fear become the character's goals and constraints), and knowledge boundaries (what the character knows and does not know about the game world). The new skill required is prompt engineering for consistency: writing character definitions that produce reliably in-character responses across a wide range of player inputs, including adversarial inputs from players trying to break the character.
Testing AI-powered characters is more complex than testing scripted ones because the character's responses are non-deterministic. The same player input might produce slightly different responses each time. Testers need to evaluate whether the character stays in voice, maintains knowledge boundaries, handles unexpected questions gracefully, and produces responses that feel natural within the game's world. Automated testing that sends a battery of test inputs and evaluates the responses against rubrics is becoming standard practice for AI-powered game characters.
Compelling game characters are built from a clear want and fear, a distinct and consistent voice, a visible arc with defined change points, reactive dialogue that acknowledges the player's actions, and revision based on real player feedback. These fundamentals apply whether the character is fully scripted or powered by an LLM.