How to write LitRPG: systems, stats and status screens

What makes a story LitRPG

LitRPG (literary role-playing game) is fiction where the rules of a game are visible on the page. Characters have levels, stats and skills, and the reader sees system messages and status screens. Because the reader knows the rules, they can guess what a character can do next and enjoy watching a clever plan work.

That changes what readers expect:

• The rules stay fixed. If a skill costs 20 mana in chapter 4, it costs 20 mana in chapter 140 unless the story shows why it changed.
• Growth is visible. Readers come back to see the next level, the next skill, the next class.
• Smart use beats raw power. The best scenes are the ones where a character wins with a weak skill used in a way nobody expected.

Progression fantasy is the wider family: stories about getting stronger in clear steps. Cultivation novels often belong to it without showing any numbers. If your steps are realms and breakthroughs instead of levels and stats, the light novel guide and the magic system generator may fit you better.

Design the system before chapter 1

Write a one-page rules sheet before you draft. It needs five things: where the system came from, the stats, how levels work, how skills are gained, and the hard limits nobody can break. Keep the stat list short. Four to six stats are easier for a reader to remember than twelve.

Then decide what your protagonist has that nobody else has, and what it costs. A plain advantage (strong, lucky, reborn) is not enough. The cost is what makes chapters interesting.

System rules sheet: The Ledger (example)

Source: The Ledger appeared to everyone in the city of Varn on the night the bells stopped. Nobody knows who runs it.
Who can see it: Each person sees only their own sheet, unless they spend a skill to read someone else's.

Stats (4): Strength, Agility, Focus, Grit. A person starts at 5 in each. Each level gives 3 points to spend.
Levels: 1 to 50 for this book. XP needed doubles every 10 levels.
Classes: chosen at level 5 from offers based on what the person did in the first five levels.
Skills: gained by repeating an action or by a class reward. Each skill has a rank (I to V) and a cost.

Hard limits:
- Skills that heal cost Grit for one day.
- Nobody can raise a stat above 3 x their level.
- Dying removes one level and every point of XP toward the next.

What the protagonist has that nobody else has: Mara can see the Ledger's error log, the messages it sends nobody.
What that costs her: every time she reads it, the Ledger notices, and the next quest it gives her is harder.

The sheet does not have to appear in the book. Most of it reaches the reader slowly, one rule per scene, when a character runs into it.

Status screens readers do not skip

Show the full status screen rarely: once early, then at the end of an arc or before a big fight. In between, show only what changed, right after the moment that caused it. A full sheet after every fight teaches readers to scroll past your blue boxes.

[Mara Quell] Level 7 Scavenger
Strength 8   Agility 14   Focus 17   Grit 9
Skills: Salvage II, Quiet Step I, Read Error Log (hidden)
Unspent points: 3

Salvage II reached rank III.
New effect: you can tell which parts of a broken object can still be used.

• Use one consistent format for system text, such as square brackets or a separate block, so readers can tell it apart from narration.
• Keep each message short. If a skill needs a paragraph of explanation, show it working in a scene instead.
• Check how your formatting looks on a phone. Wide tables and long lines of dashes break on narrow screens.

The chapter formatter cleans up spacing before you paste a chapter into a serial site, and the ability name generator gives you skill names that match your system’s tone.

Pace level-ups so they stay earned

A level-up feels earned when the reader saw the cost: a risk taken, a choice between two good options, an injury, a friend let down. A level-up that just arrives after a fight is a number going up.

• Plan the curve for the whole book. Decide the level your protagonist ends Book 1 at, then space the level-ups so the gaps grow.
• Make points a choice. If a character can raise every stat, nothing is at stake. Mara puts everything into Focus and pays for it when she cannot lift a beam off a trapped child.
• Let other characters grow too. Rivals and friends who level up give the reader a scale to measure the protagonist against.
• Watch for inflation. If damage numbers go from tens to millions, readers stop feeling them. Small numbers that matter beat big numbers that do not.

Sample opening arc outline

Here is a ten-chapter opening arc for the Ledger example. Each chapter gives the reader one new rule, one cost and one reason to read the next chapter. Copy it and replace the details with your own.

Working title: The Ledger Has an Error Log (Book 1, opening arc)

Premise: When a game-like system appears over the city of Varn, everyone gets a status sheet. Mara Quell, a scrap dealer, also sees the system's hidden error log, and the log is warning her about something nobody else knows is coming.

Chapter 1: The Night the Bells Stopped. Mara is pricing scrap when every bell in Varn goes silent and a sheet of blue text hangs in front of her eyes. Her neighbour laughs at his Strength score. Mara reads a line under her sheet that nobody else mentions: "ERROR: quest seed 0 failed to load."
Chapter 2: Level 1. The first monsters come out of the drains. Mara kills one with a pry bar and gets her first level and the skill Salvage I. The fight is ugly and she nearly loses a hand.
Chapter 3: The Price of Points. Mara puts all her points into Focus to read the error log more clearly. Her neighbour puts his into Strength and saves her life that night. She starts to doubt her choice.
Chapter 4: What the Log Says. A new error line names a street and a time. Mara goes and finds a family trapped under a collapsed shop. Saving them gives no XP at all. The Ledger has noticed her.
Chapter 5: Class Offers. At level 5 Mara is offered three classes. Two are strong. The third, Scavenger, is weak but lets her keep reading the log. She takes Scavenger.
Chapter 6: The Guild. A new guild of high-Strength fighters starts charging for protection. Their leader asks to see Mara's sheet. She lies about a skill for the first time.
Chapter 7: A Harder Quest. The Ledger gives Mara a quest no one else got, with a timer. The error log says the quest is a trap. She takes it anyway because the reward is a skill that hides her sheet.
Chapter 8: The Drain Boss. Mara wins by salvaging parts of the boss's armour mid-fight, not by being stronger. She reaches level 7 and Salvage II.
Chapter 9: Two Readers. Mara finds out that another person in Varn reads the error log too, and he has been using it to steer the guild.
Chapter 10: End of Arc. Mara spends her three unspent points on Grit, the stat she ignored. Final line of the error log: "ERROR: player count does not match. Correcting."

Need a premise first? The plot generator has a LitRPG option and returns six story ideas, each with the edge, its cost and the scene readers come back for.

Track stats over hundreds of chapters

Long LitRPG serials break in the numbers. A stat changes without a level-up, a skill rank goes backwards, a cooldown is forgotten in a big fight. Readers notice, and they say so in comments.

Keep one record and update it after every chapter:

• Each character’s level, stats and unspent points
• Every skill with its rank, cost and cooldown
• Items and where they are
• Each system rule, and the chapter where readers first saw it

The story bible template has sections for ranks and abilities you can adapt for stats and skills.

Publish it as a web serial

LitRPG has a large readership on web serial sites such as Royal Road, where readers follow a story chapter by chapter. Read a few popular stories in the genre on the site you choose, to see how they format system text, write blurbs and tag their stories. Each site has its own rules, so read them before you post.

A steady schedule matters more than a fast one. Build a backlog of chapters before you launch, and use the web serial schedule calculator to see how long your backlog lasts at the pace you plan.

Where AI tools help

AI tools are most useful in LitRPG for the bookkeeping: keeping stats and skills in one place, checking a chapter against the rules, and suggesting names for skills, classes and items. If a tool drafts prose, treat it as a rough draft. Check every number against your record, rewrite lines that do not sound like you, and follow the rules of the site you post to.

Webnovels AI is our desktop writing app for web serial authors. It keeps your story facts in Book memory, and its /review command finds facts in a chapter that conflict with them. Every edit it proposes waits for you to approve it. See what it does or check the price.

FAQ