AI characters aren't built — they're given a life to live. Where did they grow up, what did they experience. In this era, narrative becomes the execution logic, and the line between writer and developer quietly disappears.
If you've ever played an old video game, you know this scene. You walk up to an NPC. You talk to them, and the same line comes out. Talk to them three times, ten times, or again a year later, and they repeat the same sentence like a parrot. They appear to have been standing there a long time, but really, nobody is home.
Let's slowly unpack why that scene is changing, and why the shift reveals a principle that goes far beyond games. NPC is short for Non-Player Character — a character the game moves, not a person. Think of them as the ones the world runs.
Think about people. When you try to understand why a friend acts a certain way, you look at their life. Where were they born, what kind of parents did they have, what did they go through, what are they good at, what scares them. People don't run on rules. They run on stories. That's basic common sense.
But somehow, the moment we face computer characters, that common sense evaporates. For the past 30 years we've been programming game characters with rules. "If the player gets within 3m, say this line," "if HP drops below 30%, run away." The character isn't alive — a rule table is just spinning behind it. That approach hits its limit fast. To cover 1,000 situations, you need to write 1,000 rules.
The reason is that technology is finally ready. Language models arrived, and suddenly you can tell a character a story, and behavior appears without rules. Skip the rules. Write a backstory instead.
A backstory is simply a narrative of how this character has lived. For example: "Her name is Amelia Sparkle. 28 years old. A former assassin. She left the organization seven years ago, and now runs a small flower shop. Her hands shake when she sees a gun." That's enough. When the player asks any question, the character composes an answer that matches that backstory. The story becomes the execution logic.
There's a real company doing this. Convai. It got famous after NVIDIA demoed it live on stage. Making a character inside Convai takes three steps. One, enter a name. Two, pick a voice. Three, write in the backstory box. The box takes up to 2,000 words.
I built one I called "Mr.5pm," based on the intro text for my channel Mr.5pm. I only dropped in about 221 words, and when the player asked "what is your name?" the character replied, "I'm called Mr.5pm." Asked "what's your specialty?" it said, "I blend art and technology to make new things." Not a single rule written. I only wrote the story, and the character started talking.
After that you can drop the same character straight into Unity, Unreal, or Roblox. It gets used in education simulations, virtual tour guides, museum docents. In an NVIDIA demo, someone spoke "search that area" to a soldier character, and the character didn't just reply — it actually moved in that direction. Words and actions fired together.
A simple analogy. Imagine a new hire showing up for day one. No company teaches them 1,000 rules one by one: "when the phone rings press this button, when a guest arrives say this, if the printer breaks call this number..." Instead they say, "this is who we are, these are our customers, and this is your role." They plant context. Then the new hire handles the rest with judgment.
A backstory-driven AI character is exactly that new hire. They don't memorize rules. They know who they are, and from then on they decide. So even if 1,000 situations come up, a well-written backstory covers all of them.
The contrast becomes clear with numbers.
| Approach | Situations covered | Authoring time | Edit cost |
|---|---|---|---|
| Old rule style (if-else) | only as many as rules | 40 hours for 1,000 cases | 10 minutes per line edit |
| Backstory style | effectively unlimited | 30 minutes for 2,000 words | 3 minutes per paragraph edit |
The old way took 40 hours to cover 1,000 dialogue situations. And when case 1,001 arrived, you had to add another rule. The backstory way takes 30 minutes for 2,000 words once. And with those 2,000 words, the character reacts to almost anything without a single rule.
Characters are no longer programmed. They are given a life.
That is today's aha moment. The verb shifts from "build" to "give a life to." The character description a writer composes becomes the code.
So if you're building an AI agent or chatbot, where do you start? Just make one question a habit.
"Who is this character? What have they seen, what do they fear?"
As soon as you start writing answers, you're writing backstory. No need to overthink it. Three paragraphs and the character moves.
Concrete example. You're building a simple consultation bot for a neighborhood dermatology clinic.
Old style (rules): if the word "acne" appears, give answer A, "melasma" answer B, "hives" answer C. Write 50 rules. The 51st symptom breaks the bot.
New style (backstory): "You are a dermatology consultant with 15 years of experience. This clinic specializes in skin conditions. Your role is to hear the patient's situation before they see the doctor and route them to the right track. If anything looks urgent, suggest an immediate visit. Don't diagnose — only guide." — Four lines. That's it. With those four lines, the bot now responds like a human to acne, melasma, hives, and 50 or 100 more symptoms it's never seen before.
Authoring time drops from 20 hours for 50 rules to 10 minutes for 4 lines. 120x faster. And quality goes up.
A short routine that works in any AI tool.
1. Pick a name (one line)
2. Write what this character knows (expertise)
3. Write what this character has been through (experience)
4. Write what this character must not do (guardrails)
5. Hand it to a friend and tell them to ask anything
Step 5 matters. Your own questions will land fine. It's the questions you didn't anticipate — asked by someone else — that reveal the quality of the backstory.
One sentence summary: Characters aren't built from rules. They come alive from stories. Three paragraphs by a writer now replace 1,000 lines of if-else.
This principle isn't just for game NPCs. Customer support AI, educational tutors, virtual assistants, avatars — they all run on backstory. Tool names will change. When Convai fades, the next company will work the same way, because this isn't a tech fad, it's how to make something feel human. People live by story.
One more thing. This quietly flips something. Going forward, writers become developers, and developers become writers. You may not be able to write a single line of code, but if you can write a character description, you can build an AI character. Conversely, if you want to become a developer, you'll need to learn how to write. The line between the two jobs is blurring. Tools change. Principles don't.
Three words to remember — Story. Character. Alive.