You asked
How do I setup for 1 player
Abstained — no grounded answer; closest passages below counted as honest abstainAsked with: Euthia: Torment of Resurrectionbg-295785-en-1e
I looked through Euthia: Torment of Resurrection's rulebook and couldn't find a solid answer to that one — and I'd rather tell you so than guess at your table. Try asking it another way, or ask me about setup, turns, or how the game ends: those I know cold.
The closest rulebook passages are below — check them before ruling.
Example of a full 4-player competitive setup for 'Defending the Settlements' Beginning with the starting player and proceeding clockwise, each player takes a turn. At the beginning of your first turn of the game, place your Hero on the Church at the center of the Starting Map tile. Note: Some Scenar
Place the Scenario/Trade board to the side of the playing area and set it up as follows: Randomly select the starting player. Place one of the starting player's Hero tokens on space 1 on the Round track. The starting player does not change during gameplay. All players place one of their Hero tokens
These are the setup rules for a 2-4 player game. For the Solo Game, see page 31 . Choose one of the Scenarios from the Scenario book. The choice will influence further steps of Setup. For your first game, we suggest playing The Hunt . All Scenarios use similar basic rules. Special rules for a partic
For a 3-player game using the Defending the Settlements Scenario. Use all of the Fixed Map tiles from Chapters I, II, III, and IV. Randomly choose 1 Encounter Map tile from Chapters I and II, and 2 Encounter Map tiles from Chapter III. There are no Scenario Map tiles used in this Scenario. From the
Sort the Natural Resource tiles into stacks based on the illustration on their reverse side. Shuffle each stack separately and place them face down nearby. Sort the Treasure tiles into stacks based on the illustrations on their reverse side. Shuffle each stack separately and place them face down nea
🔧 debug — where this ruling came from
- outcome
- ABSTAINED — Abstained — no grounded answer; closest passages below
- warm abstain
-
- this ruling — W1 — generic warm abstain · receipt: none (generic)
- corpus profile
- live,vps
- answerer pin (deploy-frozen, attribution only)
- gemma4:26b think:false 5571076f3d70
- timings
- search 100 ms · ask 4966 ms · total 5068 ms
- single-flight (PR-5)
- queued 0 ms · generation 5068 ms
- retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read
- [{"page": 9, "score": 0.047183, "snippet": "Example of a full 4-player competitive setup for 'Defending the Settlements' Beginning with the starting player and proceeding clockwise, each player takes a turn. At the beginning of your first turn of the game, place your Hero on the Church at the center of the Starting Map tile. Note: Some Scenar", "headingPath": "Other Setup · Player's Turn · Gameplay", "sharpsignalDocId": 1228}, {"page": 7, "score": 0.046642, "snippet": "Place the Scenario/Trade board to the side of the playing area and set it up as follows: Randomly select the starting player. Place one of the starting player's Hero tokens on space 1 on the Round track. The starting player does not change during gameplay. All players place one of their Hero tokens ", "headingPath": "Scenario/Trade Board · Other Setup", "sharpsignalDocId": 1228}, {"page": 5, "score": 0.032787, "snippet": "These are the setup rules for a 2-4 player game. For the Solo Game, see page 31 . Choose one of the Scenarios from the Scenario book. The choice will influence further steps of Setup. For your first game, we suggest playing The Hunt . All Scenarios use similar basic rules. Special rules for a partic", "headingPath": "Setup · Scenario Selection · Map · Fixed Map tiles · Scenario Map tiles · Other Map tiles", "sharpsignalDocId": 1228}, {"page": 5, "score": 0.031746, "snippet": "For a 3-player game using the Defending the Settlements Scenario. Use all of the Fixed Map tiles from Chapters I, II, III, and IV. Randomly choose 1 Encounter Map tile from Chapters I and II, and 2 Encounter Map tiles from Chapter III. There are no Scenario Map tiles used in this Scenario. From the ", "headingPath": "For example: · Choosing and Preparing a Hero", "sharpsignalDocId": 1228}, {"page": 8, "score": 0.03125, "snippet": "Sort the Natural Resource tiles into stacks based on the illustration on their reverse side. Shuffle each stack separately and place them face down nearby. Sort the Treasure tiles into stacks based on the illustrations on their reverse side. Shuffle each stack separately and place them face down nea", "headingPath": "Other Setup", "sharpsignalDocId": 1228}, {"page": 1, "score": 0.030415, "snippet": "ObjectoftheGame......................................... 1 ComponentList............................................ 2 Setup........................................................... 5 HeroBoard............................................................... 6 Gameplay...............................", "headingPath": "", "sharpsignalDocId": 1228}, {"page": 16, "score": 0.030303, "snippet": "These options are all fully explained in the sections about Hero tiles on page 26 and Items on page 28 . You may equip and/or unequip any number of your Equipment tiles on your Hero board at this time. This is also your last opportunity to use any number of your Item and Ability tiles that can only ", "headingPath": "Unveil Hero Tiles / Train Ability / Unlock Hero or Equipment Slot · Determine Monster-player", "sharpsignalDocId": 1228}, {"page": 18, "score": 0.029851, "snippet": "Both the Hero-player and Monster-player may choose this option. ◆ The Monster-player may use 1 Gaar token to re-roll any 1 die and add 2 to the Combat Value. ◆ The Hero-player may use 1 Gaar token to re-roll any 1 die and subtract 2 from the Combat Value. For more information about Gaar tokens, see ", "headingPath": "Use a Gaar Token · Play a Card", "sharpsignalDocId": 1228}]
- citations (raw) — what the answer cited, chosen from a retrieval this page cannot show
- []
- boost provenance — errata + base rulebook (E2/E3)
-
no registered errata card matched this query; base rulebook doc 1228 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 1228 boosted
- answered-before recall
-
no past answered ruling for this game matched closely enough
similarity threshold in force: 0.55 (rulesage.answered-before.similarity-threshold; the exact-question tier is not gated by it)
- debug row recorded
- Sep 4, 2026 22:55 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 | heading | page | fused RRF score | snippet chars |
|---|---|---|---|---|---|
| #1 | RULEBOOK Euthia: Torment of Resurrection — Rulebook (corpus doc 1228) | Other Setup · Player's Turn · Gameplay | p.9 | 0.047183 (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 Euthia: Torment of Resurrection — Rulebook (corpus doc 1228) | Scenario/Trade Board · Other Setup | p.7 | 0.046642 (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 Euthia: Torment of Resurrection — Rulebook (corpus doc 1228) | Setup · Scenario Selection · Map · Fixed Map tiles · Scenario Map tiles · Other Map tiles | p.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)) | 300 |
| #4 | RULEBOOK Euthia: Torment of Resurrection — Rulebook (corpus doc 1228) | For example: · Choosing and Preparing a Hero | p.5 | 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 |
| #5 | RULEBOOK Euthia: Torment of Resurrection — Rulebook (corpus doc 1228) | Other Setup | p.8 | 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 |
| #6 | RULEBOOK Euthia: Torment of Resurrection — Rulebook (corpus doc 1228) | p.1 | 0.030415 (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 Euthia: Torment of Resurrection — Rulebook (corpus doc 1228) | Unveil Hero Tiles / Train Ability / Unlock Hero or Equipment Slot · Determine Monster-player | p.16 | 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 |
| #8 | RULEBOOK Euthia: Torment of Resurrection — Rulebook (corpus doc 1228) | Use a Gaar Token · Play a Card | p.18 | 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 |
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 | heading | page | fused rank | fused RRF score | carried by | how it got its slot |
|---|---|---|---|---|---|---|---|
| #1 | RULEBOOK Euthia: Torment of Resurrection — Rulebook (corpus doc 1228) | Scenario/Trade Board · Other Setup | p.7 | #2 | 0.046642 (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 Euthia: Torment of Resurrection — Rulebook (corpus doc 1228) | Other Setup · Player's Turn · Gameplay | p.9 | #1 | 0.047183 (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 Euthia: Torment of Resurrection — Rulebook (corpus doc 1228) | Revealing an Encounter · Teleport · Portals · Other Teleport Effects | p.13 | #10 | 0.027052 (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 Euthia: Torment of Resurrection — Rulebook (corpus doc 1228) | Griffin · Setup · Special Rules | p.35 | #9 | 0.029412 (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 |
| #5 | RULEBOOK Euthia: Torment of Resurrection — Rulebook (corpus doc 1228) | Use a Gaar Token · Play a Card | p.18 | #8 | 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)) | vector + the doc-priority boost arm | the re-ranker chose it |
| #6 | RULEBOOK Euthia: Torment of Resurrection — Rulebook (corpus doc 1228) | For example: · Choosing and Preparing a Hero | p.5 | #4 | 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)) | vector + the doc-priority boost arm | the re-ranker chose it |
| #7 | RULEBOOK Euthia: Torment of Resurrection — Rulebook (corpus doc 1228) | Final Scoring · Skoldur · Dwurt Tokens | p.34 | #20 | 0.013333 (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 Euthia: Torment of Resurrection — Rulebook (corpus doc 1228) | Setup · Scenario Selection · Map · Fixed Map tiles · Scenario Map tiles · Other Map tiles | p.5 | #3 | 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 |
chosen chunks — what the answer actually cited
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.
| # | document | heading | page | quote chars |
|---|
generation — timing and the path taken
- timing split
- retrieval 100 ms · first delta 4947 ms · total 5068 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 100 ms · ask 4966 ms · gateway work 5068 ms · total 5068 ms
- tokens in (the prompt the answerer read)
- 3135
- tokens out (what the answerer generated)
- 9
- tok/sec
- 176.5 tok/sec — 9 output tokens in 0.051 s of generation
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 13s 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
- ABSTAINED — Abstained — no grounded answer; closest passages below
- abstain rationale
-
I don't have enough information.
BOILERPLATE, not reasoning: this is the answerer's fixed abstention phrase, the same sentence it emits whenever it declines. It records THAT the answerer declined and never why — no per-ruling reason was captured, because none was sent. Hostile corpus/LLM text, rendered escaped
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 1158), 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.