LitRPG and progression fantasy already contain a glossary: the system text defines skills, stats and items as they appear, in the reader's view, with numbers attached. That makes a back-matter glossary less necessary than in other genres and a consistency check far more necessary, because the genre's readers track the numbers and will do the arithmetic.
What actually needs checking
| Element | Failure |
|---|---|
| Stat totals | Points allocated that do not add up after a level |
| Skill costs | The same skill costing different amounts in different chapters |
| Skill names | Spelled or capitalised two ways; the commonest error |
| Item names | Same, and items are numerous |
| Level thresholds | A level reached at an experience total that contradicts an earlier one |
| System message format | Different layout or wording between chapters |
| Rules of the system | What is possible, applied differently under plot pressure |
| Class and race names | Capitalisation, and whether they take an article |
Rows three and four are where volume makes it hard. A progression novel can carry two hundred named skills and items, each used a handful of times, and at that frequency spelling never settles by repetition.
The system text as a formatting problem
System messages are in-world documents and need the treatment every in-world document needs: one format, applied identically, that survives conversion. Boxes, monospace fonts and elaborate layouts are the least reliable choices in an ebook, and a system message that renders as plain prose has lost the distinction the genre depends on.
Decide the format, record it for your formatter, and check it in the finished file rather than in the manuscript. The general treatment is in formatting letters, messages and documents.
What a back-matter glossary is for here
Not definitions, which the text supplies. Two other things:
- A reference for a returning reader, particularly in a long series where a skill introduced in book two matters in book five.
- A statement of the rules, which the system text gives piecemeal and never in one place.
Both are genuinely useful and both are short. A complete list of every item isn't a service; it's an inventory.
Checking the vocabulary
The Novel Kit's magic and technology index is where skill, item and system vocabulary surfaces, and the hyphenation checker is the highest-value report in this genre, because skill and item names are overwhelmingly compound and all three forms of a compound look correct. The capitalisation checker covers the other half, since system terms are capitalised in the system text and often not in narration, which is a decision rather than an error and needs to be a consistent one.
None of this checks your arithmetic. Stat totals, experience thresholds and costs are yours, and the guide to LitRPG stat consistency covers how to track them.
A practical next step
Extract your skill and item names and check the hyphenation of every compound. In a progression novel that list is long and it is where the errors concentrate.
Sources checked
Frequently asked questions
Does a LitRPG need a separate glossary?
Often not, because the system text already defines things as it goes. What it needs is a consistency check on those definitions, which is a different job.
What breaks most often?
Numbers. A skill that costs twelve points in chapter four and eight in chapter thirty, and a stat total that does not add up after a level.
Should the glossary include numbers?
Only if they are fixed. A skill whose cost scales should be described by its rule rather than by a value.