Chapter 7
Tests, counters and routines
Hide, Fortitude and Sailing tests, the counters they use, and calling a routine from a card.
Routines
A test is not written into every card that asks for it. It is a routine, a list of items kept once under a name starting with @, which a card runs with a call item:
- @Hide test (the Black Riders saga): commit characters, discard X cards without revealing them, and hide if your willpower is at least their threat.
- @Fortitude test (Mount Doom): commit heroes, discard as many cards as the tens digit of your threat, and pass if your willpower is greater than their Eye of Sauron icons.
- @Sailing test (the Dream-chaser): the heading shifts off-course, commit characters and ships, look at that many cards and name their sailing symbols, which bring it back on-course.
The call can pass numbers in (Hide X, extra Eye icons), and the cards of a test go to a hidden test zone, so nothing sees them move.
Counters
A counter is a named number of the game: set it or add to it (never below 0, and never above its most, if it has one), from a fixed amount, the number you named, how many cards were found, the tokens of a kind on the card itself (tokens:resource), or the willpower or threat of the cards in a test. It can expire at the end of the phase or the round. A counter named like a tracker on the bar (Pursuit, Heading) is that tracker. Read one in a text as {var:name}, and test it in Only when.
Modifiers of a test
A card that changes a test ("add 1 to the Hide value", "add an Eye of Sauron icon to each Fortitude test") has a rule with a modifier of the test's key (hide.x, hide.threat, fortitude.icons ...) while it is in the right state; the routine adds them up when it runs.
After a test
A routine emits an event when it is done (hide-passed, hide-failed, fortitude-passed, fortitude-failed, sailing-test), so other cards can react to it, and leaves its result in counters (hide.result, fortitude.failed.round) for the items after the call.