How to write LitRPG

LitRPG is fiction in which the game mechanics are explicit and visible: stat blocks, level-ups, skill trees, status-screen notifications. The load-bearing convention is that growth must be measurable on the page, not just narrated. When the hero learns a new skill, the reader sees the system announce it.

The term sits inside a broader umbrella. GameLit covers game-influenced fiction generally, using game elements as backdrop or flavor with or without a tracked mechanical system, and communities apply the two labels in overlapping ways rather than a strict hierarchy. The practical test for your own book: if you deleted every system message, would the story still make sense? In LitRPG proper, it would not.

The system is a character

Before chapter one, design the system itself: what progression exists, what powers cost, what is impossible. The genre's craft discussion keeps landing on the same two words: internal consistency. A system whose rules bend when the plot needs it trains readers to stop caring about the numbers, and the numbers are the appeal. A system with variety keeps progression interesting; a system with consistent rules keeps it meaningful.

Write the system's rules down the way you would write down a magic system's rules (see Sanderson's laws): sources of power, costs, limits, failure modes. In long serials this document becomes the most-consulted page of your story bible: skill lists, cooldowns, resource pools, what each tier can and cannot do.

Mechanics serve scenes

The failure mode of the genre is letting the system replace the story. Mechanics should enhance the narrative, not substitute for it: the protagonist still needs goals, relationships and problems that a level-up alone cannot solve. A status screen is a way of dramatizing progress, and progress is only dramatic if something is at stake besides the number going up.

A useful discipline: every system beat should also be a story beat. The level-up arrives mid-crisus, the new skill has a cost she cannot pay twice, the rare drop belongs to the person who needed to trust her.

Show growth on the page

Because growth is the genre's promise, the reader must be able to see it: milestones reached, thresholds crossed, capabilities that visibly change what a scene can do. LitRPG sits inside progression fantasy, whose structural pattern applies directly: defined tiers with clear thresholds, a visible next milestone, and training arcs treated as full narrative beats rather than montages. Power gains that carry a cost read better than free power, for the same reason limitations matter in any magic system.

Formatting system text

There is no universal standard for system messages; conventions are community-driven. The recurring pattern is to set stat blocks and notifications off from the prose, via bracketed text, bolding, or styled UI-like boxes, so the reader always knows whether they are in story or system. Pick one treatment in chapter one and keep it for the whole book; consistency of formatting is itself part of the genre's contract.

Continuity at serial scale

LitRPG serials run long, and mechanics accumulate faster than any other kind of canon: every skill, every point spent, every rule lawyered in a fight scene. Track what each ability does and costs as part of your records, because power creep is usually a continuity failure in disguise: the character who could once solve everything alone is only interesting if the story remembers what she could once do.

How Kanonara approaches this

Kanonara was built for exactly this kind of accumulation: abilities, states and world rules are tracked records with history, so a story can grow to hundreds of chapters without losing its system's logic. See how Kanonara works.