Game Concept: Iron & Timber — The Muster

Created: 2026-09-12 Status: Draft

Elevator Pitch

It's a frontier city-builder where you manage a deep medieval economy in a
monster-haunted wilderness — and every tool you forge is also a weapon, every
worker you employ is also a soldier. When the horn sounds, your supply chain
becomes your army.

Core Identity

Core Fantasy

My town's strength is legible in its stockpiles.

The player is a frontier steward whose settlement is simultaneously an economy and a militia. There is no separation between the people who produce and the people who fight — the woodcutter who has been feeding the sawmill all summer is the same person standing on the palisade in autumn, carrying a spear the player chose to forge instead of a plough.

What the player can do here that they can't elsewhere: **look at their armory and know whether they survive the winter.** In Banished the wilderness is indifferent — it starves you but never comes for you. In Manor Lords the battles happen somewhere adjacent to the economy rather than emerging from it. Here, military readiness is a direct, visible readout of economic decisions made weeks earlier.

Unique Hook

**Like Banished, AND ALSO your entire population is a conditional militia whose combat effectiveness is a direct readout of your economy's health.**

There is no "recruit soldier" button. There is iron ore, a charcoal kiln, a smelter, a blacksmith, and a person who stops being a farmer. Every point of military capability was paid for in economic capability that no longer exists.

The hook affects gameplay at every level: the 30-second loop (does this iron become a plough or a spearhead?), the session loop (is the armory full enough for autumn?), and the progression loop (can I afford a standing guard yet, or does everyone still need to do double duty?).

Player Experience Analysis (MDA Framework)

Target Aesthetics (What the player FEELS)

Key Dynamics (Emergent player behaviors)

• Players will hedge their gear production against expected threat level, developing a personal read on "how much military is enough."
• Players will specialize districts and develop layout signatures — a personal style of settlement that they recognize as theirs.
• Players will form attachments to individual settlers who survive multiple raids wearing gear the player personally decided to forge.
• Players will push into dangerous terrain deliberately once they feel armed, converting military surplus into economic opportunity.
• Players will narrate their failures ("I under-armed autumn and lost the east field") because failure traces to a specific, legible decision.

Core Mechanics (Systems we build)

• Production chains — multi-step material transformation (wood → charcoal → smelting → smithing) where intermediate goods are visible and stockpiled.
• The dual-purpose output system — every smith output is categorized as economic (ploughs, tools, nails) or military (spears, mail, shields), drawing from the same input pool. This is the central tension mechanic.
• The muster — an alarm state that converts assigned workers into armed defenders based on available gear in the armory. Pulls them off work temporarily; the real cost was paid at the forge.
• Telegraphed directional threat — escalating, visible, readable danger that approaches from specific map directions on a known cadence.
• Seasonal cycle — a four-season rhythm that structures production capacity, threat timing, and the natural session boundary.

Player Motivation Profile

Primary Psychological Needs Served

Player Type Appeal (Bartle Taxonomy)

• [x] Achievers (goal completion, collection, progression) — How: completing production chains, filling the armory, securing the valley. Progression is in options unlocked, not raw power numbers.
• [x] Explorers (discovery, understanding systems, finding secrets) — How: understanding the economy's interlocking depth and the threat escalation model. Later tiers add literal frontier exploration.
• [ ] Socializers (relationships, cooperation, community) — Not served. Single-player with no social systems.
• [ ] Killers/Competitors (domination, PvP, leaderboards) — Not served, and deliberately so. Combat is light-touch; competitive players will bounce.

Quantic Foundry mapping: primary appeal is Design + Completion (the builder motivation cluster), secondary is Strategy + Challenge.

Flow State Design

• Onboarding curve: The first 10 minutes are pure builder — place a cabin, a woodcutter, a field. No threat appears until the player has a functioning micro-economy, so the economic layer is understood before it's stressed.
• Difficulty scaling: Threat escalates on a visible, telegraphed schedule tied to seasons and to the player's own expansion. Pushing into dangerous terrain is the player's choice to raise difficulty.
• Feedback clarity: The armory is the master readout. A player can see at a glance whether they are prepared. Production chains show work-in-progress visibly so the player understands cause and effect.
• Recovery from failure: Losing a raid costs resources, structures, and sometimes settlers — never the ability to keep building. The settlement is never wiped; the player rebuilds from a diminished but viable state.

Core Loop

Moment-to-Moment (30 seconds)

Provisioning. Assigning labor, routing materials, placing buildings. The core act is deciding what a resource becomes: this iron becomes ploughshares or spearheads; this leather becomes work boots or a jerkin. Each micro-decision is a small bet on how dangerous the coming season will be.

Intrinsically satisfying because it is legible — the player sees the stockpile move, sees the smith begin work, sees finished gear rack up in the armory.

Short-Term (5-15 minutes)

A production chain completes. The charcoal kiln finally feeds the smelter, which feeds the blacksmith, and a finished spear appears on the armory rack. This is the "one more building" hook: the player always wants to close one more loop. Because the armory is simultaneously an economic output and a defensive readout, watching it fill delivers two satisfactions at once.

