Fantasy Writing Software for Lore, Rules, and Chapters
Fantasy novels create an unusually large memory problem. A manuscript can contain invented geography, political structures, magic rules, terminology, long timelines, large casts, and promises that pay off hundreds of pages later.
Fantasy writing software is most useful when it keeps the draft connected to the rules, places, factions, and promises readers rely on. In Quilly, World holds reference entries, Characters holds the cast, and plot points connect those records to important turns in the chapter manuscript. You choose the structure; it does not generate a complete fantasy world for you.
- Record the cost of a power before it solves a major problem.
- Connect lore to decisions instead of collecting unrelated detail.
- Carry selected series material forward as independent copies.
Choose the setting facts that constrain the plot
Fantasy often creates more reference material than the next chapter needs. Start with the rules that limit action: who controls passage, what magic costs, how an object changes hands, and which promises or loyalties matter. These are the facts most likely to produce a contradiction after a structural revision.
Use Quilly's flexible World categories and editable template fields for those facts. Add a category for magic rules, relics, schools, or another recurring reference only when the book has a reason to consult it. A category is useful because it answers a question, not because every fantasy setting is expected to have one.
A worked sequence: healing has a price
A healer can close another person's wound only by taking the same injury. Record the ability, cost, limit, and who knows the rule. The reference makes a later rescue meaningful because the healer must accept a consequence rather than simply use a convenient power.
The chapter's major plot point is the healer choosing to help an enemy. Beats can show the refusal, the discovery of a shared danger, and the decision to take the injury. Connect the healer, the enemy, the rule, and the event that created their conflict.
If a relic later stores an injury, record the limit that remains: perhaps it works once and then breaks. Plant its earlier appearance in Foreshadowing. The exception should be prepared in the manuscript, not merely explained in an internal world note.
Keep multiple factions and viewpoints understandable
Store a faction's purpose, members, allies, and relevant constraints as reference information. Keep a character's current knowledge separate from the reader's knowledge. A scene in one viewpoint does not automatically authorize another character to act on the same fact.
Use connections and relationship views to inspect the relevant people and places around a plot point. When an allegiance changes, reread the consequences in the affected chapters. The graph provides a map of recorded connections, not an assurance that every implication is represented.
Plan the series without assuming live canon synchronization
When creating a continuation book, Quilly can copy selected characters, world material, plot points, events, and foreshadowing from earlier series books. The new book receives separate records. Images are not transferred, and old chapter references are removed.
Before drafting the sequel, review which facts are permanent and which have changed since the previous ending. A destroyed city, altered alliance, or newly understood magic limit needs a deliberate starting state. Editing one copied record does not automatically revise every earlier book.
Draft first, then run a focused world pass
Use the manuscript to write the scene rather than trying to perfect the entire setting beforehand. After a section is drafted, review the world rules it uses, objects it moves, and promises it plants. Check setup and payoff passages together after major cuts.
The current planning tools support that manual review. Story Health is coming soon in Author and is excluded from Writer and the trial; it should not be the reason to postpone a consistency pass on the draft you have today.
Fantasy story questions and their working home
| Question | Keep the reference in | Connect it when |
|---|---|---|
| What can this power do and cost? | World rule entry | A character uses or breaks the rule |
| Who owns the relic now? | World object plus relevant events | Ownership changes the available choices |
| Why does this ally betray the group? | Character motivation and relationship notes | The betrayal becomes a plot point |
| Where was the exception prepared? | Foreshadowing | A later payoff depends on it |
| What changed between books? | The continuation book's copied references | You establish the sequel's starting state |
Build one fantasy chapter from a constraint
Test your worldbuilding against an action rather than expanding lore in isolation.
Pick a rule that creates a cost
Define what the protagonist cannot solve easily and why the limit matters.
Record the minimum canon
Add the people, object, location, or rule you need to consult for this chapter.
Plan the consequential choice
Connect those references to a plot point and break a complicated turn into beats.
Check the exception on the page
Reread the setup, action, and consequence to see whether the solution feels earned.
Frequently asked questions
Can I customize fantasy worldbuilding categories?
Yes. Quilly supports custom World categories and editable template fields. Genre suggestions are starting points that you can change.
Does Quilly generate my fantasy world's lore?
This workflow uses author-created reference entries, outlines, and prose. It is not a promise of automatic world or manuscript generation.
Can I reuse the setting for a sequel?
Continuation-book setup can copy selected world and character material from earlier series books. The copies are independent and do not automatically synchronize; images are not transferred.
Does Quilly automatically catch every broken magic rule?
No. Use the reference and connections to support a manual consistency pass. Upcoming Author Story Health diagnostics are not included in Writer or the trial and are not a guarantee of complete error detection.