You asked
How should we prepare everything before the first turn?
Answered counted as answeredAsked with: Arcadia Questbg-155068-en-1e
To prepare for a scenario (Guild Setup), follow these steps: 1. Choose your Guild [1] 2. Choose or Draft 3 Heroes [1] 3. Get the 5 Starter Deck cards [1] 4. Scatter several Exploration tokens around the board according to the scenario instructions, laying some face up and others face down [2]
🔧 debug — where this ruling came from
- outcome
- ANSWERED — Answered
- corpus profile
- live
- answerer pin (deploy-frozen, attribution only)
- gemma4:26b think:false 5571076f3d70
- timings
- search 226 ms · ask 12381 ms · total 34362 ms
- single-flight (PR-5)
- queued 21745 ms · generation 12617 ms
- retrieval refs (raw)
- [{"page": 7, "score": 0.032787, "snippet": "Once players are more familiarized with the game and each Hero's capabilities, they may want to pick their Heroes in a more structured fashion. If all players agree, they can choose their Heroes at the start of a campaign by using the drafting method. Shuffle all the Hero cards and divide them among", "headingPath": "ADVANCED: DRAFTING HEROES", "sharpsignalDocId": 415}, {"page": 12, "score": 0.032258, "snippet": "Spawn tile Place the spawn tile next to the game board. Common Area - Place in a common area around the game board, within reach of all players, the piles of Wound tokens, Death tokens and coins, as well as the Attack and Defense dice. Heroes Starting Areas Indicated in the scenario map are the Star", "headingPath": "ADVANCED: DRAFTING HEROES", "sharpsignalDocId": 415}, {"page": 10, "score": 0.031746, "snippet": "The Campaign Book contains detailed descriptions of all the scenarios that make up the campaign. Once a scenario has been chosen to play, it must be set up on the play area. The entry for the scenario contains a detailed list of all the components used in it, as well as the quantity required. To ens", "headingPath": "ADVANCED: DRAFTING HEROES", "sharpsignalDocId": 415}, {"page": 29, "score": 0.03125, "snippet": "The reverse side of the Campaign Sheet is used to keep track of the Guilds, indicating which Heroes each player chose and what are their current Upgrade cards and Death Curses. During a campaign, after a scenario is finished (but before its Upgrade Phase), players will make a record of what they hav", "headingPath": "■ SELF SACRIFICE", "sharpsignalDocId": 415}, {"page": 9, "score": 0.030769, "snippet": "In order to defeat the evil rule of Lord Fang, the Heroes will need to first make their way from the outskirts to the very heart of the city of Arcadia. As they progress, they diminish the power base of the vampire lord, while gaining more power themselves. Only after much adventuring will they be r", "headingPath": "ADVANCED: DRAFTING HEROES", "sharpsignalDocId": 415}, {"page": 11, "score": 0.030303, "snippet": "Exploration tokens After making sure to put back in the box any remaining Quest tokens, shuffle the 14 Exploration tokens face down. Each scenario indicates the number of Exploration tokens that will be used in the game. Randomly pick that number of tokens and place them in the indicated spaces on t", "headingPath": "ADVANCED: DRAFTING HEROES", "sharpsignalDocId": 415}, {"page": 7, "score": 0.029851, "snippet": "Players are able to choose the path their campaign takes, navigating through six out of eleven available scenarios, so each time the campaign is played it can have a different configuration of scenarios. The feats accomplished by a Guild in each scenario can grant it a significant strategic advantag", "headingPath": "GAME COMPONENTS", "sharpsignalDocId": 415}, {"page": 36, "score": 0.029412, "snippet": "PLAYER TURN Activate a Hero or Rest the Guild. Hero Activation (in any order): ◆ M ovement (3 Movement points to move 1 Space, open/close door or use portal). ◆ A ttack (exhaust Attack card, roll Attack dice vs. target’s Defense). Rest ◆ U nexhaust cards (remove all Guild tokens). ◆ R eorganize card", "headingPath": "", "sharpsignalDocId": 415}]
- citations (raw)
- [{"page": 36, "quote": null, "headingPath": "", "sharpsignalDocId": 415}, {"page": 25, "quote": null, "headingPath": "■ MONSTER ATTACK", "sharpsignalDocId": 415}]
- boost provenance — errata + base rulebook (E2/E3)
-
no registered errata card matched this query; base rulebook doc 415 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 415 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)
- debug row retained until
- Nov 7, 2026 05:02
retrieval — what the search arm returned
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 Arcadia Quest — Rulebook (corpus doc 415) | ADVANCED: DRAFTING HEROES | p.7 | 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 |
| #2 | RULEBOOK Arcadia Quest — Rulebook (corpus doc 415) | ADVANCED: DRAFTING HEROES | p.12 | 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 |
| #3 | RULEBOOK Arcadia Quest — Rulebook (corpus doc 415) | ADVANCED: DRAFTING HEROES | 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 |
| #4 | RULEBOOK Arcadia Quest — Rulebook (corpus doc 415) | ■ SELF SACRIFICE | p.29 | 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 |
| #5 | RULEBOOK Arcadia Quest — Rulebook (corpus doc 415) | ADVANCED: DRAFTING HEROES | p.9 | 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 |
| #6 | RULEBOOK Arcadia Quest — Rulebook (corpus doc 415) | ADVANCED: DRAFTING HEROES | p.11 | 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 |
| #7 | RULEBOOK Arcadia Quest — Rulebook (corpus doc 415) | GAME COMPONENTS | p.7 | 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 Arcadia Quest — Rulebook (corpus doc 415) | p.36 | 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)) | 300 |
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 |
|---|---|---|---|---|
| [1] | RULEBOOK Arcadia Quest — Rulebook (corpus doc 415) | p.36 | no quote on the wire | |
| [2] | RULEBOOK Arcadia Quest — Rulebook (corpus doc 415) | ■ MONSTER ATTACK | p.25 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 226 ms · first delta 12007 ms · total 34362 ms (retrieval and first-delta both measured from the START of gateway work, so first-delta INCLUDES retrieval — do not subtract)
- full breakdown
- queued 21745 ms · retrieval 226 ms · ask 12381 ms · gateway work 12617 ms · total 34362 ms
- tokens in (the prompt the answerer read)
- 4369
- tokens out (what the answerer generated)
- 75
- tok/sec
- 133.7 tok/sec — 75 output tokens in 0.561 s of generation
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 51s ago)
- 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 344), 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.