← Back to Blog

Hard vs Soft Magic Systems: How to Build One AI Won't Break

Hard vs Soft Magic Systems: How to Build One AI Won't Break

You built the rule on page eleven. Ysolde, your debt-scribe, can bind a person to a promise by writing their true name on vellum, and every binding costs her one day of her own memory, gone for good. You liked that rule enough to underline it in your notes. Then you asked the model for chapter fourteen, the scene where three smugglers corner her in the archive, and she bound all three in a single paragraph, walked out, and remembered her whole week perfectly.

Nothing about the prose was wrong. The magic was. Once one scene breaks the rule for free, every earlier scene where she hesitated stops meaning anything.

What is a magic system?

A magic system is the set of rules, limits, and costs that governs how magic works in your story: who can use it, what it can do, what it can't do, and what it takes from the person using it. It doesn't have to be written down in the book. It just has to be consistent enough that the reader can feel when something is possible and when it isn't.

A system has three parts, and most writers spend their time on the wrong one:

  • Powers: what the magic does. Bind a promise, call fire, read a lie.
  • Limits: what it can't do, or the conditions it needs. Only true names work. Only on vellum. Only in daylight.
  • Costs: what using it takes. Memory, blood, years of life, a debt someone will come to collect.

Hard vs. soft magic: the actual difference

Hard magic has rules the reader understands well enough to predict, so characters can use it to solve problems. Soft magic stays mysterious, so it creates wonder and danger but can't be the thing that resolves the plot. Most published systems sit somewhere between the two.

The vocabulary comes from Brandon Sanderson, whose First Law of magic states: "An author's ability to solve conflict with magic is DIRECTLY PROPORTIONAL to how well the reader understands said magic." In that essay he puts Tolkien at the soft end. Gandalf is powerful, but nobody knows the limits of that power, and the story doesn't let him simply fly Frodo to Mount Doom. Asimov's robot stories, built on three explicit laws, sit at the hard end. Sanderson calls Harry Potter hard within each individual book and soft across the series, and he describes his own magic as roughly 80% hard.

The First Law is about payoff, not taste. If your climax depends on a magical solution, the reader has to have learned the rule beforehand, or the ending reads as the author reaching into the box and pulling out whatever was needed. If your magic is soft, that's a strength, but it means your characters have to win with something else: courage, cunning, a sacrifice, a friendship.

A quick way to place your own system:

  • Can a reader guess, before the scene, whether a spell will work? Hard.
  • Does the magic mostly cause problems rather than solve them? Soft.
  • Would explaining the mechanism make it less frightening? Keep it soft.
  • Does your climax hinge on someone using magic cleverly? You need it hard, at least for the piece the climax uses.

Neither end is better. A gothic horror novel where the house's power is never explained gets nothing from a rules appendix. A heist fantasy where the crew exploits a loophole in how wards work dies without one.

Why limits matter more than powers

Limits create the story, because a character who can do anything has nothing to struggle against. Sanderson's Second Law puts it bluntly: "Limitations > Powers." His summary line is the one worth taping above your desk: "Superman is not his powers. Superman is his weaknesses."

Think of it this way: the cost is the plot. Ysolde's power to bind a promise is a neat idea. Her losing a day of memory each time is a novel. Now every binding is a decision. By chapter fourteen she's done nine bindings, so nine days of her life are blank, and one of those days is the afternoon she met the man who now claims to be her brother. She can't check. The reader knows she can't check. Suddenly the magic system and the mystery plot are the same machine.

Good limits share a few traits:

  1. They're specific. "Magic is tiring" is a mood. "Each binding erases one full day, oldest first" is a rule you can build a scene around.
  2. They connect to the world. Vellum is expensive, so poor scribes write on scraps that hold bindings badly. The limit creates an economy, a class divide, and a black market in stolen calfskin.
  3. They force cleverness. When Ysolde faces three smugglers, she can't bind all three without losing three days. So she binds one, the one the other two take orders from, and has to make that single promise do the work of three.

That last point is where Sanderson's Third Law comes in: "Expand what you already have before you add something new." Before you give Ysolde a second power for the back half of the book, ask what the first one hasn't done yet. What happens if she binds herself? What if someone forges a true name? What do the scribes' guild's records look like if every member has gaps in her memory? One rule pushed to its edges beats five rules sitting side by side.

How to build a magic system, step by step

Start from what the story needs the magic to do, then design the limits that make doing it hard. Here's the sequence that works whether you're drafting by hand or with a model.

  1. Decide the job. Is the magic a tool your protagonist uses, a threat she faces, or atmosphere? This one answer tells you how hard it needs to be.
  2. Write the power in one sentence. "A scribe can bind a person to a promise by writing their true name." If it takes a paragraph, it's probably two systems.
  3. Write three limits. At least one should be a condition (only true names, only vellum) and at least one a cost (one day of memory per binding).
  4. Find the consequence chain. For each limit, ask: who profits from this? Who suffers? What crime does it make possible? Three questions, and you've got half your subplots.
  5. Name the exception you'll never use. Every system has a tempting loophole. Decide now that it doesn't exist, and write that down too. Ysolde can't restore lost days. Ever. Not even in the finale.
  6. Plant the rule before you need it. If the climax depends on a limit, the reader should see that limit cost someone something in the first third. This is the same discipline as setting up Chekhov's gun: show the rifle early, fire it late.

