How to Track LitRPG Stats Across a Long Serial
A change-log method, copy-paste spreadsheet formulas, the pitfalls that break trackers around chapter 100, and where tools fit.
The most reliable way to track LitRPG stats is a change log: one spreadsheet row per stat change, tagged with the chapter it happens in. A formula then rebuilds any character's sheet as of any chapter, so editing old chapters or writing ahead for patrons never corrupts your numbers.
Key takeaways
- Log every change as its own row with a chapter number, not one sheet per chapter.
- Keep base values, bonuses and unspent points as separate rows so totals add up.
- Store formulas for derived stats instead of typed totals.
- Always ask questions as of a chapter: is this right as of chapter N?
- Run a five-minute status-screen check before every post.
- 1Why does LitRPG stat tracking break?
- 2What LitRPG stats should you track?
- 3What spreadsheet layout works for LitRPG stats?
- 4Derived stats: keep the formula, not the total
- 5Seven pitfalls that break trackers around chapter 100
- 6What is point-in-time state, and why does it matter?
- 7How do you check stats before posting a chapter?
- 8Tools: a spreadsheet, a notes app, or something that reads your chapters
The most reliable way to track LitRPG stats across a long serial is a change log: one row for every stat change, tagged with the chapter it happens in, so you can rebuild any character's sheet as of any chapter. A single "current stats" tab, or a copy of the sheet for every chapter, both break once you edit old chapters or write ahead of what you've posted. This guide covers what to track, a spreadsheet layout with formulas you can copy, the pitfalls that break trackers around chapter 100, and where dedicated tools fit.
Want plotwrite.ink to draft your next chapter in your own voice?
Why does LitRPG stat tracking break?
Stats are the one part of a LitRPG that readers can audit. They copy status screens into the comments, add up the points, and notice when Strength went from 48 to 52 in chapter 31 and is back to 50 in chapter 34. A reader who stops trusting the numbers stops caring about the next level-up.
Trackers usually fail for one of four reasons:
- You updated the prose and forgot the sheet, usually mid-fight, when stopping to open a spreadsheet would kill the scene.
- You write ahead. If patrons read 10 or 20 chapters ahead of Royal Road, your sheet reflects the newest chapter, but the chapter you're fixing is older.
- You moved or cut a scene, and every number after it shifted.
- The System grew. A sheet designed for six attributes at chapter 1 has no room for skill ranks, titles, set bonuses and a second class at chapter 150.
None of these is a discipline problem. They're design problems with the tracker, and they have design fixes.
What LitRPG stats should you track?
Track the state a character carries from one chapter into the next:
- Level and experience, if your System shows them.
- Attributes, with base values kept separate from bonuses from equipment, titles and buffs. Readers forgive a bonus they understand. They don't forgive a total that doesn't add up.
- Unspent points. Points spent twice, or never spent, are the most common slip of all.
- Skills: name, rank or level, cost, cooldown, and the chapter each was gained. Note every rename.
- Class, subclass, race and titles, with what each one does and when it was gained.
- Equipment and items that change numbers. Plot items matter too, but stat-changing gear matters most.
- Currency and resources, if your story spends them.
- Lasting effects: curses, injuries and debuffs that carry across chapters.
- The System's own rules: caps, conversion rates, what a level-up grants, and anything that can never go down.
Leave out what resets every scene, like HP and mana mid-fight or cooldown timers inside one battle. Log the result of the fight, not every tick of it.
If you write smooth LitRPG, with few numbers on the page, the list gets shorter but doesn't disappear. Ranks, skills, titles and what each character can do still have to hold.
What spreadsheet layout works for LitRPG stats?
Most trackers start as one tab per character with a column per chapter, or a fresh copy of the sheet for every chapter. Both make you retype values that didn't change, and both fall apart when you edit. The layout that holds up is a change log: one row per change, never one row per chapter.
Use these columns:
- A, Chapter: the chapter where the change happens on the page.
- B, Character.
- C, Attribute: STR, Level, Rank, Skill: Ember Step, and so on. Spell each one the same way every time.
- D, Change: +3 or -1, for numbers that add up.
- E, Value: the new value, for things that are replaced rather than added (a rank, a class, a skill level).
- F, Source: a few words quoted from the chapter, so you can find the line again.
- G, Note: why it changed (level-up, item equipped, curse).
Enter starting values as rows at chapter 0. Now any sheet, as of any chapter, is a formula. In Google Sheets or Excel 365, with the chapter you want in cell J1, Kira's Strength at that chapter is:
- =SUMIFS(D:D, B:B, "Kira", C:C, "STR", A:A, "<="&J1)
For values that are replaced, like a rank, take the last row at or before that chapter:
- =INDEX(FILTER(E:E, (B:B="Kira")*(C:C="Rank")*(A:A<=J1)), COUNTA(FILTER(E:E, (B:B="Kira")*(C:C="Rank")*(A:A<=J1))))
The second formula expects the log sorted by chapter, so sort it before you look anything up. Build a small "sheet" tab that pulls every attribute this way, change J1, and you have the status window as it stood at any chapter.
Stop retyping your stat sheet. PlotWrite reads it from your chapters. Start your 7-day free trial →
Derived stats: keep the formula, not the total
If your System has derived numbers, like max HP from Vitality, or damage from Strength plus a weapon, write the formula once and let the sheet compute the total. Typed totals are where drift hides: you update Vitality and forget the HP that depends on it.
Keep bonuses as their own rows too. Equipping a sword is a row with +5 STR. Selling it in chapter 90 is a row with -5 STR. The totals at chapter 85 and at chapter 95 both come out right, and you can see why.
Seven pitfalls that break trackers around chapter 100
- Updating later. Log the change when you write the status screen, not at the end of the week. If that breaks your flow, drop a marker in the draft (a symbol you never otherwise type) and clear every marker before you post.
- Renamed skills. Pick one name per skill, keep old names in the note column, and search older chapters for the old name before you publish.
- Unspent points. Track them as their own attribute, with spending logged as negative rows.
- Rebalancing the System. If you change how the System works, add a note row at the chapter where readers learn about it, and decide whether earlier chapters get edited or stay as they were.
- Moved scenes. Chapter numbers in the log go stale the moment you move a scene. Fix the rows for that scene the same day, or the whole timeline after it is suspect.
- Readers on different chapters. Royal Road readers, patrons and your own draft can sit at three different chapters. When a reader asks about a number, check it as of their chapter, not yours.
- Screen and prose disagree. Decide which one is canon (usually the status screen), fix the other, and don't leave both standing.
What is point-in-time state, and why does it matter?
The change log works because it stores what was true and since when, not just what's true now. That one idea, point-in-time state, is what lets you edit chapter 40 while drafting chapter 140 without the numbers from chapter 140 leaking backwards.
It also changes how you check a chapter. The question stops being "is this right?" and becomes "is this right as of this chapter?" Pull the sheet as of the chapter before, apply what happens in this one, and compare the result with the status screen you just wrote.
How do you check stats before posting a chapter?
- Find every status screen in the chapter (search for your System's brackets).
- Compare each one with the sheet as of the previous chapter plus this chapter's changes.
- Check unspent points and anything with a cost: mana, cooldowns, currency, a once-a-day limit.
- Search the chapter for every skill name it uses, and confirm the character had each one by then.
- Log anything new before you close the file.
- Want ideas for the screens themselves? The free LitRPG stat block generator makes sample status windows in the browser, with no sign-up.
Tools: a spreadsheet, a notes app, or something that reads your chapters
A spreadsheet is free, flexible and fits any System, and if you already have one that works, keep it. Its cost is upkeep: every change is typed twice, once in the prose and once in the log.
Notes apps like Obsidian give you a page per character and links between them, which is great for lore and relationships. Stats over time are harder there, because a note shows what you last typed, not what was true at chapter 47.
Several free LitRPG trackers have been shared on the Royal Road forums over the past year, many of them offline and made by authors. Most use the same change-log idea and ask you to log each event by hand, which suits writers who like a dedicated window for their System.
PlotWrite takes a different route: it reads the chapters you've already written and proposes each level, stat, skill and title as a fact with the chapter and the line it came from. You approve them in the Inbox, any character's sheet as of any chapter is one click away, and the canon check compares each new chapter against it before you post. It does the upkeep for a subscription, where a spreadsheet does it for your time.
Whichever you choose, the principle doesn't change: every change gets a chapter number, and every question gets asked as of a chapter. For the wider version of this habit, beyond stats, see How to keep a 500-chapter web serial consistent.

Frequently asked questions
What's the best way to track LitRPG stats?
A change log: one row per stat change, with the chapter it happens in. From that, a formula rebuilds any character's sheet as of any chapter, which is what you need once you edit old chapters or write ahead for patrons.
Should I show a full status screen in every chapter?
Only if your readers want it. Full screens every chapter are easy for readers to check and easy for you to get wrong. Many authors show the full screen at level-ups and arc ends, and only the changes in between. Either way, log every change.
How do I fix stat mistakes in chapters I've already posted?
Decide which number is canon, edit the old chapter, and add a short author's note if readers noticed. Then add a note row to your tracker so you don't undo the fix later.
How many stats should a LitRPG track?
Only as many as readers will check. Track what carries between chapters: level, attributes, unspent points, skills, class, titles and gear that changes numbers. Skip per-fight values like mid-battle HP, and log the result of the fight instead.
Do I need to track stats if I write smooth LitRPG?
Less, but yes. Smooth LitRPG shows few numbers, but readers still notice when a rank, skill or title changes without a reason. Track those with the chapter they changed, even if you never track a single attribute.
Stop retyping your stat sheet. PlotWrite reads it from your chapters.
plotwrite.ink learns your writing style, keeps track of your characters and world rules, and can draft the next chapter in your voice with your Claude or ChatGPT plan or your own AI key. Built for Royal Road, Wattpad, and serial authors who post weekly.
- No credit card
- Cancel anytime
- Full Architect access
- Works with your Claude or ChatGPT plan or your own AI key
Quick answers from this guide
Direct one-page answers to the most-asked questions on this topic.
What should a LitRPG character sheet include? (Free template)
A LitRPG character sheet should list the character's level, attributes, unspent points, skills, class, titles, gear and currency, and every entry should say which chapter it changed in. The chapter number is what keeps stats consistent over hundreds of chapters, because it lets you rebuild the sheet as it stood at any point in the story. Copy the template below and log each change the moment you write it.
How do you avoid power creep in progression fantasy?
Power creep in progression fantasy is what happens when each new power-up makes the earlier ones pointless, so the hero has to keep getting stronger just to stay interesting. Avoid it by giving every power a cost and a limit, keeping old abilities useful, and writing problems that raw strength cannot solve. A written record of what the hero can do, and when they got it, keeps the escalation in check.
How do you design cultivation realms and stages?
To design cultivation realms, build a ladder of a few named realms, split each into sub-stages, and give every step a visible gain, a cost and a way to fail. Write the ladder down before chapter 1, and keep a realm table for every character. Readers forgive a simple ladder. They do not forgive one that changes its own rules.
Start writing your web serial today
plotwrite.ink builds your story bible, tracks your progression systems, and flags contradictions — so you can focus on writing the story that earns you readers and income.
Start your free trial — 7 days, no card needed