How to write fantasy: rules and magic
The most common problem in fantasy manuscripts isn't a lack of imagination — it's too much freedom: if magic can do anything, nothing in the story is genuinely at risk, because the protagonist can always find a spell that solves the problem. A magic system works when it's, first of all, a system of limits.
The rules need deciding before the climax, not during it
The classic mistake is inventing magic's rules as the plot needs them: a new power shows up exactly when the protagonist needs it to escape a dead end. The reader reads it as a deus ex machina, even if it's "magical" and therefore in theory plausible within the book's world.
The magic system's rules — what it can do, what it can never do, at what price — need to be fixed before writing the scenes that will use them, ideally before writing the first chapter. If the climax requires a power the established rules don't allow, the fix isn't changing the rules at the last minute: it's changing the climax.
Cost is more interesting than possibility
Magic with no cost is a structural problem, not just a plausibility one: it removes tension, because every obstacle becomes surmountable with the right tool. The cost can be physical (pain, exhaustion, years of life), material (rare components, objects that get used up), or relational (a debt to an entity, a reputation to pay with).
The most effective cost creates a dilemma, not just a price: a character who can save someone but knows they'll use the last of the energy they have, or who gains a power at someone else's expense, produces a scene with moral tension as well as physical.
Show the rules through use, don't list them
A block of explanation — "in the kingdom of Aldar, magic worked like this: first, second, third..." — is almost always the least effective way to communicate a magic system. Readers learn the rules better by seeing them applied: a character who fails a spell for a specific reason teaches more than a paragraph listing the limits in the abstract.
The first times magic appears in a scene are the chance to establish what's possible and what isn't, through action. Any later exception to the rules established that way needs an explanation, or the reader feels cheated.
Internal consistency: magic has to answer the same questions as physics
A consistent magic system behaves like a consistent physical system: if a spell requires eye contact in one scene, it can't work through a wall in the next without an explanation. Fantasy readers are often readers who notice system inconsistencies more than they notice prose errors, because the magic system is the central contract they accepted by picking up the book.
Keeping an explicit list of the rules established — what's been shown to be possible, what's impossible, which exceptions have been justified — keeps the book from contradicting itself a hundred pages later.
Worldbuilding: how much to tell, how much to leave off the page
A fantasy world needs a coherent history, geography, and politics behind the scenes, but only a fraction of that work should reach the page. The useful question before any piece of lore exposition is the same one that applies to any background information: does the reader need this to understand this scene, or is it just interesting to you, who built it?
Invisible worldbuilding — the part that informs the characters' choices and the world's coherence without ever landing in an explanatory paragraph — is almost always what makes a world believable, more than the sheer quantity of detail actually narrated.
The protagonist shouldn't have the strongest power
A common early-draft mistake is giving the protagonist, early on, a power that outstrips everyone else in the world. It drains tension from every later confrontation, because the reader already knows how it'll end. A protagonist who has to find clever solutions because their power isn't enough, or who has to pay a steep price for every win, stays interesting far longer than an all-powerful one.
Keeping rules, geography and history together as you write
A fantasy novel piles up more background material faster than memory can hold: place names, power hierarchies, magic rules established chapter after chapter. In NovLore, the work's story bible in the dashboard keeps all of it in one place, reachable while you write, and the AI assistant reads it to help you check that a spell in chapter thirty doesn't contradict a rule set in chapter three.
Frequently asked questions
Does the magic system need to be fully explained to the reader?
No. It needs to be consistent for you as the writer, but the reader only needs the rules that affect the characters' choices in the story they're reading. A system richer than what's shown on the page is normal, and it's often what gives the sense of a world that's alive beyond the book's edges.
How strong can the protagonist's power be?
Strong enough to make them credible in their role, but not so strong it removes tension. A good test: if the protagonist can solve most problems with their main power, they probably need more limits or a higher cost.
Is too much worldbuilding detail a problem?
Not if it stays in your notes. It becomes a problem only when it all lands on the page: history and geography descriptions that don't serve the scene at hand slow the pace without giving the reader anything they need at that moment.