The Fragility of FromSoftware NPC Questlines
2026-08-18 · 9 min read · Dark Souls, Dark Souls III, Bloodborne, Elden Ring
Ask a group of Souls players about their first Dark Souls playthrough and you will eventually get the Solaire conversation. Almost nobody saves him the first time. They meet him on the bridge above the Undead Burg, they laugh at the sunlight, they summon him for a couple of bosses, and then at some point in Lost Izalith they find a hollowed thing with a familiar helmet wearing a red bug on its head, and they kill it because it is attacking them, and only later do they learn that there was a way to prevent it and that they walked straight past it.
This is not an accident of design and it is not, despite how it gets described, simply bad quest design. It is the most consistent authorial choice FromSoftware has made across sixteen years, and it produces something no quest log has ever managed. Understanding why requires being honest about how genuinely user-hostile these quests are first.
How the quests actually break
There is no journal. There is no marker. There is frequently no dialogue line indicating that a quest exists at all. Beyond that, the failure modes are specific and worth naming, because they are the same handful repeated across every game in the series.
- Progression is gated on world state rather than on conversation. Characters move when you kill a boss, light a fire, or enter an area, whether or not you knew they were waiting on it.
- Many steps require returning to a location you have no reason to revisit, and offer no hint that returning would do anything.
- Some steps are gated on talking to a character repeatedly until dialogue exhausts, which players routinely stop doing after the first new line.
- A single boss kill in the wrong order can silently skip several steps, and there is no indication that anything was skipped.
- Characters can be permanently lost through actions that look completely reasonable, including simply being efficient.
- Several quests can only be completed within a narrow window of world progress that closes without warning.
Sirris of the Sunless Realms in Dark Souls III is the cleanest illustration. Her line requires you to be in a specific covenant state, to be summoned into her world twice, to fight two invaders, and to visit an unmarked grave in a location most players see once. Miss any link and she simply stops appearing. Nothing tells you. There is no failure state, no notification, no closed entry in a log. There is only an absence you probably will not notice for another twenty hours.
The argument that this is bad, which is partly correct
It is worth conceding the obvious objection properly rather than waving at it. A meaningful proportion of these quests are effectively uncompletable without a wiki on a blind playthrough, and describing that as intentional design does not make it good design. Ranni the Witch in Elden Ring involves a sequence of steps across four regions with a hard dependency on entering an invisible-walled cave behind an illusory floor. The chance a first-time player completes it unaided is close to zero.
When a designer builds content most players will never see, that is a real cost, and pretending otherwise is fandom rather than analysis. The counterargument is not that the fragility is harmless. It is that the fragility is doing narrative work, and that the work is worth the cost more often than not.
What the fragility actually produces
Consider what happens when Siegmeyer of Catarina goes wrong. He is a gently comic figure, an onion-shaped knight stuck at obstacles you can trivially solve, and helping him is a series of small favours across the whole game. Do it wrong, or too efficiently, and his story ends in the Ash Lake with his daughter Sieglinde standing over him. Do it right and it ends slightly better, but only slightly.
The thing that gives Siegmeyer his weight is that most players discover the failure retroactively, and the failure was theirs. They cleared the enemies before he could. They were being helpful. That specific texture - the sense that you contributed to an outcome you did not intend and cannot now undo - is not something a quest log can produce. A log makes failure legible in advance, and legible failure is just a task you did not do.
A quest you can fail without noticing is the only kind of quest that can genuinely regret.
The same mechanism gives Eileen the Crow her power in Bloodborne. She is a hunter of hunters, tired, near the end of her working life, and she asks you plainly to stay out of her business. Follow her instructions and she survives longer. Intervene at the wrong moment in the fight with Henryk, or approach her after she has gone mad in the Cathedral Ward, and you fight her. Most players fight her. The game never punishes you for it or comments on it. It simply lets the outcome stand.
What makes that land is that Eileen has told you exactly what will happen. She warns you that hunters go mad, that she expects to go mad, and that she would rather it be quick. She has, in effect, foreshadowed her own ending, and you get to watch yourself deliver it. The design does not moralise about this. It just leaves the memory with you.
Why players get attached anyway
The obvious question is why anyone develops affection for characters whose quests they mostly ruined. Several things are going on at once, and they compound.
The first is scarcity. NPCs in these games appear rarely, speak little, and are usually alone. A world this empty makes every voice enormous. When Solaire tells you he is looking for his own sun, that is perhaps ninety seconds of dialogue in a forty-hour game, and it is one of the only unguarded expressions of hope you will hear. Scarcity makes the encounter feel like an event rather than a stop on a route.
The second is that the player has to do the interpretive work. Because nothing is spelled out, understanding a character means assembling them from dialogue fragments, item descriptions and the location where you last saw them. Ranni is the extreme case: her actual plan is distributed across a doll, a spirit ashes description, an assassin she hired centuries ago and a moon she wants to take somewhere. Players who understand Ranni understand her because they built the picture themselves, and people are attached to conclusions they reached rather than conclusions they were handed.
The third is loss aversion, applied honestly. In most games, a companion dies when the script says so, and you know it was scripted, which limits how much it lands. In a FromSoftware game, an NPC can vanish because of a decision you made without realising it was a decision. That converts a narrative event into a personal one. Players do not remember that Solaire went hollow. They remember that they did not save him.
The fourth is repetition. These games are built for multiple playthroughs, and the second run is where the quests become tractable. Knowing the failure points transforms them from invisible traps into a genuine layer of optional content, and doing a quest correctly for the first time on a third playthrough carries a satisfaction proportional to how long you spent getting it wrong. The fragility is annoying once and rewarding every time after.
The design has been quietly changing
It is worth noting that FromSoftware has moved on this, gradually and without announcement. Dark Souls III added conversation prompts at bonfires that surface characters who have something new to say. Elden Ring added map markers for NPCs you have met, which is a meaningful concession, and its base game questlines are broadly more forgiving than Dark Souls-era equivalents even when they remain obscure.
The remaining design does not tell you what to do; it tells you where someone is. That is a good compromise. It preserves the interpretive work, since knowing where Ranni stands does not tell you what she wants, while removing the single most frustrating failure mode, which was never really discovery but rather losing track of a character who moved while you were somewhere else.
Whether the studio should go further is a fair argument. What seems clearly right is that a full quest log would destroy the thing being described here. The moment a game lists Solaire under active objectives with a next step attached, he becomes a task. The reason he is not a task is that the game genuinely does not care whether you help him, and that indifference is what makes helping him feel like a choice.
Recognising them by their words
These characters are mostly remembered through their voices, which is exactly what the NPC and Quote modes on Soulsdle test. A line of dialogue stripped of its speaker turns out to be surprisingly identifiable once you have spent enough hours listening, because these characters are written with very distinct registers: Solaire is earnest, Siegmeyer is cheerfully oblivious, Eileen is clipped and tired, Ranni is formal in a way that keeps you at a deliberate distance.
It also functions as a decent audit of how much of the series you actually absorbed. Plenty of players who have finished every game find they can name the bosses instantly and still hesitate over a line from a character they walked past four times in a single playthrough.