High fantasy roleplay: worldbuilding, battles and long campaigns

High fantasy is less about darkness and more about scale: maps, histories, a party with distinct voices and battles that matter. The hard part is consistency over hundreds of turns.

A photograph that sets the mood for high fantasy roleplay — Photo by Boston Public Library on Unsplash

What a high fantasy campaign needs

High fantasy works when the world feels bigger than the scene. The model needs to remember that the elves distrust the river kingdom, keep three party members sounding different, and run a battle where the outcome follows from what happened rather than from narrative convenience. It also needs to write real combat: people die in wars, and a dragon attack that injures nobody is a cutscene.

Where mainstream models fall short

High fantasy is mild compared to horror, so outright refusals are rarer. The issues are softer. Filtered models pull punches in combat, keep companions alive no matter what, and steer every conflict toward negotiation. They also tend to give every NPC the same earnest voice. And if your campaign wanders into adult territory, a romance between party members or a brutal siege, a filtered model may refuse partway through a session you have been running for weeks, which is the worst time for it.

Worldbuilding that the model can use

Lorebook over card. Put nations, gods and history in a lorebook with keyword triggers. The card should hold only the narrator's role and the current situation.
Voice lines for each companion. One sample line per party member ("Brannoc: 'Aye, and I'll carry the dead ones too.'") anchors their speech better than a personality list.
Keep a running summary. Even with a 1M context window, a short "story so far" in the author's note helps the model weigh what matters.
State the stakes of battle. "Combat is dangerous; named characters can be wounded or killed" gives permission the model will otherwise not assume.

Sample game master prompt

You are the game master of a high fantasy campaign. Narrate the world, play every
NPC and companion, and never act or speak for {{user}}.
Keep geography, politics and history consistent with the lorebook.
Each companion has a distinct voice; keep it.
Combat has real stakes. Resolve actions fairly from the situation, describe
injuries honestly, and let poor choices fail.
End turns with a clear situation {{user}} can respond to.

Samplers and model choice

Temperature 0.85 to 0.95. You want invention for names and places, but battles need clear cause and effect.
Min-p 0.05.
Repetition penalty about 1.05. Fantasy prose loves "ancient" and "mighty".

outlaw-1 is the sensible start for a long campaign. Its 1M context and low price let you keep months of play in memory. If you run tactical battles with many units and want the model to reason through positions, glm-5.3-outlaw is noticeably better at that kind of bookkeeping. Both are listed with prices on the pricing page.

Failure modes and fixes

Companions merge into one voice. Add their sample lines to an always-on lorebook entry.
World facts drift. Check the triggering keywords; an entry that never fires does nothing.
Nobody ever dies. Tell the model explicitly that companions can die and that this is part of the story.
Turns end with "What do you do?" every time. Ask for varied endings: a line of NPC dialogue, an interruption, a choice.

FAQ

How do I keep a long fantasy campaign consistent?

Put world facts in a lorebook with keyword triggers, keep a short running summary in the author's note, and use a model with a large context window so earlier sessions are still visible.

Can the AI run combat fairly?

It can if you tell it combat has stakes and that bad choices fail. For tactical fights with many moving parts, the full GLM 5.3 Outlaw reasons through positions more reliably.