Stat blocks aren't what kill a litRPG novel; unaudited stat blocks are. The system message is one of the strongest tools the genre has, but it works as punctuation, not narration, and most authors paste in the engine output without ever asking what the line is doing on the page.
What a litRPG system message is actually supposed to do
A litRPG system message exists to compress information, mark a change in state, and reward the reader's investment in the character's progression. That is the actual job, and once you say it out loud you also know what the bad system messages are doing instead, which is, mostly, narrating the fight that the prose just narrated, in a slightly different voice, with numbers attached. I think the genre got into this mess because so many of the canonical books (Aleron Kong's The Land, the early Zogarth, the Travis Bagwell Awaken Online series) faithfully print the raw notification logs the protagonist sees inside the game world, readers grew up on that, and the convention calcified into "the system shows you everything." But the system showing the character everything is a different problem from the system showing the reader everything; the character lives inside the System and has no choice in the matter, while the reader is sitting on a couch with a Kindle, looking for a story.
So my feeling, then, is that the first question to ask before writing any system message is what work the line is doing that the prose isn't already doing. If the answer is "nothing, the prose already covered it," cut it. If the answer is "the prose can't say this without breaking the rhythm of the action," keep it. There is no third good answer.
Why most authors over-use them (the cargo-cult problem)
Most authors over-use system messages because they treat the System as the author of the scene rather than as a tool the author chooses to use. Once you set up a system apocalypse, the System is technically generating output for every action, and a certain kind of writer, especially one new to the genre, feels obligated to faithfully report all of it. It feels rigorous, it feels crunchy, it feels like the books they grew up on. The problem is that the books they grew up on were also being lazy about this, often, and the readers complaining about the convention are mostly complaining about exactly this lazy mimicry. The complaint, when you read it carefully, is almost never "I hate stat blocks." It is "I hate stat blocks that don't tell me anything." A grenade doing eleven points of damage to one zombie, then twelve to the next, then eleven to a third, contains no information beyond what the verb "killed" already gave us, but it costs the reader four lines of attention and a hard stop to the action. Multiply by a fight scene with twenty mooks and you have a scene that, on the page, is mostly numbers, and on audio, is forty-five seconds of monotone arithmetic.
There is also a structural reason this keeps happening, and I think it deserves naming. Generating a stat block is a free pass on writing prose. If you are stuck on how to describe a moment of impact, writing Critical hit. 47 damage. Skill rank up: Polearm Mastery, Level 12 is much easier than writing the thump of the spear hitting bone, and the genre quietly enables this. The cure is to notice when you are reaching for the stat block out of laziness rather than out of authorial decision, and to make yourself write the prose instead, at least on the first draft. You can always paste the box back in later.
The good stat block is punctuation, not narration
The strongest stat blocks in the genre work as punctuation, marking the moment a change in state matters, and not as line-by-line narration of every swing. Matt Dinniman's Dungeon Crawler Carl is the most public example of this done well; the system messages there are wickedly funny precisely because they are rare and editorial, and the AI announcer that issues them is a character with opinions, not a damage calculator. When Carl gets a notification, it lands, because Dinniman has spent five chapters not giving him one. Compare that to the per-swing damage logs in weaker books and the difference is obvious. Restraint is what makes the system feel real, because in real games the only notifications you remember are the ones that mattered.
The same principle is doing the heavy lifting in He Who Fights with Monsters, where Shirtaloon uses the system as a vehicle for bureaucratic comedy more than as a combat ledger. The System in those books is a character, somewhat petty, fond of stiff phrasings like awarded for cause: minor, and the reader leans in when the box pops up because the box is going to say something the prose can't. That is the test for a working system message. The box has to say something the surrounding prose either can't say or shouldn't.
When to use a full readout, when to use a half-line, when to cut
The choice between a full readout, a half-line, and a complete cut is a pacing choice, and the deciding question is whether the number itself is doing emotional or strategic work. A full readout (the multi-line notification with stats, descriptions, and skill effects spelled out) belongs at moments of significant transition: a level up the reader has been waiting for, a class evolution, a new skill the protagonist will use later in the book, a death notification for a side character. The reader will absorb the full block in those moments because they have been earning it across many chapters.
A half-line, something like the System rang once for the kill, then again, drily, for the second one, is right for the in-between, when you want to confirm the gameplay layer is still operating without putting the camera on it. And the complete cut is correct for the mass combat of mooks where the only information that matters is "the threat is over." In other words, the question to ask of every stat block is not "is the System producing this output?" (the in-world answer is always yes), but "does the reader need to see what the System produced?" Most of the time, the reader does not. That is fine. That is what authorial selection is.
My advice, then, for writers in the middle of a manuscript that has too many stat blocks, is to walk through each fight scene and ask of every notification whether the next ten pages would be confusing if the notification were not present. If the next ten pages are not affected, cut. If the next ten pages turn on a specific number (the protagonist made the saving throw with one point of mana to spare, say), keep, and make the box sing.
Formatting matters because half your readers are listening
Format matters because the modern litRPG reader is, more often than not, an audiobook listener, and a stat block that scans cleanly on the page can be unlistenable in the ear. Travis Baldree, who narrates large chunks of the genre's catalog including Zogarth's Primal Hunter and Will Wight's Cradle, has talked publicly about how to read a system notification so that it does not destroy the scene's momentum. The honest answer is that you have to write the notification so the narrator has a chance. That means short, parseable lines, with the most important word in the first three. Skill gained: Mana Edge lands cleanly in audio. Through your sustained engagement with the System's mana matrix, you have acquired a new active skill, designated Mana Edge, which scales with your Intellect attribute and consumes mana proportional to its effect output is forty-five seconds of audiobook the listener will fast-forward through, and that is the listener's last good memory of your book.
The other formatting lesson the strong books teach is that the stat block should look different on the page from the prose around it. Bracketed, blockquoted, code-block monospace, italicized; pick a convention and hold it. The visual break is a contract with the reader that says, "you may skim or read this paragraph, your choice, but the prose above and below it is doing the actual storytelling." I think the genre's best authors are honest with their readers about this, and the weaker ones are not, and the reader frustration on the forums is mostly a reaction to the dishonest version, where the System box masquerades as load-bearing prose and then turns out to contain nothing.
A self-test before you commit a system message to the page
The self-test I use, and that I think holds up for most litRPG and progression fantasy writers, is three questions asked of every box before it goes on the page. Does this notification mark a state change the reader will care about ten pages from now? Does the box say something the surrounding prose either cannot say or should not say? And, if I read this aloud to a listener at one and a half times speed, would they still want to keep listening when it ends? If the answer is yes to all three, you have a stat block that has earned its place in the book. If the answer is no to two or more, the answer is not "shrink the box." The answer is, cut the box and let the prose carry the moment.
That, in my view, is the difference between books that get glowing reviews on Audible and books that get the same complaints, every week, on the genre forums. The numbers were never the problem. The author's relationship with the numbers was the problem, and once you remember that you, not the System, are writing this book, the question of how many stat blocks to include answers itself.
Common questions about litRPG system messages
How often should a litRPG novel use system messages?
Most working litRPG authors aim for a handful of stat blocks per chapter rather than one per action, with the actual count rising during set-piece progression moments such as level ups, evolutions, and boss kills, and dropping to near zero during travel, dialogue, and recovery scenes. Treat the System notification as a tool you ration for impact, not a recording device that follows the protagonist everywhere. Readers consistently say they want fewer, sharper blocks rather than more exhaustive ones.
Are repetitive system messages a problem for audiobook listeners?
Yes, repetitive system messages are the single most common complaint from audiobook listeners in the litRPG and progression fantasy space. On the page the eye can skim past a damage log; in audio the narrator has to read every line, and the listener has no easy way to skip a single notification mid-track. If even half your readers are likely to be on Audible, write your stat blocks short and editorial, and trim anything that is just an arithmetic restatement of the prose around it.
Do readers actually skip the system messages?
Many do, and most authors are quietly aware of it. Print readers report skimming over routine combat notifications and slowing only on level ups and skill acquisitions; audio listeners often disengage when a long stat dump begins. This is not a failure of the reader. It is the format telling you which notifications were worth writing. If a block is universally skipped, that is feedback. The fix is to cut it, or to give it something only it can say.
Can a litRPG be successful without numerical stat blocks?
A litRPG can absolutely be successful with very few or no traditional stat blocks, provided the progression system still feels concrete and ruled in some other way. Mother of Learning tracks progression through skill descriptions and observable in-world consequences with almost no numerical readouts, and most readers do not consider it any less of a progression novel for that. The genre's defining feature is rule-based growth, not the bracketed text box.
Should I use a code-block or italic format for system messages?
Either works, provided you commit to one convention and hold to it through the whole book. Code-block or monospace gives a clean visual break and works well on Kindle and Royal Road; bracketed italics are friendlier for paperback layout and audiobook scripts. What matters is that the reader can recognize a system notification at a glance and decide, mid-paragraph, whether to read it carefully or let the eye glide past.
by Jacob Tam · May 23, 2026
I run IlorisNovel, a platform for writers of web fiction. If this kind of craft writing is your thing, the rest of the blog lives here.