Stat blocks and system pop-ups are part of what makes a LitRPG feel like a LitRPG, but most authors are still writing them as if every reader is looking at the page. In 2026, with audio carrying a majority of the genre's listening hours, repetitive system messages have stopped being a stylistic choice and started being a load-bearing craft decision. The short version is this: keep the messages, change how often you fire them and how a narrator can survive reading them aloud.
Are LitRPG system messages craft or just noise?
LitRPG system messages are craft when they carry information the prose has not already given you, and noise when they restate what just happened in a slightly different font. There is a real reason the genre evolved with stat readouts in it, and I think the writers who shrug them off as a quirk to be edited out are misreading what readers come to LitRPG for. The screen-of-text aesthetic, the little blue popup, the cold numerical confirmation that yes, the goblin really is dead (those are part of the genre's pleasure, the same way that a sword-and-sorcery novel that refused to ever describe a sword would feel like it was missing something). But the version of this that broke in audio is also real, and pretending it isn't is what's getting authors one-star reviews on Audible without their understanding why.
The debate inside the community tends to split three ways. One camp says the messages are the genre and to deal with it; another says they're skim fodder on the page and torture in audio; a third (the one I think is right) says the messages are fine but the way most authors deploy them is lazy. My feeling about this is that "stat blocks are LitRPG" and "stat blocks should be readable" are not in tension. They are a craft problem with known solutions, and a small number of well-established authors have already figured them out.
When repetitive stat blocks actually earn their place
Repetitive system messages earn their place when the repetition is the point, when it's doing emotional work that prose alone cannot do, and when the reader is meant to feel the rhythm of the numbers rather than parse each one. Think about the climactic levelling sequences in Dungeon Crawler Carl by Matt Dinniman, where the stat readouts pile on so hard and fast that the cumulative effect is celebratory; you're not meant to read each line, you're meant to feel the avalanche. Or the early notification spam in Defiance of the Fall by TheFirstDefier, where the sheer torrent of "skill gained" lines is what tells you the protagonist's class is broken in a way ordinary prose understatement could never quite hit. He Who Fights with Monsters by Shirtaloon uses a slightly different version of this trick, where the rules-lawyer voice of the system itself becomes a character, and the readouts are funny rather than informative.
My advice, then, is to think of repeated system messages the way a poet thinks of repetition: as a deliberate hammer-blow, not as a default narrative mode. If the repetition is supposed to feel oppressive, fine, lay it on thick. If the repetition is supposed to convey the next ninety seconds were a meat grinder of identical zombies, you can in fact say that out loud and skip the ninety actual messages. The popup is a tool, and like any tool it's most powerful when it isn't the only one in your hand.
Where system spam tips over into reader fatigue
System spam tips into fatigue the moment the messages stop adding information per line, and the worst offender by far is the per-hit damage readout in a multi-enemy fight. A representative bad example looks like this: five grenade damage messages, each shaving a damage point off the previous, telling you nothing that the prose Johnny threw a grenade into the horde of zombies has not already established. There's nothing wrong with showing damage numbers, and I think the writers who reflexively cut all numbers (sometimes in deliberate over-correction to audiobook feedback) end up with a watery action sequence that doesn't read as LitRPG at all. The issue is granularity. A single summary line covering ten zombies is information. Ten near-identical lines covering ten zombies is a clogged drain.
The same logic applies to passive skill notifications. The first time the MC's fireball skill ticks up in the middle of a fight, the popup adds something. The forty-seventh time, you are training the reader to skim. And once a reader has trained themselves to skim system messages in your book, the next important one (the one you actually wanted them to read) gets skimmed too. That's the real cost, not the lost minutes. It's the slow erosion of the trust that any given system message is going to matter, which is the same trick that ad-saturated platforms have used to teach their users not to read banners. You do not want your readouts to look like banner ads.
The audiobook problem most LitRPG authors still write past
The audiobook problem is that the same paragraph of text that reads in two seconds on a page can take forty-five seconds in audio, with no visual cue that this is the boring numbers part and no easy way to physically skip without scrubbing. In print I can let my eyes glide over a stat block in a tenth of the time it took to typeset; in audio I am held hostage by it. Most LitRPG audiobooks in 2026 are unabridged transcriptions of books that were written without ever once asking how this scene would land at 1x playback. That mismatch is where the audience friction is coming from, and pretending it's a narrator problem rather than a manuscript problem is letting yourself off the hook.
The fix is not (in my view) to gut the system messages from the manuscript. Doing that breaks the print and ebook experience, and a non-trivial slice of LitRPG readers, the ones who buy the Defiance of the Fall and Cradle hardcovers and put them on a shelf, are exactly the people you cannot afford to alienate by sanding off the crunchy bits. The fix is to write the messages in a form that an audiobook can elegantly compress: a single representative line plus a summary, or a meta-narration like Rhaegar uses in Azarinth Healer where the prose literally says stat increase, and so on until the relevant final value. RinoZ, in Chrysalis, sometimes goes further and gives the audiobook listener an in-character aside such as I'll spare you the dozens of notifications, here's what mattered, which doesn't read as a fourth-wall break in audio because the narrator just sounds like he's choosing to summarize.
A working rule of thumb for system messages
A working rule of thumb is that any system message in your manuscript should either deliver new information, carry emotional weight through deliberate repetition, or both, and that any message that fails both tests should be collapsed into a summary or cut entirely. I keep coming back to a quick sanity-check I borrowed from an author friend who writes in a different genre but has the same instinct: read the section out loud, fast, in a flat voice, and notice where your own attention slips. If you, the author, are skimming your own stat block, your reader is too, and your audiobook listener is going to be furious.
There is a temptation, especially for newer LitRPG authors, to use system messages as proof that the book really is a LitRPG. I understand the impulse. The genre is crowded and the readers are quick to dismiss anything that looks like soft fantasy in a stat-block coat. But I think the way to signal genre is to use the messages well, not to use them often. You have gained the Greater Fireball skill, used once at a turning point, signals genre more clearly than fifty per-hit damage lines, and the reader who would have bounced off your book over a missing readout is not going to be won back by readouts that exist purely to exist.
The thing the best LitRPG writers seem to know in their bones is that the popup is a narrative tool, not a quota. Travis Bagwell uses them sparingly in the Awaken Online books and they hit harder for it. Andrew Rowe in Arcane Ascension uses them for milestones and assessments rather than combat play-by-play. Even authors who lean very hard into the crunchy end of the genre, like Aleron Kong in The Land, tend to cluster their readouts at the moments where the numbers are the point. None of these writers are minimalists. They just understand that a tool used everywhere stops being a tool, and that the readers and listeners who pay your bills can tell the difference between a stat block that earned its place and a stat block that was reflex.
Common questions about LitRPG system messages
Should I cut all repetitive system messages from my LitRPG?
No, and authors who do this tend to end up writing soft fantasy with a stat sheet glued to the cover. The fix is collapsing repetition into summary lines and reserving full readouts for moments where the numbers carry weight, not stripping the genre's signature element out of the book entirely. The readers who want crunch will leave if you over-correct, and the listeners who want flow will leave if you don't correct at all.
How many system messages per chapter is too many?
There isn't a clean number, but my rule of thumb is that if more than one or two stat blocks in a chapter could be summarized in prose without losing information or feeling, you have too many. The test is not count but redundancy. A chapter with ten meaningful readouts can read tight; a chapter with three identical ones reads padded, even though it has fewer lines of system text on the page.
Do system messages hurt LitRPG audiobook reviews?
Yes, and consistently. The most common one-star audiobook complaint in the genre over the last two years has been narrators reading stat blocks for fifteen minutes straight. Authors who write with audio in mind, by using summary lines and meta-narration like Azarinth Healer and Chrysalis do, see noticeably fewer of those reviews even when the book is dense with mechanics. It is, in my view, the single biggest unforced craft error in the genre right now.
What's the best way to handle damage numbers in a fight scene?
Almost always with a single representative line and a prose summary, not a per-hit readout. Show the damage formula once, indicate scale (a hundred zombies, all roughly the same), and let the prose carry the choreography. A reader who wants the crunch gets it; a reader who wants the action doesn't have to wade through fifty near-identical popups to find it, and the audiobook listener gets a scene that moves instead of a spreadsheet read aloud.
Are LitRPG system messages worth keeping at all in 2026?
I think yes, and the genre would be poorer without them. They are part of what makes a LitRPG feel like a LitRPG, the way a procedural feels like a procedural because of the case file. The problem the genre is grappling with is not whether to keep the readouts, but how to write them so they survive contact with the audiobook listener, and the writers who solve that problem are the ones whose careers will compound through 2027 and beyond.
by Jacob Tam · May 26, 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.