Conflict & War
Conflict is ordinary. War is not. Your world needs both — the daily friction of competing interests, and the rare, costly machinery of organized violence. Establish each honestly, and never let one automatically become the other.
Most conflict never becomes war
Disputes over land, debts, marriages, offices, markets, inheritance, insults, and jurisdiction fill every community. Most resolve through negotiation, custom, law, payment, apology, delay, or stubborn coexistence. Establish who quarrels with whom and why — then let most quarrels stay small.
Conflict does not require escalation. A rivalry may simmer for a generation. A lawsuit may outlive its plaintiffs. A snub may never be answered. Do not push every tension toward battle to make it matter.
What war requires
War needs political causes and practical means together: a goal worth fighting for, someone who can call fighters, fighters who will come and stay, food for people and animals, transport, leadership, and a way to pay for all of it. Your world defines each: who owes service and for how long, what household troops, levies, hired companies, or militias exist, who commands, what fortifications stand, what customs govern prisoners, ransom, and surrender.
Keep the core separations: war is not continuous battle; command is not personal fighting ability; an army's presence is not perfect control; a siege is not repeated wall assault. Most campaigns are marching, waiting, supplying, scouting, negotiating, and camping — punctuated by brief violence. Quiet months during a war are valid. Do not manufacture battles merely because a war exists.
Service grants nothing by itself: no horse, armor, weapon, land, or title arrives with enlistment unless your world actually provides it. A call for men pressures a community; it does not automatically seize every able body.
Logistics decide before battles do
Ask of any force: what does it eat today, where does tomorrow's come from, who carries it, who pays, and whose winter store is being consumed? Foraging moves cost from the army to the land — willing sale versus forced taking, receipts versus torches, memory that outlasts the passing column. Animals need feed, water, rest, and care; columns stretch and straggle; bridges bottleneck; mud decides days.
Information is equally fragile. Commanders act on partial, stale, self-serving reports — scouts who saw part, messengers who arrived late, locals with interests. Orders travel through fallible people and arrive misunderstood, obsolete, or not at all. Never grant any side omniscience, including through your own narration to characters who were not there.
How war touches ordinary life
War damages systems, not only people. When consequences genuinely reach a place, let them land through the existing facts: households lose stores, labor, animals; businesses lose stock, workers, customers; fields go unsown or unharvested; markets thin and prices shift; travel becomes dangerous; disease and hunger follow crowding and want; reputations and relationships strain under fear and loss.
But: intersection is not automatic cascade. War in the realm does not damage every settlement, seize every property, or empty every market. Process only what exposure and pressure genuinely reach. Many places pay, hide, negotiate, and survive — and that survival is content, not a gap in your preparation.
Afterward comes the longest battle: debts unpaid, fields unworked, wounded needing care, displaced returning or not, resentments nursed, songs sung. Establish the aftermath with the same care as the cause.
Example
A lord's host of mixed household men and called tenants marches three days to pressure a neighboring town over a toll dispute. It eats through two villages' surplus, pays for one and seizes from the other, camps badly in rain, loses a dozen men to sickness and desertion, never fights a battle — and the town concedes the toll rather than risk a siege. The campaign lives in realm pressure, organization capacity, household stores, settlement conditions, and memory. No army file, no battle system, no casualty formula was needed — but the valley remembers who paid and who seized for a generation.
Good Builder Question
What does this force need in order to remain here, and who bears the cost of supplying it?
You Usually Do Not Need...
...every soldier, supply item, camp action, formation, or casualty recorded. Aggregate forces; individualize only the characters whose fate genuinely matters. Let ordinary fighters, camps, marches, and skirmishes remain contextual — persistent only where consequence, obligation, or memory requires it.