Building a Magic System That Holds Across Ten Books — The Five Questions

Magic is the promise fantasy keeps that no other genre can. It is also the trap that breaks more multi-volume projects than any other detail. A protagonist who cannot heal in book one and suddenly heals in book three without the plot earning it — that is not sloppiness, that is a broken pact with the reader.

If you are working on a fantasy novel, your magic system is the second architecture decision after the plot. It defines what your protagonist is allowed to solve, what stays impossible, and what magic costs. It decides whether your world feels like a universe with its own laws — or like a chess board where the author keeps adding new pieces when the plot needs them.

This article shows what hard and soft magic really separates, the five questions every functioning magic system answers, how Sanderson's three laws work as a diagnostic tool — and why consistency across book boundaries is the hardest, most important discipline in series fantasy.

Hard vs Soft Magic — Where the Difference Actually Is

Hard magic and soft magic are not two boxes. They are the endpoints of an axis, and every magic system sits somewhere on it.

In hard magic, the reader knows the rules. What can this magic do? What does it cost? Who is allowed to use it? What are its limits? The answers are established in the text before the protagonist uses magic for the plot. Brandon Sanderson's Mistborn Allomancy is the textbook case — sixteen metals, each with a specific effect, each with a clearly named limit.

In soft magic, the system stays mysterious. Gandalf is a wizard — but Tolkien never tells you what he can or cannot do. The reader does not know why Gandalf loses to Saruman in their duel, or why he holds off the Balrog with his staff. Soft magic is atmosphere, not mechanics.

Both work — but they are mutually exclusive when it comes to plot. Hard magic lets the protagonist solve problems with magic, because the reader can follow the solution. Soft magic demands that magic is not the plot lever — Gandalf does not save the Fellowship by spell, he saves them by strategy and sacrifice. The Ring is not destroyed by magic. It is carried into the fire on foot.

The trap: a writer who promises hard magic — detailed rules in the early chapters — and then activates a new, unnamed power in the climax has broken the pact. A writer who promises soft magic and then resolves mechanically in the climax has explained the atmosphere to death.

Before you build your magic system, decide where on the axis you want to sit. That decision steers everything else.

Sanderson's Three Laws

Brandon Sanderson has formulated the most useful tool for magic-system design. Three laws, all from his Tor.com essays and BYU lectures.

First Law: An author's ability to solve conflicts with magic is directly proportional to how well the reader understands that magic.

That is the hard/soft diagnosis in a single sentence. If your protagonist solves the climax through magic, the reader has to have known the solution was possible. Otherwise it is deus ex machina. If the reader knows nothing about your magic, magic cannot be the resolution lever.

Second Law: Limitations are more interesting than powers.

What your magic cannot do is narratively more valuable than what it can do. A protagonist who can heal anything has no conflict. A protagonist who can heal anything except her own sister has a plot from page one. Limitations are where tension lives — they force the protagonist into decisions that pure power cannot resolve.

Third Law: Expand existing magic before adding new magic.

If your system has sixteen metals in book one, do not build book two by adding five new metals — build it by deepening applications of the existing sixteen. Depth beats breadth. This is especially true across book boundaries — new magic layers per volume read like a world where the author keeps adjusting the rules.

These three laws are not commandments to follow blindly. They are a diagnostic method. When your magic system is not working, you ask: does the reader understand it well enough to track the solution? Are the limitations as clear as the powers? Does the next volume build on what exists, or does it tinker?

The Five Questions Every Magic System Has to Answer

Before chapter one, your magic system should answer five questions. If one stays open, the novel will wobble at that point.

Source — where does the magic come from? Gods? A material element like metals in Mistborn or Stormlight in the Knights Radiant? Genetics, like benders in Avatar? A pact with a higher power? The source defines who has access and who does not — and through that, the hierarchies of your world. Magic from divine favour produces different politics than magic from a genetic line.

Cost — what does magic cost? Life force? Memory? Material resources? Time? In Sanderson's Allomancy, allomancers burn metal — they have to ingest it, it runs out, they cannot cast forever. In Le Guin's Earthsea, every act of magic costs the inner balance of the world — you shift something, you have to compensate. Free magic is boring magic.

Limits — what cannot magic do? What stays out of reach, no matter how powerful the protagonist becomes? Cannot raise the dead? Cannot reverse time? Cannot compel love? That wall is not a weakness, it is structural promise. It tells the reader: against this wall, even your strongest hero will fail — and that is the point.

