GameMaster
GameMaster is the agent you talk to when the question is about numbers instead of prose. Stat blocks. Abilities. Encounter balance. What-if simulations. Any time you need something generated, designed, or analyzed that has to stay consistent with your Magic System, GameMaster is the specialist Ishvana delegates to — and because he reads the active ruleset directly, everything he produces respects your project’s actual rules instead of defaulting to generic fantasy-RPG assumptions. If your ruleset says ability scores go from 1 to 20, GameMaster generates stats in that range. If your ruleset has a custom formula for hit points, GameMaster uses that formula. If you invented a ninth stat called “Aura” and defined how it interacts with everything else, GameMaster knows what Aura is when you ask him to make a stat block.
Home module
Section titled “Home module”GameMaster lives in the Edit workspace as a specialist panel, and he’s also reachable from the main Chat view as a selectable agent. The Edit workspace’s GameMaster panel is the dedicated interface — it has dice icons in the toolbar, generation buttons for each operation, and a message area for back-and-forth conversation about whatever you’re designing. The Chat view is for quick one-off questions where you don’t need the full panel.
He’s not available from most other modules directly. That’s intentional. Mechanics is enough of a specialized concern that you want to opt into it explicitly — from the Edit workspace when you’re working on a character, or from Chat when you have a specific mechanics question — rather than have GameMaster’s capabilities bleed into every tool.
Five things GameMaster does
Section titled “Five things GameMaster does”Freeform chat
Section titled “Freeform chat”The lowest-level capability. You type a mechanics question in plain language — “how should I balance a level 5 fire mage in our system?” — and GameMaster reads your active ruleset, checks your project context, and answers. He can cite your specific rules (“your ruleset’s fire damage formula is X”) and reference your existing NPC stat blocks if relevant.
Use this when you’re exploring and don’t yet know the specific operation you need. It’s the equivalent of asking a smart friend who’s read your system docs.
Stat block generation
Section titled “Stat block generation”Give GameMaster a description of a character, creature, or item and he’ll produce a complete stat block constrained by your active ruleset. “A grizzled bounty hunter from Grimnest, mid-30s, specializes in stealth and one-handed weapons.” GameMaster reads that description, picks appropriate stat values for your ruleset’s stats, runs the ruleset’s formulas to compute derived values, selects abilities that fit the concept, and hands you back a complete block ready to drop into a Legendry entry.
The key word is constrained. GameMaster doesn’t invent new stats or abilities — he works within the rules you’ve defined. If your ruleset has Strength, Dexterity, Constitution, Intelligence, Wisdom, and Charisma, he generates values for those six stats and nothing else. If your ruleset has a completely custom set of stats you invented, he uses yours.
Ability design New abilities
Section titled “Ability design ”Give GameMaster a concept for a new ability — “a spell that lets the caster see through a target’s eyes for one minute” — and he’ll draft it as a structured ability that fits your ruleset’s ability schema. Name, type, tier, cost, duration, range, cast time, effects, prerequisites, balance notes explaining why he thinks the cost and power level are appropriate.
The balance notes are the most useful part. A new ability is dangerous — it’s easy to accidentally design something that breaks the game math if you’re not thinking carefully about where it sits on the power curve. GameMaster compares the proposed ability against others in your ruleset and tells you, in plain language, whether he thinks it’s under-tuned, appropriately costed, or potentially overpowered. You can accept his suggestion, push back (“no, make it more expensive”), or use the output as a starting point and tune it yourself.
Encounter balance analysis
Section titled “Encounter balance analysis”Give GameMaster a party (your player characters or protagonist group) and a set of enemies, and he’ll analyze the encounter for balance. He runs the ruleset’s formula engine on both sides, computes effective combat power using whatever metric your ruleset supports, and returns a difficulty verdict — trivial, easy, moderate, hard, deadly — with a breakdown of which side has advantages in which dimensions.
This is not a generic challenge-rating calculation. It’s specific to your ruleset’s math. A ruleset where Hit Points scale differently than D&D will get an encounter balance analysis tuned to that scaling. If your system has a custom “threat rating” formula, GameMaster uses it.
What-if simulation
Section titled “What-if simulation”This is the operation most authors don’t realize they need until they use it. You tell GameMaster “if I raise this character’s Dexterity from 14 to 18, what changes?” and he runs the formula engine on both states — before and after — and reports the delta across every derived value. Attack bonus, damage output, initiative, skill modifiers, defenses, saving throws, anything that depends on the changed stat.
This is how you check whether a character arc upgrade actually matters mechanically, or whether a proposed ruleset change would accidentally break a character build you like. Run the simulation, see the delta, decide if it’s what you wanted.
Why GameMaster is kept separate from Hawken
Section titled “Why GameMaster is kept separate from Hawken”A question that comes up: why not just have Hawken (the writing coach) also handle mechanics? He could — Hawken is an LLM, and LLMs can do math in a pinch. The answer is that prose-craft and mechanics are different skills, and forcing one agent to do both produces worse output at both.
Hawken’s system prompt is tuned for narrative voice, rhythm, and continuity. When he reads a combat scene, he’s thinking about pacing and emotional beats, not about whether the damage math tracks. If you ask Hawken “give this character a stat block,” he’ll produce something that sounds right but often isn’t constrained properly by your ruleset — stats outside the allowed range, formulas he made up, abilities that don’t exist.
GameMaster’s system prompt is tuned for mechanical precision. He’s constantly checking against the ruleset, he’s using the formula engine to compute exact values, and his output is structured rather than prose. The tradeoff is that if you ask GameMaster to comment on the prose-craft of a combat scene, he’ll produce something technically accurate but dry — that’s outside the lane he was built for.
The split is the whole point of having specialists.
What GameMaster’s output looks like
Section titled “What GameMaster’s output looks like”A GameMaster response is usually structured, not prose. A stat block comes back as an actual stat block with stat values in the right shape. An ability design comes back with every field from the ability schema filled in. An encounter analysis comes back with a difficulty verdict plus a table of contributing factors.
When GameMaster does use prose, it’s usually for explanatory notes — “I picked Strength 14 because this character is described as ‘strong but not exceptional,’ and 14 is the middle of your ruleset’s strong-but-not-exceptional band.” The prose is commentary on the structured output, not a replacement for it.
The result is that GameMaster’s output can be copied directly into a lore entry’s stat block, or into the ruleset’s abilities table, or into a printable character sheet, without needing to be translated or cleaned up. Hawken’s lane is the prose readers will see. GameMaster’s lane is the stat block editor that powers it.
Activity tracking
Section titled “Activity tracking”GameMaster is one of the divine agents whose activity is tracked by the Agent Transparency system. You can see how many stat blocks he’s generated, how many abilities he’s designed, how many encounter analyses he’s run, and what his success rate looks like on each operation type. This is surfaced in the Analysis workspace and it’s how you tell whether GameMaster is pulling his weight or whether the model you have him running on is underperforming.
What GameMaster can’t do
Section titled “What GameMaster can’t do”A few limits:
- He can’t invent new stats. GameMaster operates within your active ruleset. If your ruleset has six stats, he generates six-stat blocks. He won’t add a seventh stat because the character concept “feels like it needs one.” If you want a new stat, you add it to the ruleset yourself.
- He can’t run live combat. GameMaster analyzes mechanical setup and individual rolls. He’s not a combat simulator that rolls initiative and runs a turn-by-turn fight for you. That’s a different class of tool, and it’s not what this agent is for.
- He can’t read your mind. If you give him a vague concept — “a powerful character” — he’ll make reasonable guesses about what that means in your ruleset, but the guesses will often be wrong. More specific input gets better output. “A level 8 fighter specialized in defense and battlefield control” is a better prompt than “a strong character.”
- He can’t override the ruleset’s validation. If the ruleset’s validator rejects his output (a formula error, a stat out of range), he has to redo the generation. Usually this just means the retry works fine, but occasionally it means the ruleset itself has a bug GameMaster can’t work around.