Magic Systems 101: How to Design Magic That Feels Fair

Magic can make a fantasy world feel enchanted, or it can wreck it completely. If a wizard can fix any problem with a spell, why does the story need anybody else? A good magic system produces wonder and tension at once. It hands characters power, then makes that power cost them something.

This guide covers the basics of designing magic for your RPG world. It also shows how to write the rules down so a Game Master, human or AI, can apply them the same way every time. That second part is close to my heart, because EchoQuest's Game Master reads the world rules that creators write, and a vague rule gives it far too much room to wobble.

Hard Magic vs. Soft Magic

Fantasy writers often describe magic on a spectrum, and the novelist Brandon Sanderson popularised the terms most people now use. His First Law of magic says "an author's ability to solve conflict with magic is DIRECTLY PROPORTIONAL to how well the reader understands said magic." For soft magic, he points to Tolkien. As he puts it, there's a reason Gandalf doesn't simply fly Frodo to Mount Doom: we don't know what his magic can do, so it can't be the thing that solves the plot.

• Hard magic has clear, knowable rules. Players understand exactly what it can do, so they can use it cleverly to crack problems.
• Soft magic stays mysterious and unpredictable. It stirs awe and dread, but nobody can count on it.

	Hard magic	Soft magic
Best for	Problem-solving, tactical play	Mood, mystery, horror
Player feeling	Clever, in control	Wonder, fear
Risk	Can feel mechanical	Can feel arbitrary

For RPGs, where players actually use magic, you'll usually want mostly hard magic for player abilities, with soft magic for the world's great mysteries. I'd go further and call that a rule. A novelist can keep the reader guessing, but a player who can't predict their own spell will stop casting it, and fairly so.

My own worlds lean on this split. In The Shattered Reaches, a dark fantasy world in EchoQuest's library, the rules note that magic is unstable and that spells may have unexpected side effects down in the Rift. That's soft magic on purpose, aimed at the scariest place on the map.

The Three Pillars: Source, Cost, Limit

1. Source: Where Does Magic Come From?

• Gods and pacts
• Study and formulae
• Bloodlines
• Natural energies (ley lines, stars, the sea)
• Artefacts and relics

The source shapes your world's politics. If magic comes from gods, temples hold the power. If it comes from study, the universities do. Sanderson's Third Law ("Expand what you already have before you add something new") pushes the same instinct. He suggests asking "what happens when" questions until the consequences fall out, such as what happens to warfare when magic can make food from thin air. Ask that sort of question about your source and you'll find half your plot hooks waiting.

2. Cost: What Does It Take?

Magic without cost has no drama. Costs can be:

• Physical: exhaustion, pain, ageing
• Material: rare components, silver, blood
• Social: fear, persecution, obligations to a patron
• Moral: corruption, lost memories, harm to others
• Risk: a chance of mishap every time

Tabletop games have been pricing magic for decades. In the current Dungeons & Dragons rules, casting a spell expends a spell slot, and finishing a Long Rest is what restores them. Some spells also eat a costly material component, which the caster has to actually own. That's a stamina cost and a material one stacked together, and it's why wizards in D&D spend so much time worrying about when they'll next get to sleep.

Here's something I learned building EchoQuest: a cost the game never enforces isn't really a cost. Until recently, hitting 0 HP in EchoQuest didn't carry a proper setback. I've since added one, because danger that never bites soon stops feeling like danger. Magic works the same way. If casting is supposed to exhaust you, the exhaustion has to show up in the story.

3. Limit: What Can't It Do?

Limits are the most important design choice you'll make. Common ones:

• Can't raise the dead
• Can't create something from nothing
• Can't affect someone who knows your true name
• Only works at night, near water, or while chanting
• Range, duration, or number of uses per day

