Worldbuilding Tips for Fantasy Web Novels and Power Systems
Our advice for worldbuilding a fantasy web novel: build only what your story needs, keep it consistent, give every power a clear limit, and reveal lore when a scene needs it. For cultivation, LitRPG and progression fantasy, we'd add one more rule: plan your power tiers before chapter one, because every rule you publish becomes a promise.
This guide draws on three fantasy authors: Brandon Sanderson's three Laws of Magic, J.R.R. Tolkien's idea of a Secondary World, and N.K. Jemisin's case for immersion over explanation. It then applies them to serial problems like power creep, lore spread across hundreds of chapters, and reader theories in the comments. If terms like cultivation or LitRPG are new to you, start with the web novel genres guide.
Key takeaways
- Build what your scenes touch first. Sanderson calls the urge to keep building instead of writing "worldbuilder's disease."
- Sanderson's First Law ties magic's power to solve conflict to how well readers understand it, and his Second Law says limitations matter more than powers.
- Our advice: design the top of your tier ladder first, and make every tier add a new limit, weakness or cost, not just more power.
- Reveal lore when a character needs it, immerse rather than explain, and keep a series bible so chapter 400 agrees with chapter 4.
- In our view, reader theories are feedback on your foreshadowing. Log every continuity catch in your bible.
Start with the story, not the atlas
Story-first worldbuilding means you design the parts of the world your characters will actually touch, and leave the rest as a sketch until the plot asks for it. In our view, it keeps chapters coming and makes every invented detail do a job in a scene.
In his 2025 lecture notes on worldbuilding tools, Brandon Sanderson names the trap: "worldbuilder's disease," where building the world takes the place of writing the story. His remedies are practical. Give yourself deadlines, and build what serves your plot and characters.
Our advice for serial writers: remember that readers see chapters, not your wiki. A long history of the first dynasty earns nothing until a character's choice depends on it.
Build the three layers your scenes touch
Sanderson's notes split setting into three layers: physical, cultural and magic. A useful first pass (our advice) is to answer a few questions per layer for your opening arc only:
- Physical: Where does the first arc happen? What's the terrain? How long does travel take between key locations?
- Cultural: Who holds power here? What do ordinary people believe and fear?
- Magic: What can the protagonist do by chapter 10? What can't they do? What does it cost them?
Everything outside the first arc gets a one-line placeholder. You can deepen it when the story travels there.
Use Tolkien's consistency test
Tolkien argued that a fantasy world earns belief by staying consistent under its own laws. He made the case in "On Fairy-Stories," first given as the Andrew Lang Lecture at the University of St Andrews on 8 March 1939. It was printed in 1947 in Essays Presented to Charles Williams (publication history).
He described the storyteller as a sub-creator. In Tolkien's sense, a Secondary World is an invented world that readers enter in imagination, with its own laws. Our reading: when a scene breaks those laws, the reader's belief is at risk.
You can turn that idea into a quick test for any scene where your world's rules matter. These questions are our suggestion, not Tolkien's:
- Could this have happened earlier in the story under the same rules? If yes, why didn't it?
- If a character in chapter 12 had known this, would they have acted differently?
- Does it cost the same as the last time someone did it?
If an answer makes you wince, fix the rule or fix the scene. We think serials face this test especially hard, because a reader who binges meets old and new rules close together.
Sanderson's Laws of Magic, applied to cultivation, LitRPG and progression
In our view, Sanderson's three Laws of Magic are the most practical toolkit for designing a power system. They suit progression fantasy well, because cultivation realms and LitRPG status screens can be written as clear, rule-based systems.
First Law: readers must understand what solves the climax
Sanderson's First Law (2007) reads: "An author's ability to solve conflict with magic is DIRECTLY PROPORTIONAL to how well the reader understands said magic." Hard magic is a magic system with clear rules the reader knows, so it can fairly resolve conflict. Soft magic is magic that stays mysterious, which suits wonder and dread but can't fairly resolve a conflict.
Here's how that plays out in genre (original examples):
- Cultivation: Your hero breaks through mid-fight and wins. If readers learned in chapter 30 that a forced breakthrough can cripple a cultivator, the scene becomes a gamble they can weigh. If they never learned that, it reads as a free win.
- LitRPG: A hidden skill unlocks at level-up and happens to counter the boss. Show the skill's prerequisite several chapters earlier, or make the unlock cost something readers already know matters.
- Soft elements: A sealed ancient sect or a vague heavenly will can create problems and atmosphere. Just don't let them solve the problems.
Second Law: limitations are more interesting than powers
The Second Law, "Limitations > Powers," first appeared in Leading Edge issue 61 and was posted on Sanderson's site in 2011. Our take: what a character can't do forces choices, and choices make plot.
In his 2025 lecture notes on the Laws, Sanderson sorts limitations into three kinds: fundamental limits, exploitable weaknesses, and costs or consequences. He uses Superman as the example: kryptonite and his personal ethics both limit him. Applied to progression fantasy (our examples):
- Fundamental limits are things the power can never do. Qi can't restore lost lifespan. A skill can't target anything the user can't see.
- Exploitable weaknesses are things enemies can use. A sword-intent path fails inside formation arrays. A summoner's creatures vanish if the summoner is stunned.
- Costs and consequences are what using the power takes. Burning essence blood shortens a life. A forbidden skill consumes a permanent stat point.
Our advice for LitRPG writers: mana and cooldowns are costs, but they can fade into routine. Keep at least one cost that still hurts at high tiers.
Third Law: expand what you have before you add something new
The Third Law (2013) reads: "Expand what you already have before you add something new." Sanderson gives three methods: extrapolate, interconnect and streamline. His 2025 notes also frame them as guards against power creep.
- Extrapolate: If pills can raise a cultivation realm, who controls the herbs? What happens to a sect that can't afford them?
- Interconnect: Tie tiers to politics. If elder seats go to whoever reaches a given realm, every breakthrough becomes a political event.
- Streamline: If "qi" and "spirit energy" do the same job, merge them.
One trap to watch for, in our view, is the brand-new system at chapter 400, such as a second hidden cultivation path. Before you add one, check whether your existing system can deliver the same surprise.
How to design power tiers and avoid power creep
Power creep is the steady inflation of power that happens when each arc has to top the last, so strength grows faster than the story can give it meaning. Left unchecked, it can make old threats stop mattering and leave a bigger number as the only way to raise stakes. Our fix is to design the whole ladder before you climb it and make each rung add a limit as well as a power.
These tier-design rules are our craft advice, not laws:
- Design the ceiling first. Decide the highest tier your series will reach. Everything below gets easier to pace.
- Pair every power with a limit. Each tier should add a new limit, weakness or cost. A tier that only adds power is where creep starts.
- Widen the gaps. Early tiers can come quickly so readers feel progress. Later tiers should take longer, with an in-world reason.
- Keep lower tiers relevant. Numbers, formations, money and politics still matter. A peak expert can be poisoned, outvoted or outnumbered.
- Grow sideways between climbs. New techniques, allies and understanding let the hero grow without a new tier.
- Scale threats by what's at stake. A rival who threatens the hero's family can hit harder than a far stronger monster.
- Write down your math. In LitRPG, decide how stats scale before chapter one, and record the formula in your bible.
How to reveal lore across hundreds of chapters
Our advice: reveal lore when a character needs it, in the smallest dose that makes the scene work. A long serial gives you time, so you don't have to explain the world in chapter one.
Immerse first, explain later
In "Worldbuilding 101" (2015), N.K. Jemisin argues that the more your world differs from ours, the more you should immerse readers rather than explain it to them. She lays the idea out as an "Immersion Pyramid" and warns against info-dumping. Our reading for web novels: let readers meet a concept in action first, then fill in the rules once they care.
Put exposition inside conflict wherever you can: an argument over a pill's price, a bargain with a sect elder, a lesson where failure has consequences. A reveal can also end a chapter well, and our guide to writing chapter hooks covers how.
Use the iceberg, and re-anchor your terms
Sanderson's 2025 worldbuilding notes describe the iceberg technique: know far more than you show, so the visible part hints at the depth beneath. For serials, we suggest one extra habit, which we call re-anchoring.
A reader returning after a month may not remember what your fourth realm does. Slip a clause of context into the sentence ("the Blaze stage, when a cultivator can first fly") rather than stopping the story. Two more habits we recommend:
- Keep a reveal list: each lore fact, the arc where it changes a decision, and whether it's been revealed yet.
- Introduce roughly one new concept per chapter, so readers aren't juggling five new terms at once.
Lived-in details make the world feel real
In our view, a world feels lived in when its magic and history show up in ordinary life: prices, slang, jobs and chores. Sanderson's notes favor concrete detail over info-dumps.
Ask what your power system does to people who don't have it. Some original prompts:
- If cultivators can fly, what do city walls look like, and who pays for them?
- If spatial storage rings exist, what happens to porters and caravan guards?
- In a LitRPG world with visible levels, does anyone lie about their level?
These details can carry meaning too. Speaking to the Cornell Chronicle in 2023, Jemisin said that building a world from scratch makes it easier to reimagine our own. We'd suggest the gap between those with power and those without is a good place to start.
Keep a series bible
A series bible is a single reference document holding every fact your story has committed to, so a chapter written two years in agrees with the first. For a frequently updated web novel, it saves you from rereading old chapters to check a detail. Here's a template you can copy:
| Section | What to record | Example entry |
|---|---|---|
| Power rules | Each power's abilities, limits, weaknesses and costs | Flame tier: fire to thirty paces; full release causes a day of sickness |
| Tier ladder | Every tier, the planned arc, stat formulas | Blaze reached in arc 4; flight limited to minutes |
| Characters | Current tier, known skills, injuries, promises, secrets | Lin: Kindled, broken left hand (ch. 88), owes the Iron Sect a favor |
| Places | Geography, travel times, who controls what | Capital to Ashvale: 6 days by cart, 1 by flying sword |
| Factions | Leaders, goals, relationships, resources | Iron Sect: controls cold-iron mines, hostile to the Ember Path |
| Timeline | In-world dates for key events | Tournament begins three months after the flood |
| Terms | Every invented word and its short definition | Heart Flame: fifth tier, can restore others' qi |
| Reveal list | Planned lore, target arc, revealed or not | Sovereigns are bound to land: planned arc 7, not yet revealed |
| Open threads | Foreshadowing and promises to readers | Mysterious scar mentioned ch. 12, 140, 233 |
| Continuity log | Errors found, fix made, chapter updated | Travel time contradiction in ch. 201, corrected |
Update the bible when you write a chapter, not when you post it. If you keep a chapter buffer, that gives you a window to catch mistakes before readers do. Our guide to update schedules and chapter buffers explains how to build one.
How to handle reader theories and continuity errors
Our advice: treat reader theories as feedback on your foreshadowing, and treat continuity catches as free proofreading. In our view, both are signs that readers care about your world.
On ChapterChase, each chapter page has its own comment thread, and every novel has its own forum board with per-chapter discussion threads and megathreads. The forum guide explains how boards work, including the norm that spoilers belong in post bodies, not titles.
Reader theories
- Don't confirm or deny. A neutral "I love reading these" keeps the mystery alive.
- Read guesses as data. If many readers guess a twist, your clues are clear. Decide whether that's what you want before you change anything.
- Don't rewrite a planned twist because one person guessed it. A fair twist should be guessable.
Continuity errors
- Check the bible first. Confirm the error is real before you respond.
- Fix small details quietly, then log the change.
- If a rule break matters later, fix it and note the change briefly, or make it canon only if an in-world explanation genuinely fits.
For comments that go beyond continuity into criticism, see our guide to handling reader feedback and negative reviews.
Frequently asked questions
What are Sanderson's three laws of magic?
The First Law says an author's ability to solve conflict with magic is directly proportional to how well readers understand it. The Second says limitations matter more than powers. The Third says to expand what you already have before adding something new. Sanderson published them on his site in 2007, 2011 and 2013.
What's the difference between hard and soft magic?
Hard magic follows clear rules the reader knows, so it can fairly solve problems. Soft magic stays mysterious and works best for wonder, atmosphere and threats. Our advice is to keep cultivation and LitRPG systems toward the hard end if they resolve your climaxes.
How do you create a magic system for a web novel?
Our suggested order: decide what the protagonist needs to do and fail to do in the first arc. Then define the power's limits, weaknesses and costs, sketch the tier ladder from the top down, and record it all in a series bible.
How do you avoid info dumps in fantasy?
Our advice: reveal lore only when a character needs it, and deliver it through conflict such as arguments, bargains or lessons with stakes. Re-anchor unfamiliar terms with a short clause instead of a paragraph.
How do you stop power creep in a cultivation or progression novel?
We suggest planning your top tier first, making every tier add a limit as well as a power, and widening the gaps as tiers rise. Between climbs, grow the hero sideways and scale threats by what's at stake.
How we wrote this guide: the ChapterChase editorial team checked every statistic against the linked source, and labels our own advice as advice. Spotted an error? Contact us, or read more about us.
Build less, reveal better
In our view, strong fantasy worlds come from a few well-understood rules, applied consistently and revealed at the right moment. Build what your scenes touch, give every power a limit, plan your tiers from the top, and let a series bible carry the details. When your first arc is ready, set up your novel, cover, blurb and tags in the ChapterChase creator workspace. Publishing is free, and you post on your own schedule.