How to use the Magic System Generator.
Limits and costs create story possibilities. Define what magic cannot do before adding convenient new powers to solve a plot problem.
Make the workflow fit your task.
Define an ability, its cost and its limit before adding exceptions. Test ordinary uses and attempted abuses, recording what stops characters from solving every conflict with the same power.
- What you provide
- Fantasy setting and thematic constraints.
- What you get
- Rules, costs, limits and narrative consequences.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Magic can move heat but cannot create it.
Completed example
Warming one room chills another; practitioners must account for where heat comes from and who bears the cost.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Should readers know every magic rule immediately?
Reveal the rules needed to understand stakes and solutions. Keep your own record consistent even when characters have incomplete knowledge.
Why does a new power weaken the conflict?
Check whether it removes an established cost or limit. Foreshadow a bounded exception or resolve the problem using existing rules.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