Stat blocks belong in your LitRPG only when they earn the page they take up. The default reading experience for a stat block is for the eye to glaze over it, and if your blocks are not paying for that cost with information the prose cannot carry, you have a problem no amount of genre convention will solve.
This piece is aimed at the person who is writing or about to start writing a LitRPG, and who has been quietly worrying about the stat block problem. If you have read more than a handful of books in the genre you have probably noticed that nobody can agree on this, and that the people who care about it tend to care a lot. So I want to lay out my view, and I want to be upfront that everything I say below can be, and has been, successfully contradicted by published authors who are doing very well. There is no universal rule. There is a debate, and you are going to have to take a side whether you mean to or not, because every chapter you write is a vote.
My feeling about this is simple. Stat blocks belong in your LitRPG, but only if they are earning the space they take up on the page. The default reading experience for a stat block is that the eye glazes over and the reader skips down to find the next paragraph of actual prose, and if that is what most of your stat blocks are doing in your manuscript, you have a problem that no amount of "but it is part of the genre" will solve. Genre conventions are not free. Every convention you use was, at some point, justified by a writer who used it well, and now we copy them and forget that part.
Why do so many LitRPG readers skip stat blocks?
Readers skip stat blocks because the average block is a receipt for something the prose has already proved. The argument against stat blocks is mostly an argument about pacing and immersion, and once you take it seriously you start to see why so many readers, including readers who love the genre, train themselves to scan past the boxes. A reader who is in the middle of a tense fight scene does not want to stop and parse a table of numbers, because the moment they drop into the table their pulse comes back to baseline and the scene loses tension. Worse, the table itself rarely contains information that changes how the reader experiences the next paragraph. 'Strength: 47, +12 since last chapter' tells you the character is stronger, but you already knew the character was stronger, because you have been reading about them getting stronger for the last fifteen chapters. The number is a receipt for something the prose already proved.
There is also a craft point that gets less attention. When a writer leans on stat blocks, the prose around them often gets lazy. If the stat block is going to do the work of telling the reader the character grew, then the writer does not have to find a way to show the growth, and the result is fiction that works as a spreadsheet but not as a story. I have read books where I could remove every stat block and the reader would lose nothing except a sense of bookkeeping, which is a strange thing to lose, because it suggests that the bookkeeping was the point.
So before I argue for stat blocks, I want to give that side its due. If you write a great LitRPG without a single stat block in it, you are in good company. Cradle by Will Wight, which most people would shelve next to LitRPG even though it is technically progression fantasy, has no stat blocks at all and has sold extraordinarily well. Mother of Learning uses almost none and is one of the most beloved web serials of the last decade. The genre does not require them.
When do stat blocks earn their place in a LitRPG?
Stat blocks earn their place when three things are true at the same time: the number on the page changes the story, the format itself has voice, and the reader has been trained to read the blocks. Miss any one of these and the block reverts to bookkeeping, no matter how clean the formatting or how clever the system.
The first is that the number on the sheet has to actually change the story. By this I mean that the value of seeing the number, on the page, in that moment, has to be greater than the value of having the prose carry the information. Consider the difference between 'Carl looked at his stats and noticed his Strength had crossed 30 for the first time' and the equivalent stat block. The prose version is fine. It carries the information and keeps you in Carl's head. The block version is only better if the exact number matters, if the reader has been trained to know what 30 unlocks, or if the format of the block itself adds something the prose cannot. If none of those things are true, the prose version wins, every time.
The second is that the format of the block has to have voice. Matt Dinniman's Dungeon Crawler Carl is the textbook case here, because the system messages in those books are characters in their own right. The dungeon AI is sarcastic, hostile, occasionally affectionate, and the boxes that deliver its output are written like a person speaking, not like a database query. When the system in your book has a voice, the boxes stop being interruptions and start being scenes. The reader leans in for them instead of skimming past them. If the system in your book is a faceless API delivering numbers, you are asking the reader to do work for nothing.
The third is that the reader has to have been trained to read the blocks. This one is on you, the writer. The first stat block in your book teaches the reader how to read every stat block that comes after it. If that first block is dense, unstructured, and full of stats that have not yet been explained, you have just told the reader that stat blocks in this book are a cost, not a payoff, and they will start skipping by chapter three. If your first block is short, has a clear structure, and contains exactly one piece of information that pays off in the next scene, you have taught the reader that blocks in this book are worth reading. The investment compounds. By chapter twenty, when you finally drop the long-form character sheet, the reader will actually read it.
Where do new LitRPG writers go wrong with stat blocks?
The three failure modes I see most often are the lore-dump character sheet, the combat-interrupting update, and the worldbuilding flex. Each one shows up in nearly every first draft I have read from a new LitRPG writer, and each one is fixable once you can name it.
The first is the lore dump dressed up as a character sheet. The writer has invented a beautiful, intricate skill tree, and the only place they can think to put it is in a giant stat block in chapter two. The reader, who does not yet care about the protagonist, is now being asked to memorize a system. They will not. They will skip the block and resent the book a little, and you have spent your goodwill on something the prose could have introduced one skill at a time, in scenes where the skill mattered.
The second is the combat update that interrupts action. The MC is mid-swing, the prose is doing its job, and then the writer drops a 'Critical Hit! +18 XP. Sword Mastery: 22 → 23.' in the middle of the swing. This almost never works, because combat prose is built on momentum, and the block stops the momentum cold. There are ways to do this. Shirtaloon does it in He Who Fights with Monsters by treating the system messages as a kind of internal monologue the MC is half-ignoring, which keeps the rhythm. But the default move, the one new writers reach for, kills the scene.
The third is the system message that exists only to flex the worldbuilding. You have a cool magic system. You want the reader to know it. So every time something happens, a box appears explaining the underlying mechanic. This is the LitRPG equivalent of an exposition dump in a fantasy novel, and it has the same problem: the reader did not ask. If your worldbuilding is good, it will leak into the prose naturally over many chapters. If you have to put it in boxes to get it across, the worldbuilding is not as good as you think it is, and the boxes are doing patch-up work.
How do you fix the stat blocks in your manuscript?
The most useful fix is to write your opening chapter twice, once with the stat blocks in and once without, and read both back. So my advice, then, comes down to a few practical moves, and I will deliver them as prose because if I put them in a list it will undercut my entire argument.
When you are writing your first chapter, write it twice. Write it once with the stat blocks in, and once without. Read both back. The version that loses the most by removing the blocks is the version where the blocks are doing real work. If the no-blocks version reads better, your blocks are bookkeeping, and you should cut them and let the prose carry the story. Then, in the chapters where you do keep blocks, ask of every single one: what is the one piece of information in this block that the next scene depends on? If you cannot answer the question, the block is decoration.
The other move, which is harder, is to give the system a voice. Even a single sentence of personality at the top of a status screen changes the reading experience completely. 'You have leveled up. The System notes, with what may or may not be approval, that you continue to survive against expectations.' That is not a database. That is a character. The reader will read every block from that system because the system is a person now, and people are interesting in a way that numbers are not.
The deeper truth, I think, is that the stat block argument is a proxy for a much older argument about what fiction is for. Readers who love stat blocks love them because the number on the page is a promise that the world is real and consistent, that the rules are stable, that the math will come out the same way every time. Readers who hate them hate them because the number on the page is a reminder that the world is fictional, that the writer is doing the math, that the rules were invented to make this scene work. Both sides are right. Your job, as a writer, is to pick the side you are writing for and then to write the blocks (or not write them) so well that the people on the other side will keep reading anyway.
That is the bar. It is a high one. But the writers who have figured this out are the ones whose names you already know.
Common questions about stat blocks in LitRPG
Should I include stat blocks in my LitRPG novel?
Only if each block does something the surrounding prose cannot. A stat block earns its place when the exact number on the page changes how the next scene reads, when the format itself has voice the way Matt Dinniman's dungeon AI does in Dungeon Crawler Carl, or when the reader has been trained over earlier chapters to anticipate what a given threshold unlocks. If none of those things are true, the block is bookkeeping, and the prose version of the same information will almost always read better.
Do all successful LitRPG novels use stat blocks?
No. Cradle by Will Wight, which most readers shelve next to LitRPG, has none. Mother of Learning, one of the most-read web serials of the last decade, uses almost none. The genre rewards stat blocks but does not require them, and a strong LitRPG without a single block is a perfectly viable book. The mistake is assuming you must include them because the genre does, rather than asking whether they belong in your specific story.
Where should the first stat block appear in a LitRPG story?
Wherever you want, as long as you remember that the first block teaches the reader how to read every block that comes after. If your opening block is short, has a clear structure, and contains exactly one piece of information that pays off in the next scene, you have trained the reader to read every block in the book. If it is dense, full of unexplained stats, and serves mostly to show off your system, you have trained them to skip.
How do I keep stat blocks from interrupting fight scenes?
Either fold the block into the protagonist's interior monologue the way Shirtaloon does in He Who Fights with Monsters, or save the block for after the fight is resolved. Combat prose runs on momentum, and the average mid-swing system message kills that momentum cold. If the information has to land during the fight, treat the system message as a voice your MC is half-listening to rather than a database query the reader has to parse.
What is the difference between a stat block and a system message?
A stat block is a structured table of numbers, usually a character sheet or status screen. A system message is a single line of in-world text from the system itself, often delivered with personality. The distinction matters because the failure modes are different. Stat blocks fail by being boring; system messages fail by being too frequent or by lacking voice. A book can lean heavily on one and barely touch the other.
by Jacob Tam · May 9, 2026
I run IlorisNovel, a platform for writers of serialized web fiction. If this kind of craft writing is your thing, the rest of the blog lives here.