Who — who has access? All humans? A genetic elite? Chosen ones? Scholars after years of study? This answer defines the social tension of your world. If only a small caste can wield magic, your world runs on conflicts between mages and non-mages. If everyone can, it is about training and power gradients.

How — how is magic cast? Ritual? Word? Gesture? Concentration? Material focus? This mechanic is not detail, it is scene economy. Magic that needs a ten-hour ritual cannot be drawn in combat. Magic that works on a thought can be deployed anywhere — and therefore needs stronger costs and limits to keep tension alive.

If all five questions are answered and the answers interlock, you have a system. If one is missing, you have an element you will adjust later — and that is exactly where inconsistency creeps in.

Magic and Plot — Where the Trap Is

The deus-ex-machina risk is the biggest trap with magic in plot. It happens when the resolution of a conflict comes through magic the reader could not have anticipated.

Sanderson's First Law is the diagnosis. The practical question is: how do you tell whether your climax resolution is deus ex machina?

Three tests.

First test — foreshadowing test. Have you established the resolution mechanic at least twice before the climax? Once as a casual detail (someone mentions this magic exists). Once as a demonstrated effect (someone shows it in a lower-stakes context). If both are missing, the climax is deus ex machina, no matter how elegant it feels.

Second test — limits test. In the same breath you established the magic, did you also show its boundary? A protagonist whose magic can do anything is not a protagonist — she is a divine instrument the author wields when needed.

Third test — protagonist-action test. Does the protagonist actively decide her way through the conflict, or does the resolution happen to her? If a senior mentor suddenly appears and casts the problem away, it is deus ex machina. If the protagonist does something only she could do, because she learned something specific, it is legitimate climax magic.

Soft-magic novels sidestep these tests by not making magic the plot lever. Tolkien does not let Gandalf destroy the Ring — Frodo does, on foot, step by step. The magic is atmosphere, the plot is human. A writer who chooses soft magic has to put the resolution responsibility on the protagonist without magic.

Magic as Character Trait vs Magic as System

There are two modes of anchoring magic. Both work, but they demand different architectures.

Magic as character trait. Here magic is bound to individual figures — Gandalf's staff, Galadriel's mirror, Sauron's eye. The magic follows the character, not a system. In this mode magic is a narrative tool that marks figures — who has which power says something about their role.

This works in epic settings with clearly stratified character hierarchies. But it makes magic inconsistent — every mage has their own rules, because the magic is bound to them. That is soft magic at the character level.

Magic as system. Here every act of magic follows the same rules, no matter who casts it. Sanderson's Allomancy is system magic — a Mistborn and a Mistborn apprentice use the same sixteen metals by the same mechanics, only with different experience and strength. Magic is a law of the world, not a property of the figure.

System magic is harder to write in discipline — you have to keep the rules in your head and measure every scene against them. But it is narratively fairer. The reader knows the same protagonist will not suddenly learn new tricks unless the system allows it. Conflicts emerge from the mechanics themselves, not from the author's hand. Which mode fits your novel depends on the plot focus. If your story revolves around epic hero figures, character magic is strong. If it revolves around a world with its own laws, you need system magic. More on hero-figure architecture in the hero's journey in fantasy.

Magic Across Book Boundaries — The Consistency Challenge

This is where it gets brutal. Keeping magic consistent across books is the hardest discipline in multi-volume fantasy — harder than character consistency, harder than geographic stability, harder than plot memory.

The reason: readers track magic rules with a precision other world details do not get. If your protagonist could not heal in book one and suddenly heals in book three without the plot earning it, readers post about it. They post on BookTok. They write reviews with chapter references. Inconsistency in the magic system kills trust faster than any other world inconsistency, because magic is the explicit pact between author and reader.

Four typical traps across book boundaries:

Power creep. The protagonist gets stronger every book without a clear ceiling. By book five she can do everything that was impossible in book one. Stakes evaporate, because no wall remains. Sanderson's Third Law addresses exactly that — expand existing magic instead of adding new.

Cost drift. In book one magic costs life force. By book four the protagonist is tired but no longer really weakened. The reader notices the price has quietly fallen. Magic without a felt cost becomes wallpaper.

Limits forgotten. In book one you established that the dead cannot be raised. In book six someone raises a dead character — and the justification is "an old magic we did not know about." That is limits forgotten, and it breaks the pact.