Session-Level (30-120 minutes)

One seasonal cycle. Spring build-out → summer expansion into dangerous terrain → autumn raid and muster → winter scarcity, repair, and planning. Each season boundary is a natural stopping point. The session ends with the player knowing the state of their armory and the shape of next year's threat.

Long-Term Progression

Frontier establishment. Growth is in options, not raw power. Early game: one settlement doing everything badly, everyone doing double duty. Late game: specialized production districts, a standing guard that frees workers from militia duty, outposts claiming the iron valley. The game is "done" when the frontier is secure enough that raids are an annoyance — and then the player pushes further out and makes it dangerous again.

Retention Hooks

• Curiosity: What's in the unmapped valleys? How does the threat escalate next year?
• Investment: The settlement the player designed, and the named settlers who have survived in it.
• Social: Not applicable (single-player).
• Mastery: The gear-vs-tools allocation curve has real depth. Reading the frontier correctly is a skill that visibly improves.

The hook that follows the player off the couch: *I know my armory is thin and autumn is coming.*

Game Pillars

Pillar 1: The Economy Is the Army

Every unit of military capability traces back to a production decision. There is no "recruit soldier" button; there is iron, a smith, and a person who stops being a farmer.

Design test: If we're debating whether a military feature should cost economic resources or be purchased directly — it costs economic resources, always.

Pillar 2: The Settlement Is a Creative Act

The town is the player's expression. Layout, specialization, and aesthetics matter, and the game should never punish a player for building something beautiful over something optimal.

Design test: If we're debating between a system that adds depth and one that adds constraint on layout freedom — we choose depth, and leave the layout to the player.

Pillar 3: The Wilderness Has Intent

Unlike Banished's indifferent nature, this world contains things that want your stuff. Threat is directional, escalating, and readable — the player should always be able to see danger coming and prepare for it.

Design test: If we're debating between a random punishing event and a telegraphed escalating threat — always telegraphed. Surprise is not the same as difficulty.

Productive Tensions Between Pillars

These pillars are designed to pull against each other. Pillar 2 says don't constrain layout; Pillar 3 says threat comes from a direction, which naturally pressures layout. Pillar 1 says everything costs economy; Pillar 2 says don't punish the builder. The interesting design decisions live in these frictions — and the resolution is consistently: **the cost is paid at the forge, weeks earlier, not at the moment of crisis.**

Anti-Pillars (What This Game Is NOT)

• NOT a tactical combat game: Combat is light-touch command resolved in minutes. Deep tactical systems would compete with the economy for both development time and player attention, compromising Pillar 2.
• NOT a game where the muster punishes the builder: Calling the militia is never a decision the player regrets on economic grounds. The cost was paid earlier in the workshop. This protects Pillar 2.
• NOT a game that uses randomized disaster events as difficulty: No surprise plagues, no unannounced raids from nowhere. Every threat telegraphs. This protects Pillar 3.
• NOT a game that gates creative building behind combat performance: Losing a fight costs resources and people, never the ability to keep building the town the player wants. This protects Pillar 2.

Visual Identity Anchor

*This section is the seed of the art bible. It captures the visual decisions made during concept development before they can be forgotten between sessions.*

Direction: Weathered Almanac

A hand-drawn, slightly illustrative medieval look — woodcut prints and farmers' almanac illustrations rather than gritty realism. Chosen for readability at a city-builder's zoomed-out camera distance, which is the practical constraint that matters most for this genre.

One-line visual rule: Everything shows its season and its wear.

Supporting Visual Principles

1. Seasonal colour is the primary information channel. The palette shifts wholesale across the year — spring greens, summer gold, autumn rust and mud, winter blue-white. The player should be able to identify the season from a single frame with the UI hidden.

Design test: If a visual choice would make two seasons look similar, we change it.

2. Wear tells the story. Buildings, gear, and people visibly degrade and get repaired. A three-raid veteran's chainmail looks different from fresh-forged. Palisades show where the ram struck.

Design test: If we can show state through wear instead of a UI icon, we use wear.

Colour Philosophy

A muted, earthy base palette so that the two things that matter most read instantly:

• Iron grey — military capability, gear, weapons, armor
• Warm gold — food, prosperity, economic health

Threat is signalled by desaturation and cold tones creeping inward from the map edges, reinforcing Pillar 3's commitment to telegraphed, directional danger.

Inspiration and References

Non-game inspirations: Medieval farmers' almanacs and woodcut illustration (visual direction); the historical reality of frontier settlements where militia duty and agricultural labor were the same people's work (core fantasy); the logistics of pre-industrial ironworking, where charcoal production and iron smelting were inseparable economic activities.

Target Player Profile

Technical Considerations

Risks and Open Questions

Design Risks

