I just bought the game and downloaded the pdf to read while I wait. I have played blades and band of blades for reference. I don’t really understand how the battle clocks work. Do I make the clocks, tick them down when we take actions and then once it’s completed the battle is over? Is it competing clocks? And what is the difference in the field, foe and fallout clocks? In short I just don’t understand narratively how’s they work and what they result in.
Hey, good question.
You begin the battle by making two clocks that the players will fill with successful actions: the field clock (representing routing the enemy forces) and the foe clock (representing eliminating the enemey commanders). When (and if) these clocks are full, the players win the battle. You could totally make a racing clock to track when the player retinue's forces are routed and tick that when the players' forces are routed. We aren't too prescriptive on how you frame the consequences for these rolls.
The fallout clock comes out after the battle is resolved, representing the aftermath of battle: "wraiths emerging, fires spreading, and structures collapsing". The players can resolve these, and potentially face consequences, or they can ride home. Choosing to not manage the fallout is likely to mean that the players will face more severe unrest and entanglements after this fight.
All that said, battles tend to be a rare thing. Most playtest groups only ran a few battles over the whole campaign. Most smaller skirmishes can be resolved in a single roll or pair of racing clocks. These rules are designed to give more detail and time to epic conflicts.
Hi, came here to ask a similar question. (Great game btw, I rarely sit down and read an RPG book from beginning to end before my intent to run it).
I would really love a better example of the battle sequence, in part because the language in the book implies all clocks need filling but don't showcase how a battle would be waged or which actions would affect said clocks. Also while the raising of levies and their quality would be an important part of the narrative, I am uncertain how to deploy these resources in play mechanically. I feel battles, however rare, would be quite pivotal and essential to the story, and a play-by-play example would really bolster my confidence in running these scenarios.
Keep doing what you're doing!
I don't have a recording of any full battles that I can share, but I wrote up an example.
Hopefully this helps folks interested in battles who want a sense of how they might flow. Keep in mind that this is just one way it could go. players might resolve the foe clock before the field clock, or they could even lose the fight and resolve either.
This has been both incredibly informative and fun to read!
Last followups.
1. So the clocks move in sequence, not at the same time - correct?
2. With the field clock full, Ailios describes him riding up to Luthais Gearr and demanding his surrender. Luthais refuses but offers to end the battle in single combat. The retinue is conflicted about how to proceed.
I wondered about this one when reading the book. If the NPC surrenders does the clock fill automatically and in the inverse - if their army is shattered but refuse surrender, what is the clock supposed to represent?
3. Is dealing with the fallout always about wraiths and perhaps collateral damage like fire etc? (I hadn't imagined the wraiths would appear so instantly until reading this, really does put more weight on the dangers of killing/murder). The book suggests the clock MUST be filled for the battle to be over, but earlier in this thread you said they can choose to ignore it (with consequence). Would that just be a mitigating of more fallout (in terms of Ire and Faction relationships)?
Thank you for taking the time, you should post that link on the KS section as well!
- The clocks don't move in sequence. You might infiltrate the enemy command tent and resolve the foe clock first, or cut back between field and foe. Resolving one of the clocks first can effect your positioning on the other. The enemy commander might be more inclined to surrender after their forces have been routed. The enemy line might be less organized if their commander has been killed or captured. The exception to this non-linearity is the fallout clock. You might add sections based on the course of the battle, so I generally resolve this last (though I bet an artful GM could start at the fallout and flash back to the battle that led to that moment).
- I use the clock as a pacing cue. Does Luthais surrender when his line breaks? Well the foe clock is not full so probably not, though the broken line will put the retinue in a good position to make demands (and roll to see if they are met). From the Blades SRD: "Remember that a clock tracks progress. It reflects the fictional situation, so the group can gauge how they’re doing. A clock is like a speedometer in a car. It shows the speed of the vehicle—it doesn’t determine the speed."
- Wraiths and collateral damage are the most likely fallout. You could also focus on treating the wounded and rallying the broken spirit of your levies. "Do you have to fill all the clocks?" is an interesting questions. For "victory", yes. Filling all clocks means you broke the enemy line, destroyed their command, and dealt with the fallout of the battle. You can march home victorious. However, you could just kill the enemy commander and run. That's not winning the battle, but it might accomplish your strategic goals. Similarly, if you are there to pillage a holding, you might not care about the fallout clock; let the city burn and wraiths roam. In these instances, the clocks can help everyone get on the same page as to how the battle ended and the likely consequences.