In 1997, a game designer named Raph Koster sat down to write a postmortem about Ultima Online, one of the first massively multiplayer games ever built. His team had spent years designing an ecology system where animals would breed, predators would hunt prey, and resources would flow through a simulated food chain. It was brilliant on paper. Players were supposed to discover this living world and feel like they'd stepped into a fantasy novel.
They killed everything in about forty minutes. Every deer, every wolf, every rabbit. The entire ecology collapsed on day one because the designers forgot something fundamental: players don't experience systems the way designers intend them to. They experience systems the way systems let themselves be experienced.
Koster wrote about this for years afterward, and it became one of the foundational stories in game design. But I think it matters even more for fiction writers, especially anyone working in LitRPG, because the problem isn't really about games at all. It's about the gap between how a system looks from the outside and how it feels from the inside.
The Stat Screen Is Never the Story
There's a version of LitRPG writing that reads like someone copied a spreadsheet into a Word document. You've probably encountered it. A character levels up, and you get fourteen lines of stat changes, skill acquisitions, and damage modifiers. It's technically accurate to how a game works. It's also completely dead on the page.
Travis Deverell figured this out early with Dungeon Crawler Carl. His stat screens exist, but they're woven into the narrator's voice so thoroughly that you almost forget you're reading game data. Carl reacts to his notifications the way you'd react to a parking ticket, with annoyance and sometimes disbelief and occasionally a grudging recognition that the system has a point. The mechanics become characterization.
Andrew Rowe does something different in his Arcane Ascension books. Corin obsesses over his magic system the way an engineering student obsesses over circuit diagrams. The stats aren't interruptions to the story. They're the lens through which a specific, particular person sees his world. Take the system away and you'd lose the character.
I'm not sure why so many writers treat their game mechanics as separate from their prose, like a technical manual you have to periodically consult. The best LitRPG writing tips I can offer come down to this: if your reader could skip the stat block and miss nothing, the stat block shouldn't be there.
Progression Has to Cost Something Real
Will Wight's Cradle series sells millions of copies and half of those readers couldn't tell you Lindon's exact power level at any given moment. What they can tell you is that every advancement he earns costs him something he cared about, sometimes a relationship, sometimes his safety, sometimes months of grueling work that Wight doesn't skip over or montage past.
This is where game mechanics in fiction diverge from game mechanics in actual games. In a video game, progression is a reward loop. You do the thing, you get the number, the number goes up, dopamine fires. In a novel, progression without friction is just inflation. Nobody cares that your character went from level 40 to level 41 unless level 41 meant giving something up or making a choice that can't be reversed.
Mother of Learning by Domagoj Kurmaic understood this instinctively even though its main character is stuck in a time loop where, theoretically, nothing is permanent. Zorian's growth feels expensive because the currency isn't hit points or mana, it's his willingness to engage with people he'd rather avoid and confront problems he'd rather postpone and slowly, painfully accept that being talented isn't the same thing as being competent, which is itself not the same as being wise, and that realization keeps unfolding across hundreds of chapters in ways that a simple leveling system could never capture.