Every TTRPG system collapses two separate things into one entry: who a character is, and how they function in the game physics. Skryrún keeps them apart — and that changes everything.
Open any monster manual. Find an NPC entry. Look at it carefully.
You will find two completely different documents stapled together.
The first document is a character. A name. A role. A history. A list of things they want and fear. The kind of person who makes a world feel inhabited.
The second document is a rules object. Armor class. Hit points. Speed. Ability scores. A list of actions, each with dice and damage types and save DCs. The kind of entry that makes combat resolvable.
These two documents have almost nothing in common. One is game-agnostic. The other is system-specific to a degree that makes it incompatible with any other ruleset. And yet every TTRPG — every monster manual, every NPC appendix, every published adventure — presents them as a single unified thing, as if the character and the statistics were the same.
They are not.
In tabletop RPGs, the world and the game physics are experienced simultaneously. The moment your players encounter the tavern keeper, they might try to pick his pocket, charm him, or stab him. The GM needs to know immediately: what's his Dexterity modifier? What's his passive Perception? If things go badly, what are his hit points?
So the books merged the answers into one entry. The tavern keeper's name and the tavern keeper's statistics live on the same page because you need both at the same moment.
This is a completely reasonable design decision for a printed rulebook. But it encodes a false assumption: that knowing who someone is and knowing how they behave under the game's physics are the same category of information.
They are not. And treating them as the same has a cost that compounds across every world a GM ever builds.
Mira Thornvale is the head of the Spice Merchants' Guild in Caldervane. She is shrewd, patient, and has been quietly building leverage over the city's harbor master for three years. She lost a son to a plague that the city council refused to acknowledge. She speaks warmly to people she intends to exploit and coldly to people she respects. She keeps a coded journal she believes no one knows about.
None of that is a game system. None of that belongs to D&D 5e, or Pathfinder 2e, or Daggerheart, or any other ruleset. Mira exists as a narrative entity independent of what game you are playing. She will be herself whether you run Caldervane in a high-crunch tactical system or a narrative-first system that doesn't even use hit points.
Her character is game-agnostic. Her statistics — if she ever needs them — are not.
A stat block is a physics declaration. It says: in this game's simulation, this entity behaves according to these rules.
In D&D 5e, a stat block defines Mira's Armor Class (how hard she is to hit), her Constitution saving throw modifier (how well she resists poison), her Insight bonus (how good she is at reading deception). These numbers are downstream of D&D 5e's specific mechanical vocabulary. They are meaningless in a system that doesn't use that vocabulary.
If you took Mira's D&D 5e stat block and tried to run her in Pathfinder 2e, you would need to rebuild it almost entirely — different proficiency system, different action economy, different save structure. If you tried to run her in a narrative system like Ironsworn, the concept of a stat block might not apply at all. She'd be an NPC defined by her rank, her drives, and a handful of descriptive tags.
The stat block is not Mira. The stat block is a translation of Mira into a specific ruleset's language.
When GMs build worlds using conventional tools — or when they build directly in system-specific sourcebooks — they are forced to make a game system choice before they've finished building the world.
The moment you sit down to write an NPC in a D&D 5e framework, you're being asked to commit to Challenge Rating, to action economy, to damage types. If you later want to run that world in Pathfinder, you're not importing a world — you're doing conversion labor. If you want to run it in a narrative system, you're doing even more work, discarding most of what you wrote and reconstructing the parts that transfer.
This is backwards. The world should come first. The system should come later — when you actually know what rules your table is going to use.
Most worlds never get run because the GM builds the world in one system and then changes their mind, or because the group's preferred system shifts, or because a second GM wants to run a parallel campaign in the same world using different rules. The merge that seemed convenient in a printed rulebook becomes a trap the moment you try to separate what it joined.
In Skryrún, an NPC is a narrative entity. It has a name, a role, a portrait, relationships, secrets, a home location, a faction affiliation — everything that makes it real as a character. It lives in your world's canon, fully formed, independent of any game system.
It does not have a stat block. Not because we forgot, but because a stat block is not part of what an NPC is — it is part of how an NPC performs in a specific encounter, under a specific ruleset.
When an encounter arrives, you attach a stat block. You choose the system — D&D 5e, Pathfinder 2e, Daggerheart, whatever your table is running — and you associate the mechanical representation with the narrative entity. The stat block sits alongside the character without replacing it. If Mira is never drawn into combat, she may never need one at all. If she is, the GM attaches the appropriate block for their system and the encounter runs cleanly.
The narrative identity and the mechanical representation stay in separate layers. They can reference each other. They are never the same thing.
This separation has a consequence that is easy to understate: your world is no longer owned by a game system.
Caldervane is Caldervane. Mira Thornvale is Mira Thornvale. The Spice Merchants' Guild, the coded journal, the harbor master conspiracy — these exist in the world independent of what physics engine you are running. One GM can run Caldervane in D&D 5e on Monday nights. Another can run the same world in Daggerheart on Friday nights. Both are drawing from the same canon. Neither is translating anything. They attach the appropriate stat blocks when encounters require them and then return to the world.
When a new game system releases that your group wants to try, you do not need to migrate your world. The world is already there. You build new stat blocks for the system, attach them, and play. The five years you spent building Caldervane belong to you — not to the ruleset you happened to be using when you started.
This is what system-agnostic world-building actually means. Not that your world is somehow mechanical-detail-free and therefore vague. It means that the rich, specific, deeply imagined world you built can be expressed through multiple systems without being owned by any of them.
There is a useful analogy in fiction.
Middle-earth is Middle-earth. Tolkien's world does not belong to any game system, and it has been expressed through dozens of them over the decades — from MERP to The One Ring to Adventures in Middle-earth, each using different physics to simulate the same world. Frodo is Frodo in all of them. The Shire is the Shire. The narrative entity is stable. The mechanical expression of it varies.
When we built Skryrún, we wanted world-builders to have that same stability. The character you spend an hour writing — their history, their voice, their secrets — should not be held hostage to a particular ruleset's design decisions. The world you build should survive the game system you started with.
The NPC is not the stat block. The stat block is the NPC's physics, borrowed from a game engine, applied when needed, and returned when the encounter ends. The character was always something else entirely.
— The Skryrún Team