Random Emergency Quests and Reserve Planning

You know the scene: a flood warning reaches the Round Table while every useful knight is three days into a grand expedition. The court has prepared for everything except the next thing. The answer is not one perfect reserve knight, Your Grace. Keep a small, mixed bench that can cover several statistics, then use the rest of the roster for story quests and stranger pairings.

A cycle is the game’s version of a day. You hear petitions, manage the tower, assign knights at the Round Table, and select the next cycle. A quest’s deadline is the time left to send a party. Its duration is how long that party remains unavailable. A two- or three-cycle assignment can therefore leave a fine-looking roster with nobody home when an urgent quest appears.

What Can Trigger, and When?

Emergency pattern	Observed trigger range and run variation	Deadline and consequence
Random regional disaster	These can appear during an active act without a repeatable numbered cycle. The crisis and its arrival point can change after different choices or a rewritten timeline.	Read the timer as soon as the quest appears. The flood example gives one cycle to respond and threatens to destroy the village if no suitable party is sent.
Faction- or treasury-linked crisis	Some urgent events are tied to the current satisfaction or treasury state. Different decrees and quest results can move the kingdom into that danger state earlier, later, or not at all.	Use the deadline shown on that event; there is no single timer shared by every crisis. Many failures allow the reign to continue, but the damaged faction, resource, location, or story state may change later options.
Availability squeeze	This can happen on any cycle. Two-cycle assignments appear early, and three-day absences can overlap a one-cycle emergency.	There is no separate warning timer. The consequence is simple and rude: committed knights cannot answer the new quest, forcing a weaker party, an accepted failure, or a rewind.

Do not build a calendar around one flood appearing on the same cycle twice. Build around the interruption itself. Before selecting the next cycle, assume that the throne may receive one urgent problem and that the kingdom will choose the least convenient possible moment.

Build a Reserve Bench, Not a Reserve Mascot

For early and middle play, try to leave two healthy knights unassigned. This is a planning target, not a guaranteed solution. One should lean toward Strength and Agility; the other should lean toward Magic and Wits. Spread Charisma and Luck across the pair so one weak statistic does not sink every emergency option. When the roster grows, keep a third knight free before a major deadline or while faction and treasury meters look fragile.

Traits: Reveal traits before treating a knight as a reserve specialist. Favor a mixed bench with useful traits for aid, diplomacy, animals, travel, or strange hazards, but always compare those traits with the highlighted quest clues. A matching trait can alter an outcome; it does not erase a bad statistic or an undersized party.
Equipment: Keep flexible stat gear available for the party you are about to send. The Hunting Bow, for example, adds 1 Wits and 1 Agility and can patch a small gap. Do not assume one item can rescue a party that misses several requirements.
Armor: Repair likely responders before buying a luxury upgrade. Quests can damage armor, and an unsuitable or poorly equipped knight can die on assignment. A healthy reserve with bare statistics is safer than a brilliant knight held together by heraldic optimism.
Party capacity: Party size, statistics, and attributes all affect the result. Keep at least two seats available when possible, and preserve a third before dangerous story deadlines. If an urgent quest asks for more than your reserve can supply, compare the likely failure with the value of every ongoing assignment.

End-of-Cycle Reserve Checklist

Read every active deadline before starting an optional quest.
Check which knights will remain away for two or more cycles.
Keep one physical responder and one Magic/Wits responder healthy.
Check every faction meter and the Treasury; do not rely on a fixed number of crisis-safe points.
Save enough gold to repair the responders you are most likely to use.
Take note of the current cycle, assignments, armor, and route goal before advancing. That small timeline log is worth more than another ceremonial rug.

Cancel the Plan, Accept Less, or Rewind?

Choice	Use it when
Reshuffle the plan	You are still at the Round Table and have not selected the next cycle. Unassign knights from optional work and cover the urgent quest first when its failure would ruin a location or route you still need.
Accept a weaker result	Your available party can cover the requested size and most important statistics but is unlikely to earn the best result. Preserving the location or faction state can be worth more than chasing a perfect optional outcome.
Let the crisis fail	The reign can continue and the loss does not remove the alliance, recruit, romance, or ending you want. This is a route tradeoff, not automatically poor play.
Rewind	The only suitable knights were committed several cycles earlier, the result kills a route-critical knight, or the failure removes the main reason for this timeline. Return to before the long assignments, preserve the needed coverage, and remember that rewriting events can also erase later allies, artifacts, and opportunities.

Recovery After the Court Explodes

Death: Replace the lost knight’s role, not just their empty chair. Check which statistics and traits vanished from the bench. Continue if another recruit or equipment setup can cover them; rewind if the character is essential to your intended route.
Resignation: Low knight satisfaction can make a knight leave the court. Before that happens, use liked assignments and available relationship scenes to improve affinity. After departure, rebuild their stat role and stop planning future parties around a portrait that is no longer attending meetings.
Depleted armor: Use the forge to repair the smallest group that restores both physical and magical coverage. Bench the rest until the treasury recovers.
Thin treasury: Delay annexes and optional purchases, repair the most flexible responders first, and favor short quests with clear gold rewards. A modest success is useful; a funeral with excellent projected returns is not.
Damaged location or faction state: Check the Map Room for an available repair action after a quest failure. Then review the route. Continue if the damage is survivable and interesting; rewind if it removes a required alliance, recruit, artifact, or ending condition.

Reserve planning does not make Sovereign Tower safe. It makes the chaos playable. Keep enough talent at home to answer the common crisis shapes, accept that some timelines will still catch fire, and turn each failure into better scheduling for the next reign.

← Prev Next →