• The muster may not feel meaningful with the cost displaced to gear. This is the central design bet. If players don't feel the weight of the forge decision weeks later when the horn sounds, the hook fails. Mitigated by making the armory a prominent, legible readout — but only the MVP can actually answer this.
• Combat may feel like a spreadsheet check rather than a battle. Light-touch combat risks being so abstract that the payoff moment lacks drama.
• The economy may not be deep enough to satisfy Ostriv/Banished players within MVP scope, making the MVP a poor test of the real game.
• The Manor Lords coupling trap. Manor Lords did couple economy and military — militia drafted from the worker pool, gear from production, food upkeep — and its combat was still called "stapled on" and "an afterthought", because the coupling is a resource-cost gate in front of a separate RTS minigame. Players' standard advice is to disband militia quickly because idle troops are a chore. It kept a ~90% Steam rating partly because a no-combat mode ("Rise to Prosperity") lets the builder audience opt out entirely. Iron & Timber has no such escape hatch by design, so the muster must be the economy acting — not a purchase made from it — and the defence layer must carry its own weight. (Market research, 2026-09-12.)
• The Bellwright competence trap. Bellwright shipped almost this premise — gear up your people, let them fight — and it collapsed in play: a 230-hour reviewer reported that geared NPC companions were too incompetent to trust, so the player "became John Rambo" and soloed every fight, leaving building and combat "existing separately rather than synergistically". If armed settlers are not visibly capable, players route around the whole idea. This is promoted to an MVP acceptance criterion below. (Market research, 2026-09-12.)

Technical Risks

• Settler simulation performance at scale. 100+ agents with individual job assignment, pathfinding, and gear state is a known-hard problem. Unity's DOTS is available as a mitigation but adds architectural complexity.
• Seasonal visual transitions without quadrupling the art budget. Needs a shader-based approach proven early.

Market Risks

• Genre crowding. Manor Lords, Going Medieval, and Bellwright all occupy adjacent space. Differentiation rests entirely on the economy-is-the-army hook being legible in marketing.
• **The audience that wants deep economy and the audience that wants combat may be less overlapping than assumed.** Manor Lords' combat criticism suggests the builder audience is protective of the builder.

Scope Risks

• The full vision is 24-36 months solo against a stated timeline of weeks. This is managed by explicit scope tiering (below), but the risk is that the MVP is too thin to be a valid test of a game whose appeal depends on depth.
• Combat scope creep. Light-touch combat has enormous gravitational pull toward becoming tactical. Anti-pillar 1 exists specifically to resist this and must be enforced at every story-level decision.

Open Questions

• Does the displaced-cost muster actually feel weighty? Answered by the MVP — this is its entire purpose.
• What is the right ratio of economic to military smith output for the tension to be interesting rather than obvious? Answered by MVP tuning.
• How abstract can combat be before the payoff moment loses its drama? Answered by prototyping two resolution models against each other.
• Can seasonal palette shifts be achieved via shader tinting on a single asset set? Answered by a technical spike before art production begins.

MVP Definition

Core hypothesis: *Players feel the weight of choosing spears over ploughs — the displaced cost of military readiness makes the muster moment meaningful without punishing the builder.*

Required for MVP:

• One production chain, end to end: wood → charcoal → iron ore → smelter → blacksmith → finished goods. The chain must have enough steps that allocation decisions compound.
• The dual output: the blacksmith produces either economic goods (ploughs) or military goods (spears) from the same inputs, with a visible armory readout.
• The muster: an alarm state that arms available settlers from the armory and positions them for defense, with light tactical control (who musters, where they stand, when to ring the bell).
• One telegraphed raid from one direction, on a visible timer, with escalating strength.
• One season cycle providing the production and threat rhythm.
• Settler competence criterion: armed settlers must win a raid they are adequately geared for without the player micromanaging or bypassing them. In playtests, if a player's instinct is to route around their own militia rather than through it, the MVP fails this criterion regardless of how the other five feel (see the Bellwright risk above).

Approximately 8 building types, ~15 settlers, one hand-authored valley.

Explicitly NOT in MVP (defer to later):

• Weather and mud physics
• Food preservation and spoilage systems
• Animal taming and breeding
• Outbound raiding and expeditions
• Base destruction (rams, ladders, siege)
• Faith, ale, clothing, and complex needs
• Rival settlements and diplomacy
• Multiple biomes or procedural map generation
• Gear tiers beyond a single military and single economic output
• Named settler persistence and scar/wear tracking

Scope Tiers (if budget/time shrinks)

Next Steps

• [ ] Get concept approval from creative-director
• [ ] Fill in CLAUDE.md technology stack based on engine choice (/setup-engine) — repin from Godot 4.6 to Unity
• [ ] Create game pillars document (/design-review to validate)
• [ ] Prototype core idea (/prototype muster-mechanic) — before writing GDDs, validate the displaced-cost muster is worth designing
• [ ] If prototype PROCEEDS: /art-bible to formalize the Weathered Almanac direction
• [ ] Decompose concept into systems (/map-systems)
• [ ] Design each system (/design-system [system-name]) — use prototype learnings in Tuning Knobs and Formulas sections
• [ ] Build vertical slice in Pre-Production (/vertical-slice) — validate full game loop before committing to Production
• [ ] Validate core loop with playtest (/playtest-report)
• [ ] Plan first milestone (/sprint-plan new)