Ruling — Nemesis: Retaliation

← Nemesis: Retaliation

You asked

How do I play?

Answered counted as answered

Asked with: Nemesis: Retaliationbg-381248-en-1e

Beginning of the Game

1. Each player draws 5 Action cards to their hand from their Action deck.[1]

2. Player 1 receives the Starting Player token.[1]

3. The game begins with the Starting Player.[1]

Character Setup

1. Each player takes 1 Character board and places it in front of them, then places the Character tile matching their chosen Character on the board.[2]

2. Each player takes 1 Universal marker and places it in the left-most slot of the Health track on the bottom of the Character board.[2]

3. Each player sets their Oxygen counter to the max value of 7.[2]

4. Each player takes their chosen Character’s miniature, places it in the colored ring matching their Character’s color, and places the miniature in the Landing Zone.[2]

5. Each player takes the Backpack card holder with their player number and places it above their Character board.[2]

6. Each player takes all Action cards for their Character, shuffles them, and places them to the left of their Character board, face down.[2]

Players' Turns

During a turn, a player must resolve the following three steps in order:

1. Perform 2 Actions.[3]

- Players may choose from the list on the Character board.[3]

- Players may perform the same Action multiple times in any given Turn.[3]

- If unable to perform any other Action, the player must perform the “Pass” Action.[3]

- Once per game, a player may also choose an Objective during their Turn, which does not count as an Action.[3]

2. Oxygen Loss.[3]

3. Fire Damage.[3]

Note on Passing: When a player Passes, they may discard any number of cards from their hand (Action cards and Contamination cards), and then their Turn ends.[4] From that point on, their Turns are skipped for the rest of the current Round.[4]

Note on Actions:

- Play an Action card: The player reveals the chosen Action card from their hand, resolves its effect, and then places it on top of the discard pile.[4]

- Make a Move: The player discards a card from their hand to pay the Action’s cost, then:

1. Chooses a Direction (upper, middle, or lower Corridor).[5]

2. Resolves Opportunity Attacks (skips this step if there are no Intruders in the chosen Corridor or the Room being left).[5]

3. Sees the Impact of Movement (if moving to an Unexplored Room, the player performs the Exploration Sequence).[5]

- Exploration Sequence: The player draws the top card from the Exploration deck and resolves its effect from top to bottom:[5]

- Set up the Room: The player draws a random Room corresponding to the Section they are Moving to and adds it to the map, connecting it with the Corridor they are Moving through.[5] (Note: If the card specifies a type like "A", "B", "C", or "?", the player draws a random Room of that type, using "?" if no others are available [6]).

- Set up the Corridors: The player places Corridors as indicated on the card.[5] If a Corridor has a Door slot, it is placed so the slot connects with the newly Explored Room.[6] Corridors are not placed if they lead to an already existing Room [5] or if they lead outside the Facility's border.[6]

- Set up markers and tokens: The player places a Fire marker in the new Room.[5]

[1] RULEBOOK Nemesis: Retaliation — Rulebook · p.10

[2] RULEBOOK Nemesis: Retaliation — Rulebook · p.10

[3] RULEBOOK Nemesis: Retaliation — Rulebook · p.12

[4] RULEBOOK Nemesis: Retaliation — Rulebook · p.13

[5] RULEBOOK Nemesis: Retaliation — Rulebook · p.26

[6] RULEBOOK Nemesis: Retaliation — Rulebook · p.24

That's the page. Back to the table.

🔧 debug — where this ruling came from

