Why Sir Lora Refused to Disappear

The squirrel that outlasted the delete button

Every long-running game studio has a few inside jokes that become more famous than anyone expected. In Larian Studios’ case, one of those jokes is Sir Lora, the overly determined squirrel knight from Divinity: Original Sin 2. What makes the character notable is not just his odd design or his tiny scale next to the game’s larger cast. It is the fact that even Larian’s own leadership reportedly tried to erase him from later versions of the game, only to discover that Sir Lora was harder to remove than anyone anticipated.

The story has become a memorable example of how game content can develop a life of its own after launch. A character that started as a quirky extra ended up becoming part of the studio’s identity, surviving internal frustration, technical complications, and the practical realities of shipping a game across multiple platforms. For fans, it is a funny anecdote. For developers, it is a reminder that even small features can become surprisingly resilient once a game is in the wild.

This article looks at why Sir Lora became such a headache, what the episode says about production choices in large RPGs, and why tiny side characters can become unexpectedly memorable in the first place.

Who is Sir Lora, exactly?

Sir Lora is not a combat powerhouse, a main story hero, or a central villain. He is a squirrel companion who follows the player, speaks in a grand and slightly ridiculous tone, and behaves like someone who believes he is part of a noble fantasy epic. That mismatch is a big part of his charm. He gives the world of Divinity: Original Sin 2 an extra layer of absurdity without needing to affect the main plot in any major way.

In RPGs, optional companions often serve as flavor rather than function. They can provide humor, extra dialogue, or a little world-building that rewards exploration. Sir Lora fits that pattern perfectly. He is memorable because he feels unnecessary in the best possible sense: he is there to make the world feel stranger, more playful, and more willing to break from tradition.

But what is charming to players is not always convenient for developers. Optional characters can create extra work in localization, quest logic, scripting, and platform-specific testing. In a complex title, a seemingly tiny addition can ripple through many systems at once. Sir Lora became a perfect example of that problem.

Why a studio boss would want him gone

Swen Vincke, Larian’s CEO and one of the studio’s best-known public figures, apparently had little affection for the squirrel. The dislike was not just casual teasing. According to the account reflected in the source article, he actively tried to remove Sir Lora from a later version of the game. That is a strong sign that the character had crossed from “slightly annoying” into “this has become a production issue.”

Why would a leader of a studio target a character like this? The most likely answer is simple: when teams are preparing different versions of a game, every nonessential system is a candidate for removal. If a feature causes risk, adds complexity, or creates extra QA work, it becomes tempting to cut it. A side companion that is funny once but costly many times over can look like a bad trade.

That tension is common in game development. Writers and designers love personality. Producers and testers need consistency. A character such as Sir Lora lives right in the middle of that conflict. He is easy to appreciate as a joke, but much harder to justify when the schedule tightens and platform certification starts to matter.

The hidden cost of keeping a joke in the game

Players often assume that if a feature is small, then it must also be easy to maintain. In practice, the opposite can be true. Tiny systems may depend on strange triggers, one-off scripts, and special cases that are easy to forget during porting. If the team revisits the game for another release, the old joke can suddenly become a technical puzzle.

That seems to have been the case with Sir Lora. The source material suggests that removing him was not as simple as flipping a switch. Instead, the team encountered a bug where deletion worked in some regions or builds but not others. Once a feature behaves differently depending on version or localization, developers face a familiar nightmare: debugging something that should not have been a priority in the first place.

At that stage, the question is no longer, “Do we like this character?” It becomes, “How much time will it take to make his removal safe everywhere?” If the answer is too high, even a disliked character may survive out of sheer logistical stubbornness. In that sense, Sir Lora’s greatest skill was not combat or dialogue. It was structural survival.

What this says about modern RPG development

Larian is known for building reactive, systems-heavy role-playing games. Those games reward experimentation, support many character states, and allow for unusual interactions. That freedom is a major strength, but it also increases complexity. The more flexible the game world, the harder it can be to cleanly remove an element once it has been integrated.

Sir Lora’s survival hints at a broader truth about RPG production:

• Small features can touch many systems. Even a companion that does not fight may still be tied to quests, voice lines, triggers, and save data.
• Porting magnifies risk. What works in one build may behave differently in another, especially across console releases.
• Testing takes time. A change that seems harmless can trigger unexpected failures late in development.
• Funny content still counts as content. If it exists, it needs support, documentation, and maintenance.

That is why developers sometimes keep content they do not especially enjoy. The creative impulse says, “Cut the nuisance.” The production reality says, “Not until we know exactly what that does.” Sir Lora’s persistence is, in a strange way, a tribute to the complexity of modern game building.

Why players remember odd companions

Players are often more attached to eccentric side characters than to polished but generic ones. That happens because humor creates memory. A squirrel knight with a dramatic personality is easier to recall than a more standard fantasy companion, even if the standard companion is mechanically more useful.

There are a few reasons for this:

1. Contrast makes characters stand out. A tiny animal behaving like a grand adventurer creates instant novelty.
2. Optional encounters feel personal. If a player chooses to recruit or keep a strange companion, the experience becomes more self-directed.
3. Comic relief breaks tension. Long RPG campaigns benefit from moments that interrupt seriousness.

Sir Lora fits all three. He is weird, self-contained, and hard to mistake for anything else. Even players who do not love him usually remember him. That is valuable in a game where dozens of NPCs compete for attention. A character does not need to be central to be effective. Sometimes it is enough to be unforgettable.

The studio joke that turned into folklore

Stories like this often grow beyond their original context. What starts as a practical decision inside a studio becomes fan lore after players hear about it. In this case, the idea that the director wanted to delete a squirrel but failed is the kind of anecdote gaming communities love. It has a neat shape: a disliked character, an attempted removal, a technical obstacle, and a final outcome where the character remains.

That structure makes it easy to repeat and share. It also reflects a classic gaming truth: development chaos often becomes part of the final product’s personality. Fans do not only remember what appears on screen. They remember the stories behind it, the scrapped ideas, and the weird production details that reveal how the sausage was made.

For Larian, this probably had a mixed effect. On one hand, the story reinforces the studio’s reputation for personality and transparency. On the other hand, it immortalizes a character the boss wanted gone. In that sense, Sir Lora won twice: once by surviving the build, and again by becoming a legend.

What developers can learn from Sir Lora

Sir Lora’s story offers a practical lesson for game teams of any size. Creative experiments are valuable, but they should be introduced with an eye toward long-term maintenance. A feature that seems harmless in one phase of production can become expensive once localization, platform compliance, and bug fixing begin.

A useful way to think about it is this:

The lesson is not that developers should avoid strange ideas. It is that they should know the price of keeping them. If a strange companion makes a game more memorable, that can be worthwhile. The trick is to understand whether that personality is also going to survive the realities of shipping on multiple systems.

Why the story still lands with fans

At heart, this is a very human story. Someone at the top of a company disliked a small creation so much that he tried to remove it, and the work fought back through technical complexity. That is funny, but it is also relatable. Most people have encountered situations where a simple change turns into a hassle because the system is interconnected.

Fans also enjoy seeing that game development remains messy behind the scenes. It makes big studios feel less like faceless machines and more like collections of people making judgment calls under pressure. A story about a squirrel refusing to disappear is the kind of anecdote that makes a large RPG feel handmade rather than sterile.

And perhaps that is the real reason Sir Lora endures. He is not just a mascot for weirdness. He is proof that even in a massive, carefully built fantasy game, small ideas can outlive the people who tried to remove them.