You spent six months designing your magic system before you wrote a word. It has costs. It has limits. It has internal logic that you're proud of. Then you started drafting, and somewhere around chapter twelve a character did something with magic that doesn't quite fit the rules. By chapter twenty-two, you've got three different versions of how a particular spell works, depending on which scene you're reading.
This isn't a discipline problem. It's a structural one, and it has solutions that don't involve being smarter or trying harder.
Why magic systems specifically tend to drift
Plot details drift in every novel. Magic systems drift faster, and the contradictions hurt more. There are reasons for both.
Magic systems do load-bearing work. When a character can't open a door because the wards prevent it, that's a constraint that has to be consistent with how wards worked three chapters ago. When a swordsman can't unlock a door — well, swordsmen don't typically unlock doors with their swords, so there's no system to contradict. Magic carries plot weight that mundane elements don't.
The rules are invented, not borrowed. When you write about horses, you can lean on what horses are. When you write about your specific kind of fire magic, the rules exist only in your head and your notes. Anything you don't write down clearly is liable to mutate.
The rules feel obvious when you write them. A month later, you can't quite remember whether the cost was a day of fatigue or a week. You write the scene with what feels right in the moment. That feel is unreliable across a 100,000-word manuscript, let alone a series.
Soft rules become hard rules in the prose. Your design document says "magic requires concentration." Your chapter five says "a wizard cannot cast while in combat." Your chapter eighteen says "the highest-level wizards can cast in combat with effort." These aren't all the same rule. The prose has been making your soft rule progressively harder, and you haven't noticed.
Magic gets used as a plot solver. Around the climax, you need something to work that almost-but-not-quite fits the rules. You bend the rule slightly to make the scene work. You tell yourself you'll fix it in revision. You don't.
All of this is normal. Every writer working with a magic system runs into it. What separates the polished published novel from the wobbly draft isn't avoiding the problem — it's catching it.
The two kinds of magic system contradictions
Diagnosing the problem helps. Contradictions come in two flavors.
Rule-level contradictions are when your stated rules conflict with each other or with their applications. The rule says magic requires verbal incantations; a scene shows magic cast silently. The rule says one practitioner can affect one target; a scene shows one practitioner affecting twenty. These are catchable by comparing the prose against the rules.
Implication contradictions are subtler and more dangerous. Your rules are internally consistent, but their implications, fully worked out, would make your plot impossible. If healing magic exists and is common, why does anyone die of disease? If fire magic is easy, why are sieges hard? Readers feel these contradictions even when they can't name them. The world stops feeling solid.
Most working writers deal with implication contradictions by adding constraints: healing magic exists but is rare/expensive/limited; fire magic is easy but stopped by [specific defense]. The constraints have to be in place before the plot leans on them, not after. Otherwise you end up adding rules in book two that contradict events in book one.
How to design a system that doesn't betray you
Some design choices make drift much less likely.
Write the rules as constraints, not powers. Lists of what magic can do are easier to mutate than lists of what magic can't. "Magic can heal" invites scope creep. "Magic cannot regrow a limb, cannot bring back the dead, cannot heal a wound older than three days" is much harder to accidentally violate. Constraints are sticky. Powers are slippery.
Define the costs precisely. Vague costs ("magic is exhausting") drift. Specific costs ("an hour of work-magic causes a day of fatigue; ten minutes of combat magic causes the same") are harder to bend without noticing. Specific doesn't mean rigid — you can have variation, exceptions, edge cases. But you should know what you're varying from.
Decide what's known to whom. A character can only use magic the way they know how to. A villager who's seen one wizard heal a wound can't reasonably extrapolate that wizards can also raise the dead. Your characters' beliefs about magic are part of the system, and they can differ from the actual rules — which gives you legitimate room for surprise without contradiction.
Settle the hard cases before they come up. Can two practitioners combine power? Can magic affect magic? Does it work on the dead? On animals? On objects? On the magic-user themselves? If you've answered these in your notes before you draft the scenes that depend on them, you won't have to invent answers under deadline pressure that contradict scenes you'll write later.
How to catch contradictions while drafting
Design alone doesn't save you. You also need a working process during drafts.
Use a single source of truth for the rules. Not in your head. Not in the design document you wrote six months ago and haven't opened since. A live document you actually consult while drafting, that gets updated when the rules evolve.
Update the rules document when the prose deviates. This is the key habit. When you write a scene where magic does something not quite covered by your existing rules, stop and ask: is this a new rule, or a violation? If new, add it to the rules. If a violation, fix the scene. Don't leave it ambiguous.
Search before you write. Before drafting a scene that uses magic in a specific way, search your previous chapters for similar uses. Find out what you established. This takes 30 seconds with the right tool and saves hours of revision later.
Catch contradictions through tooling, not vigilance. Your attention is a finite resource. You can't reliably notice that the new scene you're writing contradicts a scene you wrote four months ago. A tool that surfaces those contradictions for you — comparing your draft against your established rules and earlier scenes — does the work your memory cannot.
How to fix the contradictions you've already written
If you're reading this with a draft that already contradicts itself, the fix is structured, not chaotic.
First, get the rules straight. Re-read your design notes, then read your draft for all uses of magic. Build a list. For each use, note what rule it implies. You'll see the contradictions clearly when they're listed.
Decide which version is canon. For each contradiction, pick one. Usually you keep the version that better serves the plot or theme. Sometimes you discover that a "contradiction" is actually two valid uses of the system that you hadn't connected — in which case you keep both and refine the rule to accommodate them.
Revise toward the canonical version. Every scene that uses magic gets checked against the now-clarified rules. Scenes that contradict get rewritten. This is unglamorous work. It's also the only way out.
Build the system that catches the next round. Whatever process let the contradictions accumulate in this draft will let them accumulate in the next. Change the process: a live rules document, consulted while drafting, with tooling that surfaces contradictions automatically.
Where Inkwarden fits
This is exactly the problem Inkwarden's design addresses. Your magic system rules live in the same workspace as your draft — not in a separate document you have to remember to open. When your draft references magic in a way that contradicts what you've established, the system can flag it. Your characters know their own relationship to magic, so when you talk to them about a scene, they respond from what they actually know about the rules, not from a generic chatbot's idea of fantasy magic.
The world encyclopedia keeps your rules connected to the scenes that depend on them. The timeline keeps the history of magical events consistent. The book editor lets you draft without losing the thread back to your system. The whole point of the tool is that the world stays honest while you write.
Join the Inkwarden waitlist if your magic system has been quietly mutating on you.
The bottom line
Magic system contradictions aren't a sign of bad writing. They're a sign that the rules of an invented system are harder to keep straight than the rules of the real world — and you're trying to do it across hundreds of pages and months or years of drafting. Design tight, write down what you commit to in the prose, consult the rules constantly, and use tools that catch the slips you'll inevitably make.
Your readers will notice contradictions even when they can't name them. The world will feel wobbly. Fix it at the source: a magic system that's solid enough to lean on, and a working process that keeps it solid as you write.