For a soft system, steps 1, 5, and 6 still apply, and for AI drafting a single line like "The house's power is never explained and never helps the protagonist" will stop the model from tidying your mystery into a mechanism.

Why AI drafts break your magic system

A language model breaks your magic because it can't see your rules at the moment it writes the scene, so it fills the gap with the most common fantasy magic it has read, which is usually powerful, cheap, and convenient. Ysolde binding three smugglers for free is the model writing an average fantasy scene, because nothing in its context said otherwise.

This is the same root problem behind AI forgetting your story details: the model doesn't remember chapter two, it only sees what's in front of it. And magic is especially vulnerable for two reasons. First, costs are boring to the model. They slow a scene down, and models drift toward tidy resolution. Second, a cost usually lives in a different scene from the one you're generating, so even a model with a large context window may not connect "binding costs a day" in chapter two to "she binds three men" in chapter fourteen.

A magic system the model can't see is a magic system the model will improvise. The fixes:

Write the rules as a short, standalone entry. Not your forty-page worldbuilding doc. A tight block, under 150 words, that states the power, the limits, the cost, and the loophole that doesn't exist. Phrase limits as hard constraints: "Each binding erases one full day of the scribe's memory. There are no exceptions. Bindings are never free." The lorebook entry format works well here: lead with the rule, not the history.

Put the rule in the prompt for every magic scene. If you're working in a plain chat window, paste the entry above your scene request every time magic appears. Yes, every time. In NovelMage the Character Codex does this for you: the AI references Codex entries automatically while writing, so a "Debt-Scribing" entry gets pulled into the scene without you copy-pasting it into chapter fourteen.

State the running cost, not just the rule. The model needs to know where Ysolde stands now. Add one line to the scene request: "Ysolde has performed nine bindings so far and has lost nine days, including the day she met Corran." That turns an abstract rule into a pressure the scene has to carry.

Ask for the limit to shape the action. "She can afford only one binding in this scene. Show her choosing who." A model that's told the limit is the point of the scene will write toward it instead of around it.

Audit after drafting. Search the chapter for every use of magic and check each against the entry. Did it cost what it should? Did anything happen that the rules forbid?

Keeping the system consistent over a whole book

Consistency comes from one source of truth you actually update, not from memory. Keep the magic entry in the same place as your character and location notes. That's the core idea of a story bible. When the draft reveals a new consequence (the guild keeps ledgers of members' lost days, it turns out), add it to the entry the same day.

A magic system is often the most original thing in a fantasy manuscript, and some writers would rather not send it to a cloud provider at all. NovelMage runs local models through Ollama or LM Studio, so your rules stay on your machine, or you can bring your own Claude, GPT, or Gemini key for a hard scene.

Frequently Asked Questions

Is Harry Potter a hard or soft magic system?
Both, depending on scale. Sanderson describes it as hard within each individual book and soft across the series as a whole. In practice that means the magic a given book's plot leans on gets shown before it matters, while the wider world of magic keeps expanding in ways nobody could have predicted. That mix is common and works fine, as long as the magic that resolves each book's climax was established earlier in that book.

Does every fantasy novel need a magic system with rules?
Every fantasy novel needs magic that behaves consistently, but not every one needs rules the reader sees. Soft magic can stay completely unexplained on the page. What you can't do is let unexplained magic solve the main conflict, because the reader has no way to judge whether the win was earned.

How much of my magic system should I explain to the reader?
Explain exactly as much as the plot uses to solve problems, and no more. If the climax depends on a specific limit, show that limit costing someone something early on. Everything else can stay in your notes. Dumping the full system in chapter one is an info dump, and readers skim it.

Can AI help me design a magic system, not just follow one?
Yes, and it's often more useful there than in drafting. Give a model your power and ask it for twenty possible costs, or ask who in your world would profit from each limit. Then pick, combine, and discard. The model is good at generating options and bad at knowing which one fits your book's themes.

Make the rules stick

The difference between a magic system that feels deep and one that feels convenient is almost never the power. It's whether the cost shows up in every scene that uses it, including chapter fourteen, when you're tired and the model is helpful.

If you want the rules pulled into every scene automatically instead of pasted by hand, you can try NovelMage free for 7 days. It's a $99.99 one-time lifetime license if you keep it, with no subscription, and your manuscripts stay on your device rather than on anyone's server.

Share this article

Loading comments...