Why LitRPG Authors Need a Narrative Engine, Not a Spreadsheet
By Rob Chipman
You've built The Spreadsheet. I know you have.
It started simple — a character stats tab. Then items. Then locations. Then a cross-reference sheet for "who knows what." Then a formula to calculate Kira's HP at chapter 31 after the Wraith ambush, minus the health potion from chapter 28, plus the +15 VIT buff from the enchanted armor in chapter 19.
At some point, maintaining the tracker became harder than writing the book.
Fiction with rules
LitRPG is different from other genres because your world has actual mechanics. Not just "Kira is strong" — Kira has 42 STR, 1,200 HP, and a shadow-enchanted blade that grants +15 damage. Readers expect the math to work. And they will absolutely let you know when it doesn't.
The Royal Road comment every LitRPG author dreads: "um actually she couldn't have used Void Step there, she burned her mana on the Wraith ambush two chapters ago."
That specific shame of getting your own system wrong. If you've felt it, you know.
The four-tool shuffle
I've spent months talking to authors on Royal Road about how they actually work. The setups are remarkably similar:
- Google Docs for prose
- A spreadsheet for stats
- Obsidian or Notion for the wiki
- Their brain for "what has the reader figured out so far"
Four tools. None of them talk to each other. None of them understand that your story has a timeline.
The temporal problem
Here's what a spreadsheet can't do: tell you what was true at a specific moment in your story.
A spreadsheet knows Kira has 1,200 HP right now. It doesn't know she had 847 in chapter 31 and 432 in chapter 38. Every time you need to check "wait, what were her stats at this point?" — you're manually cross-referencing cells with chapter notes.
Your world-state changes over time. The tool tracking it needs to understand time.
Events, not cells
A narrative engine treats world-state changes as events anchored to your manuscript:
- Chapter 12: Kira acquires Soulreaver (+15 Shadow damage)
- Chapter 28: Health Potion (HP +500)
- Chapter 31: Wraith ambush — HP -340, Mana -200
Now you can scrub to any scene and see the world-state at that exact moment. "What was Kira's HP in chapter 31?" is an instant lookup, not a manual cross-reference.
Character sheets update automatically. Equipment, buffs, and stat modifiers — all computed from the timeline. The math does itself.
The other tracking problem
Stats are the obvious case. But there's a harder one: knowledge.
What does the reader know at this point in the story? What's been revealed? What's still hidden? If you're writing a mystery subplot alongside your progression system, you're tracking two layers of truth:
- Author Truth — everything you know
- Reader Knowledge — what the prose has revealed so far
Toggling between those views — checking "has the reader learned that Vex is working for the Hollow King?" before writing a scene where Kira meets Vex — that's not a spreadsheet feature. That's a narrative engine feature.
What exists today
There are good writing tools out there. Scrivener handles manuscript management well. Campfire and World Anvil do world-building. Novelcrafter focuses on the writing experience.
None of them were built for fiction where the world has rules. None of them track how a character's stats change scene by scene. None of them can show you the state of your world at chapter 31 versus chapter 45.
What I'm building
This is why AxiomWeaver exists. It's a desktop writing tool with a built-in narrative engine — the prose editor, the entity system, the event ledger, the temporal scrubbing, all in one app. Built specifically for LitRPG, Progression Fantasy, GameLit, Cultivation, and any fiction where the world has rules that matter.
It's in alpha right now. Free. Shipping new features weekly. If the spreadsheet problem resonates, request early access and see what it feels like when the tool actually understands your story.
Or join the Discord and tell me what you need. The tool is shaped by the authors who use it.