Skip to content

Knight Strategy — Choosing Your Guard

Last updated

The Knight's rules (no consecutive guards, skipping the guard, saves being invisible) are collected in the role dictionary: Knight. This column is about choosing a guard inside those constraints.

The default guard: the Seer — but "when" comes with it

The first candidate is a claimed Seer — the one seat that adds information every night. No dilemma so far.

The hard part comes next. You can guard the same player only every other night (no consecutive guards). Say the Seer claims on day one and you guard them that night — the following night, the Seer stands unguarded. The wolves know it too. ∴ A guard choice is never just "who" — it is always "who, and on which night".

∴ Nights you can't cover are unavoidable. The craft is steering the day's discussion so the wolves prefer a different bite on exactly those nights. And on a night that feels "safe enough", skipping the guard on purpose buys back tomorrow's options (Skipping the guard).

Never declare a save

Villages love to conclude "the Knight connected". But a morning where nobody died has more than one cause (see the role dictionary) — with two wolves, split bite choices are simply normal.

The same applies to you. Whether your guard connected or the wolves split is something you cannot distinguish. Declare "that was my save" and you may be fixing a wrong read into the village's shared memory.

Should the Knight claim?

A claimed Knight lets the wolves predict who's covered. And a claimed Knight gets bitten — you cannot guard yourself.

In general, stay silent until the endgame. The claim is worth it only when silence costs the village — typically when you're about to be voted out.

Common mistakes

  • Trying to guard the Seer every single night — physically impossible under no-consecutive-guards. Deciding where to place the uncovered night is the actual job.
  • Declaring "nobody died = my guard connected" — indistinguishable (above), and if wrong, it locks the village onto a false premise.
  • Hesitating to skip on a calm night — the skipped guard isn't slacking; it's an investment that buys the next night's choice.

A scene

A 7-player room (the beginner deck): the day-one vote executed one of the Twins. Twins follow each other in death, so the village lost two at once — five players left.

Remaining: three village (Delegator, Knight, Seer) against two wolves. One more village death and the wolves reach parity — wolves win. In other words, no night may produce a death anymore.

Night one: you guarded the Seer. Morning: nobody died — though whether that was your save or a Failed attack from split wolves, you cannot tell.

Day two: the runoff vote tied as well, so that day's execution was skipped (still five alive).

Night two: you guarded the Seer last night, so the Seer can't be chosen. After agonizing, you guarded the Delegator — and the wolves bit the Seer. Two village, two wolves. Game over.

Had you skipped the guard on night one, the Seer would have been coverable tonight.

Related

Back to top page