Decide once how your status windows look

What is in the guide

• The system’s voice

  Four worked options for who or what is speaking, from terse machine to formal herald to dry administrator, with what each one costs you later.

• Nine structural decisions

  Delimiter, label case, change notation, number style, stat naming, subject, tense, maximum lines, and whether the character can dismiss a box. Each with a safe default.

• Twelve canonical blocks

  Level up, allocation, skill acquired, evolution, rank up, quest offered, complete and failed, item acquired, appraisal, status effect, and system anomaly. Copy rather than retype.

• A frequency budget

  How often each box type should fire per chapter and per book, because a notification is a reward and also an interruption.

• Formatting that ships

  Why box-drawing characters and fixed-width alignment break in EPUB, what works everywhere instead, and how to keep a serial version alongside a reflowable one.

• Your locked decisions

  A one-page table to fill in and keep beside the manuscript, plus an end-of-book consistency checklist.

Rules that come with the blocks

Each template carries the reason it is shaped that way, so you can adapt it without losing the point.

• Allocation

  Show the derived consequence, not the raw stat. "VIT +3" means nothing. "Max HP 686 to 742" is the number the reader has been tracking.

• Evolution

  Always name the condition that fired. It is the difference between an earned moment and an authorial gift, and it costs one line.

• Quest complete

  Match the reward line to what the offer promised, exactly. A mismatch is the most-reported continuity error in the genre.

The part discovered during formatting week

A border assembled from box-drawing characters looks superb in a text editor and on a web serial. In a published ebook it breaks several ways at once: embedded fonts lack the glyphs, reflowable text abandons the alignment, and at 24pt it wraps into rubble. Fixed-width columns fail for the same reason, since you control neither the font nor the size.

What survives is an indented block, a bracketed label, and typographic emphasis: no custom glyphs, no fixed widths, no tables. It reflows, it scales, it reads aloud, and it looks deliberate in print.

Audio is the constraint most authors forget. Audiobooks are a large share of this genre's revenue, and every box has to be read by a person. A twelve-row status table becomes ninety seconds of recited numbers. The guide's test is simple: read the box aloud, and if you stumble, it was built for the eye alone.

Keeping the numbers inside the boxes honest

A style guide fixes how a box looks. What goes in it still has to match the character. Clifford tracks stats, skills, and inventory chapter by chapter, so the values you quote in a status window are the values the character actually has. See the LitRPG stat tracker and the continuity checker.

The numbers themselves come from the other templates: the stat calculator for derived values, the XP curve for level-up thresholds, and the skill tree tracker for costs and cooldowns.

System notification FAQ

How many notifications should a chapter have?

Two feels generous, four feels like a game log. The guide gives a per-type budget, and the standing rule is never to place two boxes back to back without prose between them.

Can the system have a personality?

Yes, and the guide covers what it costs: a system with opinions is a character, so readers will start interrogating its knowledge and motives.

What format is the download?

A Word document (.docx) that also opens in Google Docs and Pages. The fill-in tables are editable in all three.

I publish on Royal Road first. Does that change anything?

Yes. Serial platforms are far more permissive than EPUB, so the guide has you design a serial version and a reflowable fallback for each block on the same day.