Roleplay vs. Fiction
two fires, one craft

In any roleplaying community that also hosts writers, you will eventually find this thread: a general discussion of world building where a player and a novelist talk past each other. The player says a world is only as good as what a character can do in it tonight. The novelist says a world should be deep — consistent enough that a reader can feel the history under every page.

Both are describing their own medium perfectly. The novelist’s depth is the reader’s quiet pleasure; a world that continues past the margins is why a setting outlives its story. The player’s impatience is the table’s engine; a session where nothing is actionable is a session where nothing happens. This is not really an argument about worldbuilding — it is two people using one word for two different jobs.

One side’s virtue is the other side’s flaw: the writer’s polished, finished world is, to a player, a world with no seams, and the player’s loose, improvised world is, to a writer, one that won’t hold still. Neither is wrong — each is answering a different guest.

Discoverability is a reveal in fiction

In a novel, discoverability is something the author controls. The reader meets the world through a point of view, in an order you choose, and what they never see still steadies them, the way the hidden iceberg steadies the ship. A writer can bury a thousand years of history and have it pay off as texture, as voice, as the reason two characters hate each other on sight.

Discoverability is an encounter in roleplay

At a table, discoverability is spatial and social: players learn what they touch, whom they talk to, what they open. A compendium is not a campaign — lore that lives in a binder may as well not exist until an NPC, a letter, or a choice puts it in a player’s path. The GM’s version of the iceberg has to come with stairs and lit rooms: not less history, but the interesting parts placed where a character can trip over them.

Fiction keeps a private contract

A reader is doing quiet detective work the whole book: testing each new detail against the ones before it. Consistency in fiction is a contract with the reader — break it once and the spell thins, even if they cannot say why. This is why novelists keep world bibles: not to show anyone, but so page two hundred doesn’t quietly disagree with page two. The world has to survive being re-read.

Roleplay holds a shared canon

At a table, canon is co-written and social. Players remember what the GM forgot, repeat it, and build on it; by week six the world holds everyone’s contributions. A contradiction is not a manuscript bug — it is a coordination problem between people. The fix is a shared record: agree in session zero what counts, note what actually got established, and let the GM hold the line gently without owning the world. The goal is not a flawless setting; it is one everyone can agree on well enough to keep playing inside.

Fiction and roleplay differ most sharply in how much blank they can afford. In fiction you improvise freely in the draft, then the page freezes; a gap in the final world is either deliberate technique — mystery — or simply a hole. The reader cannot ask you to fill it, so a gap has to mean something on its own.

Roleplay is the improvising. The medium is a conversation, and a conversation needs room for the other person to speak. A GM who has canon for everything has accidentally written a novel and is reading it to an audience that wanted chairs at the fire. The craft is to build the edges and the pressures — the weather, the factions, the price of magic, what everyone wants — and leave the middle deliberately blank, so a player’s choice is what fills it. An empty room you built on purpose is not a gap. It is an invitation.

• Build toward the story’s questions. The best worldbuilding is the part of the world the story is actually about. Let the premise choose what deserves depth.
• Reveal through character. History lands harder as a grudge, a superstition, a family name than as a paragraph of dates. Your narrator is a filter — use it.
• Keep the iceberg a secret. Depth you never show still steadies the book. If a cool fact does not serve a scene, cut it without grief — it can live on in the bible and color your voice for free.
• Track the canon. A small bible of names, dates, and rules stops the quiet contradictions that erode a reader’s trust fastest.

• Run a session zero. Agree on tone, on what is true, and on how the group records canon. Ten minutes up front saves ten arguments later.
• Build the edges, leave the middle blank. Detail what presses on the players — the faction, the season, the debt — and leave the interesting empty rooms for them to fill.
• Set hooks, not lectures. A rumor, a wanted poster, a locked door with a name on it teaches a world faster than a history lesson, and it asks the players to act.
• Let contributions stick. When a player invents a brother, a ritual, a street, say yes and make it canon. A world the players have written in is a world they’ll protect.

None of this is a fence. The crossover is the point: a fiction writer who plays learns which of their details a player would actually touch; a GM who writes learns which improvised choices deserve to become canon. Both trades run on the same truth — a world earns belief when consequences follow and there is room left for someone else in it. For a reader, that room is in the imagination, and a world that leaves it open gets re-read. For a player, the room is a chair at the table, and a world that leaves it open gets played in for years. Same hospitality — two ways of pulling up a chair.

The debate this guide grew from: “General Discussion on World Building,” a long-running community thread on RP Nation where roleplayers and fiction writers argue exactly this question past each other — rpnation.com/threads/general-discussion-on-world-building.568638. The positions above are our own reading of that divide; bring your side of it to the fire.