Level up the hero.Keep the numbers honest.

Why LitRPG is a genre of bookkeeping

The promise of LitRPG and progression fantasy is growth you can measure. The reader is keeping score alongside the hero: the level, the skill list, the cultivation stage, the cores spent on a breakthrough. In most genres a continuity slip is a matter of taste. Here it is arithmetic, and a comment section will find it within the hour.

The other half of the difficulty is length. Progression stories run long: open-ended serials of hundreds of chapters, written over years and often released several times a week. By the time book three is in draft, the rule you set for mana recovery in chapter eight lives in your memory, or in a spreadsheet you stopped updating around the tournament arc.

Authrot’s answer is to keep the rules, the ladder and the manuscript in the same studio, and to read each chapter against them. You still decide what the System allows. The studio remembers what you decided.

Make every step up an event in the plan

In Authrot a book is planned as arcs, each with a goal, an opposition, stakes and an outcome. In a story with a system, an arc also carries its progression: the stage before, the stage after, and what it grants. Once any arc says what it changes, the field opens on every other arc, so you can read the whole climb at a glance and spot the arc where nothing is earned.

That matters because the genre’s best advice is about the timing of gains. A breakthrough should land at a turning point and cost something. A long grind with no step up reads as a stall; three level-ups in one chapter read as a cheat. Chapters sit under the arcs they serve, and you hear when a chapter drifts from its arc, so the gains stay tied to the story instead of floating free of it.

• Progression as one line per arc: before → after, and the gains
• Arcs that run across book boundaries
• Threads that follow a system’s progression, drawn down every chapter
• A warning when a chapter strays from the arc it serves

Rules for the System, written once and checked often

Every progression world has a handful of rules the whole story leans on: how power is measured, who or what runs the System, what advancement costs, and the ceiling nobody can buy past. Write them as lore entries under How it works, and anchor the ones that must never bend. The assistant never contradicts an anchor, and a chapter reading flags a line that breaks one, with the earlier fact beside it.

Character state is the second ledger. A bible entry keeps facts that change over time, so the hero’s rank, the sword’s grade or the sect they belong to can change in chapter forty without erasing what was true in chapter four. Flashbacks follow story time, so a scene set before the first dungeon sees the hero as they were then, not as they are now.

Start from the genre’s own shape

Pick the Progression fantasy & LitRPG starter on the Start screen and it fills the open Voice fields with the shelf’s habits: a close viewpoint on the protagonist, a driven and hopeful tone with real danger, and a style note that every gain should arrive at a turning point and cost something, with status screens short and rare. Choose LitRPG, cultivation, dungeon core or GameLit as the subgenre and that becomes the book’s genre.

It also adds two entries under How it works, the system and the cost of power, waiting for your answers, and offers the Serial arcs structure: a run of arcs, each with a new goal, a setback, a midpoint step up, a low point, a climax and a breather where rewards are counted and the next hook is set. Starters are data, not a model, so they cost nothing and work with the AI off. Every field stays yours to rewrite.

• The Level-up first person voice template: a practical narrator, the System’s prompts, every gain felt
• Tropes to start from, such as weak to strong, tournament arc and system apocalypse
• About 45 chapters a book as a starting length, open-ended

Writing the serial without losing the cast

Long serials pick characters up and set them down. The bible flags anyone who has gone quiet too long, and screen time shows the cast down every chapter, so the rival from the first arc returns on purpose rather than by accident. Promises are grouped by when they pay off, which suits the genre’s long questions: the hidden bloodline, the sealed floor, the debt owed to the old master.

When a chapter is ready, publish it under a pen name, or schedule a run of banked chapters for set dates and times. If a scheduled release can’t go out, nothing is published and you’re emailed why. Readers pick up at the paragraph where they stopped, and edited chapters can be republished one at a time or all at once when you fix a number after the fact.

Fights, training and the assistant

Two kinds of scene carry most progression books: the fight that tests a new skill, and the training that earns it. The genre’s readers forgive a lot, but not training told as summary or a fight won by a power nobody had a chapter ago. Writing rules make your standards explicit: must, should, avoid and never, such as “never introduce a skill in the chapter where it saves the day”. They are held on every line the AI writes and checked in readings.

If you draft with the assistant, it drafts a chapter from its plan and the result arrives as a proposal, not as finished text. Because it walks the bible before it writes, it knows the hero’s current rank and the System’s anchored rules rather than guessing. If you would rather write every fight yourself, the plan, the ladder and the checks you set by hand still do their job.