How to Write a LitRPG: 8 Steps From System Rules to Finished Chapter

To write a LitRPG, decide what game rules your world runs on, write them as a one-page rulebook, give your protagonist a starting character sheet, plot the story around moments of growth, show the system to readers in short messages, and keep a change log so the numbers stay consistent from chapter to chapter. The prose is still a story. The system is the pressure that makes the story's choices cost something.

This guide walks through those steps in order, with a small worked example whose arithmetic you can check by hand. Every tool linked below is free and runs in your browser; none needs an account.

The eight steps at a glance

What makes a story a LitRPG?

A LitRPG is fiction in which game-like rules, such as levels, stats, skills and classes, are an explicit part of the story. Readers can usually see the numbers, and the characters act with the rules in mind. If your story is about growing stronger but never shows the rules, it may fit better under a neighboring label such as progression fantasy or GameLit, and the labels you choose set reader expectations before chapter one.

Step 1: Decide how much game your story needs

Before you design anything, decide how much of the system reaches the page. Two stories can use identical rules and feel nothing alike:

• Light touch: a status window appears at key moments, such as a level-up or a new skill. Most scenes are plain prose.
• Heavy touch: stat changes, skill checks and inventory appear regularly, and readers follow the arithmetic.

Heavier systems ask more of you. Every number you show is a promise you must keep for the rest of the series. If you are writing your first book, start lighter than you think you need to; adding visible numbers later is easier than retracting them.

Step 2: Write a one-page rulebook

Write the rules down before you write the scenes. One page is enough. It should answer:

1. Primary stats. What are the core attributes?
2. Derived values. What is calculated from those stats, such as health, damage or speed?
3. Levels. What raises a level, and what does a level grant?
4. Skills and classes. How does a character gain abilities, and what limits them?
5. Limits and costs. What can the system not do, and what does power cost?

Here is a small rulebook you can borrow. The values are illustrative, not a prescribed game system.

Primary stats: Strength, Agility, Vitality, Intellect
Max HP = Vitality x 10 + Level x 5
Weapon damage = weapon base + Strength x 0.5
XP to reach the next level = 100 x current level
Each level grants 2 stat points to spend

The limits matter most. A rule such as "you can only raise a skill by using it under real pressure" generates scenes. A rulebook with no limits generates a protagonist who can never lose, which is a plotting problem rather than a numbers problem.

Step 3: Pick a growth curve

The curve decides how far one level separates two characters and whether gear can still matter later. A linear curve keeps early and late levels comparable; an exponential curve makes each tier feel like a different world. Neither is wrong, but the choice should be deliberate. The post on linear versus exponential growth covers the tradeoffs, and the XP Curve Visualizer lets you compare curves or test your own formula before any scene depends on it.

With the example rulebook, reaching level 2 costs 100 XP, level 3 costs 200 more, and level 4 costs 300 more. A character who has earned 600 XP in total has reached level 4. Write that table down; you will check scenes against it later.

Step 4: Build the starting character

Give your protagonist a level 1 sheet with one clear strength and one clear weakness. For example:

After the first level-up, Level becomes 2, so Max HP rises to 8 x 10 + 2 x 5 = 90 before any points are spent. If the character puts both new points into Vitality, Vitality becomes 10 and Max HP becomes 10 x 10 + 2 x 5 = 110. Working the sums once, on paper, is how you find out that a "small" stat choice moves health by 20.

The RPG Stat Build Calculator does this kind of allocation for you, and the Character Stat Sheet turns the result into a sheet you can paste into a chapter.

Step 5: Plot around progression

A progression beat is a moment when the character's power changes. Good beats share three parts:

• A limit the character cannot get past yet.
• A cost paid to get past it: time, risk, a resource or a relationship.
• A payoff that changes what the character can do in the next scene.

Plot your first book as a short chain of these beats rather than a list of fights. If two milestones in a row give a reward without a cost, readers stop feeling the progression. The Character Progression Planner can show you levels across the book so a sudden spike or a flat stretch stands out.

Step 6: Show the system on the page

Readers need to see the system without being buried in it. A few habits help:

• Show a number when it changes a decision. If Strength 6 versus Strength 9 decides whether a door opens, show it. If it only decorates the scene, summarize it.
• Keep system messages short and visually distinct from narration, usually as a boxed message.
• Make the box readable without its colors. Formatting can be lost or changed on some platforms, so the text should make sense on its own.

For a worked example of building a boxed message and placing it in a Royal Road chapter, see How to Make a Royal Road Blue Box.

Step 7: Keep a change log

Every level-up, item and temporary effect changes a number somewhere, and readers will notice if chapter 40 disagrees with chapter 12. The fix is a log with one row per change that records where in the story it happened. Our guide to keeping LitRPG stats consistent across a series shows a worked ledger, including temporary buffs and what to do when you move a scene.

You can keep that log in a notebook, a spreadsheet or the free LitRPG Stat Tracker, which logs changes by chapter and shows every stat as it stood at any chapter. When you revise, the Stat Block Continuity Checker compares two status windows and highlights what changed.

Step 8: Test the numbers before readers do

Run your system through the scenes it has to survive. With the example rulebook, suppose the hero has a weapon with base damage 4 and Strength 6. Damage per hit is 4 + 6 x 0.5 = 7. A goblin with 60 HP takes 60 / 7 = 8.57 hits, so nine hits to defeat. Is nine exchanges the right length for a fight in chapter 2? If the goblin hits for 10 against 85 HP and the hero strikes first, the hero lands the ninth blow after taking eight hits, with 5 HP left, so the fight is close but winnable. That is a tension you can write.

Run the same check on rewards. The Damage Formula Sandbox tests formulas with variables and a sweep graph, and the Loot Drop Calculator shows the exact odds and expected number of attempts for a weighted drop table, so a "rare" item is as rare as you meant.

Where a writing app fits

You can write a complete LitRPG in a word processor and a spreadsheet, and for a short book with a light system that is a perfectly good setup. The tools become a burden when the log, the manuscript and the status windows live in three places and a rewrite changes all of them.

WriteIDE is a free desktop writing studio for LitRPG and progression-fantasy authors. As of version 0.7.5 you can record stat changes at the scenes where they happen, insert stat blocks that show a character's values at a chosen point in the story, and review the blocks that a later edit may have made out of date. It runs on macOS, Windows and Linux, stores your project on your computer, and requires no account. If you already have a manuscript elsewhere, you can import it or keep your editor and use WriteIDE only as a tracker; see how to move a manuscript. Nothing about it writes your prose for you.

Frequently asked questions

Do I need game design experience to write a LitRPG?

No. You need a small set of rules that you apply consistently. Start with the one-page rulebook in step 2 and add complexity only when a scene demands it.

How many stats should a LitRPG have?

Use as few as your story needs. Four to six primary stats are enough for most books, because every stat you add is another number to keep consistent. Add a stat when you can name a scene that needs it.

Should every chapter include a status window?

Not necessarily. Show the system when it changes a decision or marks a milestone, and summarize it otherwise. Chapters that are all numbers and no scene tend to read as a spreadsheet.

Can I write a LitRPG in Google Docs or Word?

Yes. Many authors do, usually with a spreadsheet beside the manuscript for the stat log. The tradeoff is that you maintain the link between the log and the chapters yourself.

What should I do when I change an earlier chapter?

Trace every number the change touches, from that scene to the end of the book, and update the status windows that depend on it. The consistency guide shows how to do that with a ledger.

---

Written for WriteIDE 0.7.5, October 2026. The rulebook and numbers above are illustrative examples, not a prescribed system.