Guides · Simulation
How town simulation works
A simulation pass is not “ask the model for a story.” It is a structured month: roster-aware arrivals, dated events, social changes, and optional macro pressure — then a results panel you can accept or walk away from.
One town vs the world
Monthly simulation advances a single settlement. World Simulate runs the selected towns in one pass, which is what you want when the party is on the road and three places should age together. You can run 0–24 months; 0-month intake adds people without ticking the clock.
What a month can change
- Arrivals — new residents, names unique against the existing roster, statted server-side where we can (abilities, HP, AC) so the model is not inventing math.
- Births and deaths — births are detected from the month’s story as well as explicit events. The graveyard keeps cause of death.
- Social — friendships, rivals, marriages, factions, incidents with witnesses and motives.
- Progression — XP logs and optional AI level-up later, on the sheet.
- Buildings — construction constrained by biome. No docks in a desert unless you overrode the setting.
- Macro / food — an abstract granary index from local food supply, not a sack-of-flour inventory. It is a pressure gauge for the region, visible on Dashboard and roster.
Results you can read
After a run, tabs split Summary, Arrivals, Births, Deaths, Social, Progression, Roles, and Buildings. Town History keeps the months. That log is the difference between “the AI said something” and “last Frostmonth the cooper died and the miller married.”
What you configure first
Town Settings (biome, demographics, food, intake level, generation rules) and campaign Settings (description, house rules, death thresholds, relationship speed, conflict frequency) are injected into the sim prompt. If the world feels generic, those fields are empty. If it feels too bloody, turn conflict down before you blame the model.
Maps and travel
Pin towns on an uploaded map and set scale. Inter-town moves during a world pass can use those distances. This is not a relationship graph pretending to be geography — see the calendar guide for tying travel to dates.
Simulation uses your configured models and credits. Preview when you can; applied months are history.