outcome: ANSWERED — Answered
corpus profile: live,vps
answerer pin (deploy-frozen, attribution only): gemma4:26b think:false 5571076f3d70
timings: search 89 ms · ask 12152 ms · total 26240 ms
single-flight (PR-5): queued 13997 ms · generation 12243 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read: [{"page": 10, "score": 0.047123, "snippet": "Put the/uni00A0rest back in the/uni00A0box. 3. Shufﬂe all Character draft cards . Deal 2 of those cards to Player/uni00A0 1/uni00A0 – they should remain secret for/uni00A0 other play- ers. That/uni00A0player chooses one of those cards (a Character to play as) and reveals it. The/uni00A0other card is", "headingPath": "", "sharpsignalDocId": 378}, {"page": 12, "score": 0.046032, "snippet": "12 players' turns During their Turn a player must resolve the/uni00A03 following steps in order: 1. Perform 2 Actions 2. Oxygen Loss 3. Fire Damage Players may also, once per game, choose an/uni00A0Objective during their Turn/uni00A0– this does not count as an/uni00A0Action. More about Choosing an O", "headingPath": "", "sharpsignalDocId": 378}, {"page": 12, "score": 0.045475, "snippet": "To perform an/uni00A0Action, the/uni00A0player pays a cost listed above by discard- ing an/uni00A0appropriate number of Action cards from hand to their discard pile, face up. Then, they resolve the/uni00A0chosen Action. Note that in Nemesis Pass is an Action. A player does not Pass automatically whe", "headingPath": "", "sharpsignalDocId": 378}, {"page": 10, "score": 0.044796, "snippet": "10 player setup objective setup and character draft To setup the/uni00A0players, perform the/uni00A0following: 1. Find Help cards with numbers corresponding to/uni00A0the/uni00A0number of players taking part in the/uni00A0game (e.g./uni00A0if there are 3 players in the/uni00A0game, ﬁnd cards “1”, “2", "headingPath": "", "sharpsignalDocId": 378}, {"page": 10, "score": 0.032787, "snippet": "This choice can be done simultaneously, but if necessary perform it in de- scending player number order. Note: For/uni00A0the/uni00A0ﬁrst game we recommend starting with 1 to- ken of each type. beginning of the game 1. Each player draws 5 Action cards to/uni00A0 their hand from their Action deck. 2.", "headingPath": "", "sharpsignalDocId": 378}, {"page": 26, "score": 0.032258, "snippet": "The player performs a “Make a Move” Action. They discard a card from their hand to pay the Action’s cost. Then, they: 1. Choose Direction /uni00A0– They choose the upper Corridor to move through (they could also choose the middle or the lower one). 2. Resolve Opportunity Attacks /uni00A0– Since ther", "headingPath": "", "sharpsignalDocId": 378}, {"page": 13, "score": 0.029851, "snippet": "Reactions are not Actions and/uni00A0do not count toward/uni00A0the/uni00A0Actions per Turn limit. choosing an objective During their Turns, players may also choose their Objective. Each player may only choose an/uni00A0Objective once per game, while they still have 2 Objective cards. An/uni00A0Obje", "headingPath": "", "sharpsignalDocId": 378}, {"page": 12, "score": 0.029644, "snippet": "TURN ORDER AS TIEBREAKER Turn order is the/uni00A0most common way to/uni00A0break ties in Nemesis . The Rulebook may call out the/uni00A0Character ﬁrst in Turn order. In any such case it describes the Starting player (the player that currently holds the Starting Player token) or is closest to/uni00A", "headingPath": "", "sharpsignalDocId": 378}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show: [{"page": 10, "quote": null, "headingPath": "", "sharpsignalDocId": 378}, {"page": 10, "quote": null, "headingPath": "", "sharpsignalDocId": 378}, {"page": 12, "quote": null, "headingPath": "", "sharpsignalDocId": 378}, {"page": 13, "quote": null, "headingPath": "", "sharpsignalDocId": 378}, {"page": 26, "quote": null, "headingPath": "", "sharpsignalDocId": 378}, {"page": 24, "quote": null, "headingPath": "", "sharpsignalDocId": 378}]
boost provenance — errata + base rulebook (E2/E3): no registered errata card matched this query; base rulebook doc 378 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 378 boosted
answered-before recall: this ruling was answered, so past rulings were not offered
similarity threshold in force: 0.55 (rulesage.answered-before.similarity-threshold; the exact-question tier is not gated by it)
answer fence: passed — letter density 0.90011 of 2613 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row recorded: Aug 25, 2026 17:01 UTC

retrieval — what the passage search returned

what this block IS: the PASSAGE SEARCH's own results — the same search that fills this page's closest-passages list — and NOT the passages the answerer read. Answering runs its OWN retrieval: a far wider candidate pool, re-ranked down to a final handful, plus floors this search never applies — the base rulebook, surviving errata corrections, and one slot per book on a multi-book read. Each of those armed only if THIS ask sent what it needs: the boost block names the ids it forwarded, and the scope line names the books it read. A document the answer CITES that no row here names is therefore EXPECTED, not a defect: two searches, two candidate pools, two orders. The answerer's own final rows are shown in their own block below, beside these and never mixed into them.

score = the fused retrieval score (reciprocal-rank fusion over the search arms) — NOT a cosine similarity. This ruling ran the THREE-ARM fuse (full-text + vector + the doc-priority boost arm, which carried the base rulebook and/or the errata corrections this query matched), whose arithmetic ceiling is 0.04918 — all three arms ranking the same chunk #1 (ceiling = arms/(k+1) at k=60). The measured healthy band 0.016–0.033 was measured on TWO-arm asks and does not bound this one: its high end is the two-arm ceiling, and a third arm has room above it. A chunk only one arm ranked highly lands near 0.016 (that one arm's #1 vote), so 0.03 here is an excellent hit, not a 3% match.

per-arm ranks (the rank each search arm gave a chunk): NOT DISCLOSED by the gateway. Fusion happens gateway-side and only the FUSED score crosses the wire, so rulesage cannot show them without a gateway change. The rank column below is the FUSED rank (position in the returned list), which is real.

token count per chunk: NOT DISCLOSED — chunk token counts are not reported on the ask path. The character counts below are of the bounded snippet/quote rulesage actually received — a real measurement of what we hold, never an estimate of the chunk.

fused rank	document	page	fused RRF score	snippet chars
#1	RULEBOOK Nemesis: Retaliation — Rulebook (corpus doc 378)	p.10	0.047123 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one))	300
#2	RULEBOOK Nemesis: Retaliation — Rulebook (corpus doc 378)	p.12	0.046032 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one))	300
#3	RULEBOOK Nemesis: Retaliation — Rulebook (corpus doc 378)	p.12	0.045475 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one))	300
#4	RULEBOOK Nemesis: Retaliation — Rulebook (corpus doc 378)	p.10	0.044796 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one))	300
#5	RULEBOOK Nemesis: Retaliation — Rulebook (corpus doc 378)	p.10	0.032787 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one))	300
#6	RULEBOOK Nemesis: Retaliation — Rulebook (corpus doc 378)	p.26	0.032258 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one))	300
#7	RULEBOOK Nemesis: Retaliation — Rulebook (corpus doc 378)	p.13	0.029851 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one))	300
#8	RULEBOOK Nemesis: Retaliation — Rulebook (corpus doc 378)	p.12	0.029644 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one))	300

what the answerer read — the passages it actually had in front of it

what this block IS: the passages the ANSWERING read put in front of the answerer, in the order it read them — the other half of the two reads described above, and the one that decides what the answer could possibly say. Each row names the book it came from and where in that book it sits, what it scored when the search arms were fused, which arm carried it there, and whether the re-ranker chose it or a floor guaranteed it a slot. A row here that no passage-search row names is EXPECTED: a far wider pool, re-ranked, with floors the passage search never applies.

candidate pool: the answering read scored 80 passages, out of a ceiling of 80 set gateway-side. Both figures are reported by the gateway for THIS ask — measurements of what actually happened, not constants read out of anyone's source and printed here on faith.

floors armed for this ask: the base rulebook — armed · surviving errata corrections — not armed · one slot per book on a multi-book read — not armed. Every floor is stated on every ask, armed or not, so a floor that did not apply here is never mistaken for one this app does not know about.

arms fused for this ask: vector + full-text + the doc-priority boost arm. Stated separately from the rows because an arm that ran and carried nothing is a different fact from an arm that never ran.

read at	document	page	fused rank	fused RRF score	carried by	how it got its slot
#1	RULEBOOK Nemesis: Retaliation — Rulebook (corpus doc 378)	p.26	#6	0.032258 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one))	vector + the doc-priority boost arm	the re-ranker chose it
#2	RULEBOOK Nemesis: Retaliation — Rulebook (corpus doc 378)	p.10	#5	0.032787 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one))	vector + the doc-priority boost arm	the re-ranker chose it
#3	RULEBOOK Nemesis: Retaliation — Rulebook (corpus doc 378)	p.12	#2	0.046032 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one))	vector + full-text + the doc-priority boost arm	the re-ranker chose it
#4	RULEBOOK Nemesis: Retaliation — Rulebook (corpus doc 378)	p.38	#33	0.011111 (below 0.016, the low end of the measured band — a weak fuse (that band was taken on two-arm asks; only its low end, one arm's #1 vote, carries over to a 3-arm one))	vector	the re-ranker chose it
#5	RULEBOOK Nemesis: Retaliation — Rulebook (corpus doc 378)	p.13	#12	0.026598 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one))	vector + full-text	the re-ranker chose it
#6	RULEBOOK Nemesis: Retaliation — Rulebook (corpus doc 378)	p.10	#1	0.047123 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one))	vector + full-text + the doc-priority boost arm	the re-ranker chose it
#7	RULEBOOK Nemesis: Retaliation — Rulebook (corpus doc 378)	p.24	#29	0.011765 (below 0.016, the low end of the measured band — a weak fuse (that band was taken on two-arm asks; only its low end, one arm's #1 vote, carries over to a 3-arm one))	vector	the re-ranker chose it
#8	RULEBOOK Nemesis: Retaliation — Rulebook (corpus doc 378)	p.13	#11	0.02683 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one))	vector + full-text	the re-ranker chose it

chosen chunks — what the answer actually cited

#	document	page	quote chars
[1]	RULEBOOK Nemesis: Retaliation — Rulebook (corpus doc 378)	p.10	no quote on the wire
[2]	RULEBOOK Nemesis: Retaliation — Rulebook (corpus doc 378)	p.10	no quote on the wire
[3]	RULEBOOK Nemesis: Retaliation — Rulebook (corpus doc 378)	p.12	no quote on the wire
[4]	RULEBOOK Nemesis: Retaliation — Rulebook (corpus doc 378)	p.13	no quote on the wire
[5]	RULEBOOK Nemesis: Retaliation — Rulebook (corpus doc 378)	p.26	no quote on the wire
[6]	RULEBOOK Nemesis: Retaliation — Rulebook (corpus doc 378)	p.24	no quote on the wire

generation — timing and the path taken

timing split: retrieval 89 ms · first delta 6152 ms · total 26240 ms (retrieval and first-delta both measured from the START of gateway work, so first-delta INCLUDES retrieval — do not subtract)
full breakdown: queued 13997 ms · retrieval 89 ms · ask 12152 ms · gateway work 12243 ms · total 26240 ms
tokens in (the prompt the answerer read): 3603
tokens out (what the answerer generated): 785
tok/sec: 130.6 tok/sec — 785 output tokens in 6.011 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 51s ago)
answerer host (measured by rulesage): reachable (for 22h, checked 0s ago)
answerer node (the seat proxy's own header — this probe, not this ask): node1
stream path: streamed — the gateway pushed at least one accumulated draft
watchdog: first-token watchdog: 30s per arming window (rulesage.table.first-token-watchdog-seconds), re-armed once by the passages frame — so the worst case before a reader falls back to polling is 60s. Whether it actually fired is a BROWSER-side decision that never reaches the server, so it is not recorded here. The stream path above is the server's half of that story: whether a delta was emitted at all.
num_ctx · think posture: both are the CHILD's settings, not rulesage's, and no ask reply carries them — an answer never states which context window or think posture produced it. The live-seat line above reads them from the running child instead, where the gateway can answer for itself; it describes the child NOW, not this ask.

disposition

outcome: ANSWERED — Answered
abstain rationale (n/a — this ruling answered): answered — no abstain rationale applies

setup-shape — why the checklist band did or didn't render

decision: NOT_SETUP_SHAPED — no setup-shape pattern matched this question

errata registry — what the gate above had to match against

this game registers NO errata cards (edition 307), so "no registered errata card matched" above could never have matched one

Errata scope: the gate above matched this ruling's own edition only. When an ask also reads an expansion, that expansion's own registered errata cards stay outside the match — a stated phase-1 limitation, not a failed lookup.