Ruling — Nemesis: Retaliation

You asked

How do I setup the game?

Answered counted as answered

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

To setup the game, perform the following steps:

Game Setup

1. Find the 3 Section border pieces and 3 Round track border pieces, connect them to each other and place them on the table.[1]

2. Place the Undiscovered Hibernatorium tile on top of the Hibernatorium Room.[1][2]

3. Place the Round marker on the 1st slot of the Round track.[2]

4. Place the Lander token on the “10” slot of the Round track.[2]

5. Place the Autodestruction token on the corresponding slot above the Round track.[2]

6. Place 1 Universal marker on the top-most space of the Objective Choice section.[2]

7. Place all 3 Life Support tokens and the Hibernatorium token Inactive side up on the corresponding slots of the 3 Section border pieces.[2]

8. Shuffle all Robot cards, draw 1 without looking at it, and place it face down on the Robot slot of the Section “A” border piece.[2]

9. Place 1 Ammo token (full side up) and 1 Oxygen token on the slots next to the Robot card.[2]

10. Assemble the Robot model and place it on the Hibernatorium (Note: If using the Terrain Expansion, do not assemble the Robot now; place only the base part and wait for the Robot to be revealed to assemble the other part).[3]

11. Shuffle and place both Anti-Aircraft tokens face down, one on top of the other, in the Anti-Aircraft slot on the Section “B” border piece.[3]

12. Place 5 Egg tokens in the Eggs space on the Section “C” border piece.[3]

13. Take 4 Ammo tokens (full side up), 4 Grenade tokens, 4 Oxygen tokens, and 4 Medpack tokens and place them on their corresponding slots next to the Landing Zone.[3]

14. Shuffle all Corridor tiles, put them inside a Corridor insert, and place it near the Round track.[3]

15. One by one, draw 3 random Corridor tiles and connect them to the Landing Zone—place them face up (showing the side with the non-zero values). If any Corridors have a Door slot, place them with the slot on an entrance to the Landing Zone.[1]

16. Take all Room tiles and sort them by their backs into 4 stacks—“A”, “B”, “C”, and “?”; shuffle each stack and place it face down near the Corridor tiles.[1]

Player Setup

1. Find Help cards with numbers corresponding to the number of players, shuffle them, and deal one to each player, who then reveals their card.[4]

2. Take all Objective cards and divide them into 2 decks—Private and Mission—and take the Mission Task deck.[4]

3. From each deck, remove all cards with a Number of Characters symbol higher than the number of Characters taking part in the game.[4]

4. Shuffle each deck separately and:

a. Deal 1 random Private Objective card and 1 random Mission Objective card to each player face down; put the rest back in the box unseen.[4]

b. Draw 1 random Mission Task card and place it face up on the Mission Task slot on the bottom Round track tile; put the rest back in the box.[4] (Note: In Solo/Coop mode, draw and place a number of random Solo/Coop Mission Task cards equal to the number of Characters taking part in the game instead [5]).

5. Shuffle all Character draft cards and deal 2 of those cards to Player 1, which should remain secret from other players.[4]

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

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

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

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

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

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 199 ms · ask 10204 ms · total 10407 ms
single-flight (PR-5): queued 0 ms · generation 10407 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read: [{"page": 8, "score": 0.048652, "snippet": "8 15. One by one, draw 3 random Corridor tiles and/uni00A0connect them to the Landing Zone/uni00A0– place them face up (showing the/uni00A0side with the/uni00A0non-zero values). If any of those Corridors have a Door slot, they should be placed with the/uni00A0slot on an/uni00A0entrance to the/uni00A", "headingPath": "", "sharpsignalDocId": 378}, {"page": 24, "score": 0.044776, "snippet": "24 Place a Room of the ? type. Reminder: Place 1 if you are Moving Cautiously. Entrance Effect: Close all Doors around this Room. Remove this card from the game. 1 2 3 4 5 Reminder: Place 1 if you are Moving Cautiously. 6 1 Place a Room of the ? type. 5 Entrance Effect: Close all Doors around this R", "headingPath": "", "sharpsignalDocId": 378}, {"page": 10, "score": 0.044023, "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": 28, "score": 0.041912, "snippet": "Y ou may keep 1 of them and discard the rest. gaining items search search For each Item Icon in your Room draw 1 Item of the corresponding type. Y ou may keep 1 of them and discard the rest. 19 life support control \"b\" Flip an / in Section B. OR Look at both Anti-Aircraft tokens and place them in an", "headingPath": "", "sharpsignalDocId": 378}, {"page": 10, "score": 0.031746, "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": 10, "score": 0.03125, "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": 10, "score": 0.030769, "snippet": "Since the/uni00A0Contractor already starts with 2 Items, they do not take part in the/uni00A0Support Equipment draft. Perform the/uni00A0following: 1. Take the/uni00A0 Support Equipment deck , shufﬂe it, draw 7/uni00A0cards from it and reveal them to all players. 2. The/uni00A0player with the/uni00A", "headingPath": "", "sharpsignalDocId": 378}, {"page": 26, "score": 0.030303, "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}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show: [{"page": 8, "quote": null, "headingPath": "", "sharpsignalDocId": 378}, {"page": 8, "quote": null, "headingPath": "", "sharpsignalDocId": 378}, {"page": 8, "quote": null, "headingPath": "", "sharpsignalDocId": 378}, {"page": 10, "quote": null, "headingPath": "", "sharpsignalDocId": 378}, {"page": 40, "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.90325 of 2553 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row recorded: Aug 22, 2026 13:32 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.8	0.048652 (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.24	0.044776 (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.10	0.044023 (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.28	0.041912 (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.031746 (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.10	0.03125 (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.10	0.030769 (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.26	0.030303 (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.10	#3	0.044023 (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
#2	RULEBOOK Nemesis: Retaliation — Rulebook (corpus doc 378)	p.8	#1	0.048652 (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
#3	RULEBOOK Nemesis: Retaliation — Rulebook (corpus doc 378)	p.2	#14	0.026546 (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
#4	RULEBOOK Nemesis: Retaliation — Rulebook (corpus doc 378)	p.8	#41	0.012346 (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))	full-text	the re-ranker chose it
#5	RULEBOOK Nemesis: Retaliation — Rulebook (corpus doc 378)	p.8	#10	0.028309 (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.40	#20	0.02381 (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
#7	RULEBOOK Nemesis: Retaliation — Rulebook (corpus doc 378)	p.8	#15	0.025911 (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
#8	RULEBOOK Nemesis: Retaliation — Rulebook (corpus doc 378)	p.24	#2	0.044776 (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

chosen chunks — what the answer actually cited

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

generation — timing and the path taken

timing split: retrieval 199 ms · first delta 6405 ms · total 10407 ms (retrieval and first-delta both measured from the START of gateway work, so first-delta INCLUDES retrieval — do not subtract)
full breakdown: queued 0 ms · retrieval 199 ms · ask 10204 ms · gateway work 10407 ms · total 10407 ms
tokens in (the prompt the answerer read): 3766
tokens out (what the answerer generated): 801
tok/sec: 203.1 tok/sec — 801 output tokens in 3.943 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 4s ago)
answerer host (measured by rulesage): reachable (for 22h, checked 3s 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: NO_APPROVED_CHECKLIST — setup-shaped, but no approved setup checklist exists for this game
pattern that matched: SETUP — "setup" / "set up"
matched words (in the normalized question): setup

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.