How to Design a Companion Character

Companion characters—allies who accompany the player—can become beloved presences that deepen attachment and enrich the experience, or annoying burdens players wish they could leave behind. The difference is in how well the companion supports gameplay, expresses personality, and earns attachment, while avoiding the specific pitfalls that turn companions into nuisances.

Support gameplay and express personality

A good companion contributes to the gameplay in a way that helps without taking over or becoming a liability—providing useful support, abilities, or presence that makes the player glad to have them, rather than a burden to manage or protect. The companion should make the gameplay better, not worse, which requires careful design of their mechanical role: helpful enough to be valued, but not so dominant that they trivialize the game or so fragile that protecting them is a chore. Alongside their gameplay role, a good companion has enough personality to feel like a real presence—a character with their own voice, reactions, and presence that the player comes to know, rather than a faceless ally or a mechanical helper. This personality is what lets a companion become a real presence in the experience and a focus of attachment, transforming them from a gameplay element into a character the player relates to. Supporting the gameplay (helpful without being a burden) and expressing personality (a real character, not a faceless helper) are the foundations of a companion players value and connect with.

Earning attachment while avoiding the companion pitfalls is what makes a companion beloved rather than burdensome. The ultimate goal of a companion character is to earn the player's attachment—to become an ally the player cares about, whose presence enriches the journey and whose fate the player is invested in—which comes from the combination of being genuinely helpful, having real personality, and sharing the journey in a way that builds a relationship. A companion the player is attached to deepens the experience enormously, making the journey feel shared and the stakes more personal. But attachment is easily destroyed by the specific pitfalls that plague companion design: companions who are needy, demanding the player's constant attention or care; companions who are helpless, requiring protection that becomes a tedious burden; companions who are intrusive, interrupting, talking too much, or getting in the way; and companions who undermine gameplay, becoming liabilities rather than assets. These pitfalls turn a potentially beloved ally into a nuisance players resent, so avoiding them—designing companions who are self-sufficient rather than needy, capable rather than helpless, present without being intrusive, and helpful without being liabilities—is essential to companions earning attachment rather than annoyance. A well-designed companion supports the gameplay helpfully, expresses real personality, avoids the needy-helpless-intrusive pitfalls, and thereby earns the player's genuine attachment, becoming the beloved ally that deepens the experience. A poorly-designed one, falling into the pitfalls, becomes the burden players wish they could abandon. Designing companions to support, to have personality, to earn attachment, and to avoid the pitfalls is what makes them the cherished presences they can be rather than the annoyances they too often become.

Scope is a decision, not an accident

Almost every overscoped game got that way one reasonable addition at a time, with no single decision ever feeling like the mistake. The finish line recedes a little with each new feature, and because the project always feels nearly done, the developer rarely notices how far the goal has drifted until they're exhausted and the game still isn't out.

Treat scope as something you actively decide rather than something that happens to you. Write down what the finished game contains, make every addition a conscious trade against that, and keep most new ideas in a backlog where they belong — because a small game you finish beats a large one you abandon.

Measure before you optimise

Intuition about what's slow, what's confusing, or what's driving players away is usually wrong, and acting on it wastes effort on problems that don't matter while the real ones persist. The developers who improve their games efficiently are the ones who measure first — profiling performance, watching real sessions, capturing actual errors — and let the data set their priorities.

It's slower than trusting your gut, but it's the only approach that reliably improves the game instead of just changing it. Find the biggest real problem, fix that, and measure again, rather than optimising guesses.

The first impression is most of the battle

More players leave in the opening minutes than at any other point, which makes the first few minutes the highest-leverage stretch of the whole game — and also the part the developer can least see clearly, having played it a thousand times. What feels obvious to you is often confusing to someone seeing it fresh, and that gap quietly costs you players before they ever reach the good part.

Get the player into the interesting part fast, let them feel competent quickly, and watch first-time players go through the opening without helping them. Nobody quits a game they're enjoying, so making the early minutes land is most of the battle for retention.

Small and finished beats big and abandoned

A folder of impressive unfinished projects teaches far less than a single small finished one, because finishing is where the hardest and most valuable lessons live — the unglamorous final stretch of bug-fixing, polishing, and shipping that ambitious abandoned projects never reach. Each completed game, however modest, builds the finishing muscle and the confidence that make the next one achievable.

So resist the pull of the dream project until you've shipped a few small ones. Scope to what you can actually complete, finish it, and let the experience of shipping make your bigger ambitions realistic.

Trust behaviour over opinions

People are unreliable narrators of their own experience — they're polite, they rationalise, they suggest fixes that miss the real problem. What they do tells the truth that what they say obscures: where they hesitate, where they get stuck, what they ignore, where they quit. The most valuable feedback is usually the behaviour you observe, not the opinion you're offered.

This is why watching beats asking, and why real data about what players actually do beats any amount of speculation. When several people stumble at the same spot, that's a problem worth fixing, regardless of whether any of them mentioned it.

A good companion supports gameplay helpfully, has real personality, and earns attachment—while avoiding the needy, helpless, or intrusive pitfalls that make companions a burden.