Who-can-what mixing. In book one only the royal line can wield this magic. In book four an outsider casts it without explanation. The hierarchy of your world was magic-anchored — when you shift it without showing the hierarchical break, the whole political architecture falls.

The only solution is bookkeeping. A magic bible that records what was established in book one, and checks every later book against new innovations. A writer who maintains this by hand has an Excel sheet or a Notion workspace with hundreds of entries. That works — but costs hours per writing day. More on multi-volume consistency in why conventional tools forget your characters and the guide to AI novels without contradictions.

Concrete Example: Mistborn Allomancy

Brandon Sanderson's Mistborn trilogy is the textbook example of a hard-magic system that holds across multiple volumes. The Allomancy deserves a closer look.

Source. Allomancers burn metal in their stomachs. Each of the sixteen metals grants a specific power. The genetic line determines whether someone is allomantic — nobles historically had more access, but the Mistborn-system shifted lines during the Final Empire.

Cost. Metal supply. Allomancers have to carry metal — as a vial, as coin reserves, as backup in buttons. When the supply runs out, the magic is off. A Mistborn without a steel reserve is a normal person. That physical limit creates scene tension — Vin has to hoard metal, plan her reserves, fight her battles economically.

Limits. Steel pulls and pushes only metallic objects. Iron pulls magnetically. Pewter boosts physical strength but consumes the body faster — burn pewter too long and you collapse. Atium grants prophetic sight for seconds, but is extremely rare. Each metal has its specific wall.

Who. Mistings can use one metal, Mistborn all sixteen. Mistings are common, Mistborn are rare — historically a noble line, visibly shifted by Vin's existence. The social hierarchy of the world is allomantically grounded.

How. Swallow metal, burn it in the stomach, feel the specific power. Certain metals demand concentration and practice — pewter is intuitive, atium is dangerous.

In book one — The Final Empire — Sanderson establishes the system almost textbook-faithfully. Vin learns Allomancy from Kelsier, the reader learns alongside her. In book two — The Well of Ascension — Sanderson deepens the existing system: Hemalurgy is introduced as a related but distinct magic, without breaking the Allomancy rules. In book three — The Hero of Ages — he brings in the atium focus and the political-mythological ending, but the basic rules of the sixteen metals stay unchanged.

What Sanderson does not do: he does not suddenly add four new metals in book three. He does not solve a climax through unmentioned magic. He keeps the limitations clear — Mistborn die from pewter crash, die to a Mistborn warrior, die from an empty metal supply.

That is system magic, carried through three volumes, with the third Sanderson law applied: expand, do not add. More on world depth in the hub for fantasy writing tutorials, and on progressive magic systems with RPG mechanics in LitRPG and AI.

Where SYMBAN Fits Magic Consistency

SYMBAN is a writing studio for multi-volume projects. Magic consistency is the discipline where SYMBAN engages most directly — because it is the pain point that classical writing software cannot solve.

Magic rules in the inventory. What your magic can and cannot do, what it costs, who has access — you store this in SYMBAN as structured world information. Not as a wiki note, but as a checkable rule layer. If you established in book one that the dead cannot be raised, that rule is in the system across every subsequent volume.

Every scene checked against the rules. When a scene in book three, chapter twelve has a protagonist breaching her established limits, that surfaces — before the scene is finished. Power creep, cost drift, limits forgotten get caught automatically. You do not have to check every prior establishment yourself; the system does.

Who-can-what across book boundaries. If your world hierarchy is magically grounded, SYMBAN documents who in book one could cast which magic. In book five a new character from a different line gets flagged as anomalous if the in-plot justification is missing. The social architecture of your world stays stable.

SYMBAN thinks in series from the start — and magic is the detail at which multi-volume projects visibly break. A writer who chooses hard magic needs a system that does not just archive the rules, but actively checks them.

Magic-system design is the second architecture decision after the plot. Sanderson's three laws give you the diagnosis. The five questions — Source, Cost, Limits, Who, How — give you the construction. Mistborn shows how a system holds across books without being adjusted.

What is left is the discipline. A magic bible you set up before writing book one, and stick to until book twelve — by hand or in a tool. If you can do that, you have a world with its own laws. If you cannot, you have a chess board where the author keeps adding new pieces.

And that is the moment the reader stops believing.