True names have a long pedigree, by the way. In Ursula K. Le Guin's A Wizard of Earthsea (1968), to work a spell you need the true name of the thing you're enchanting, and as the National Endowment for the Arts' reader's guide quotes the book, "A mage can control only what is near him, what he can name exactly and wholly." That one sentence gives you a range limit and a knowledge limit together. The greatest wizards there do all they can to avoid casting, too, because every spell disturbs the balance of the world.

Sanderson sums the whole idea up in his Second Law: "Limitations > Powers." Superman isn't interesting because he can fly. He's interesting because of kryptonite and his own moral code.

Players are most creative when they push against clear limits.

Make Magic Say Something

The best magic systems echo the world's themes:

• In a world about greed, magic might be fuelled by gold, burned up with each spell.
• In a world about memory, casting might erase your own recollections.
• In a world about community, spells might need several casters working together.

Sanderson's own example is pleasingly cheeky. While designing Mistborn, he themed every power around what thieves would want and named each one after a role in a thieving crew, so the magic itself tells you it's a heist story. Here's a handy test for your world: drop your magic system into somebody else's setting. If nothing feels out of place, your magic isn't saying much yet.

I did something along these lines in The Iron Citadel, a steampunk world in the library. It has no magic at all. Instead, a rare few workers have resonance, the ability to physically interface with the Engines that keep the city alive. The world's notes warn that it's exhausting, and that it can turn dangerous in high-energy places. So in a story about workers worn down by machines, the one "magical" talent wears its users down too.

Sensory Signatures

Give each type of magic a signature your senses can catch:

• Fire magic: a roar like a furnace door opening, the smell of scorched air
• Necromancy: sudden silence, cold breath, the taste of iron
• Healing: warmth, a hum just below hearing

In audio-first games these signatures are how players perceive magic, and they make every spell memorable. Lucasfilm Games understood this back in 1990 with Loom, where you cast spells by playing four-note melodies called drafts on a distaff. The magic was literally music, and in my view few games since have made casting feel as personal.

EchoQuest has its own small version of this. When the GM decides a spell goes off, it can trigger a sound cue: a successful cast swoops upward two octaves with a soft hiss of air. A fizzle does the reverse, sliding two octaves down into a buzzy rasp. Getting those cues heard took real work, though. This spring I made the ambient soundtrack duck under sound cues, and I started dropping duplicate cues that fire within 80 milliseconds of each other, because a doubled chime sounds like two spells when you can't see the screen.

Writing Magic Rules for an AI Game Master

If you're building a world on EchoQuest, your magic rules go into your Game Bible. Write them clearly:

Tidecalling. Only people born on a ship at sea can use it. Tidecallers command water within sight. Each casting costs the caster a memory; they choose which. Tidecalling cannot affect water inside a living body. Its sign is the smell of salt and a sound like a wave breaking far away.

Clear sources, costs, limits and signatures let the AI Game Master apply the rules consistently and describe them vividly. When you upload a Game Bible, EchoQuest pulls the mechanical rules out of your document, magic systems included, and folds them into the brief the GM works from. It's told to take only what the document actually says, though, so whatever you leave vague, the GM will have to improvise. And if you'd rather build with the World Builder Wizard, one of its questions asks for a single hard rule the Game Master must respect. "Magic always costs blood" is one of the examples it offers, and it's a great place to start. Both routes come with the Storyteller plan's private world. See How to Write a Game Bible for the full template.

Common Magic System Mistakes

• No cost: magic becomes the answer to everything.
• Too many exceptions: players stop trusting the rules.
• Only combat uses: the best magic also solves social, exploration and mystery problems.
• Wizards everywhere: if everyone can do magic, it stops feeling special.

Of these, I think too many exceptions does the most damage, especially with an AI GM. Each exception is one more thing that can be misremembered in the middle of a tense scene. A short, firm rule beats a long, clever one every time.

Try It Out

Design one magic tradition with a source, a cost, a limit and a sensory signature. Then play a session with it. Nothing stress-tests a magic system faster than a creative player who has just spotted a loophole. So what will your magic cost?

Build your world with the World Builder Wizard →