You asked
How do I setup the game?
Answered counted as answeredAsked with: Gloomhaven: Buttons & Bugsbg-393672-en-1e
🔧 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 73 ms · ask 3199 ms · total 3274 ms
- single-flight (PR-5)
- queued 0 ms · generation 3274 ms
- retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read
- [{"page": 4, "score": 0.032787, "snippet": "This guide will be using the Bruiser . If you are new to the world of Gloomhaven, we recommend using the Bruiser to follow along. Gather the following: B The brown hit point dial , set to your character's maximum hit point value for level 1, shown on your character card.", "headingPath": "Character Setup", "sharpsignalDocId": 769}, {"page": 3, "score": 0.032258, "snippet": "A Start by taking the deck of scenario cards from the box. B Then flip over the top card and read the story of That Shrinking Feeling . Before you begin, you will need to choose a character. There are six available characters, each described on the back of their respective character card.", "headingPath": "Getting Started", "sharpsignalDocId": 769}, {"page": 5, "score": 0.031746, "snippet": "C The four level 1 ability cards listed on the back of your character card. These are double-sided and start on their A-side . D Your brown character attack modifier tray. Place a white cube in the topmost slot.", "headingPath": "Character Setup", "sharpsignalDocId": 769}, {"page": 6, "score": 0.03125, "snippet": "It's time to read Scenario 1: A Rude Welcome , the next card in the scenario deck. A Read the scenario entry up to and including the goal. B Retrieve the Bandit Guard monster card , noted in the scenario entry's monster list.", "headingPath": "Scenario Setup", "sharpsignalDocId": 769}, {"page": 8, "score": 0.030769, "snippet": "Take note of the quantity and cube colors of the monsters shown on the map. Place cubes in the map hexes with Bandit Guard artwork: D a green cube in the hex marked with the green cube and E a blue cube in its corresponding hex. F Place your miniature in the starting hex . G Retrieve a monster tray ", "headingPath": "Scenario Setup", "sharpsignalDocId": 769}, {"page": 21, "score": 0.030303, "snippet": "After picking your two cards, choose the initiative value of one of them. This determines when you will take your turn during the round. The lower your initiative ( ), the sooner you act. Next, you'll determine the initiative of the Bandit Guards. Roll the die and move the white cube on the monster ", "headingPath": "2. Ordering of Initiative", "sharpsignalDocId": 769}, {"page": 11, "score": 0.029851, "snippet": "Each scenario is played over a series of rounds , and each round consists of the following steps: 1 Card Selection: First, pick two of your ability cards to play during the round. 2 Ordering of Initiative: Next, determine the order in which you and the monsters will take turns. 3 Character and Monst", "headingPath": "Playing a Scenario", "sharpsignalDocId": 769}, {"page": 10, "score": 0.029412, "snippet": "J Retrieve the red monster modifier tray and place a white cube in the topmost slot. K Keep the condition tokens , icon reference card , and die nearby for later use.", "headingPath": "Scenario Setup", "sharpsignalDocId": 769}]
- citations (raw) — what the answer cited, chosen from a retrieval this page cannot show
- [{"page": 6, "quote": null, "headingPath": "Scenario Setup", "sharpsignalDocId": 769}, {"page": 7, "quote": null, "headingPath": "Scenario Setup", "sharpsignalDocId": 769}, {"page": 8, "quote": null, "headingPath": "Scenario Setup", "sharpsignalDocId": 769}, {"page": 10, "quote": null, "headingPath": "Scenario Setup", "sharpsignalDocId": 769}]
- boost provenance — errata + base rulebook (E2/E3)
-
no registered errata card matched this query; base rulebook doc 769 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 769 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.89251 of 828 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
- debug row retained until
- Nov 12, 2026 01:10
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 Gloomhaven: Buttons & Bugs — Rulebook (corpus doc 769) | Character Setup | p.4 | 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)) | 271 |
| #2 | RULEBOOK Gloomhaven: Buttons & Bugs — Rulebook (corpus doc 769) | Getting Started | p.3 | 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)) | 289 |
| #3 | RULEBOOK Gloomhaven: Buttons & Bugs — Rulebook (corpus doc 769) | Character Setup | 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)) | 211 |
| #4 | RULEBOOK Gloomhaven: Buttons & Bugs — Rulebook (corpus doc 769) | Scenario Setup | p.6 | 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)) | 225 |
| #5 | RULEBOOK Gloomhaven: Buttons & Bugs — Rulebook (corpus doc 769) | Scenario Setup | p.8 | 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 Gloomhaven: Buttons & Bugs — Rulebook (corpus doc 769) | 2. Ordering of Initiative | p.21 | 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 Gloomhaven: Buttons & Bugs — Rulebook (corpus doc 769) | Playing a Scenario | p.11 | 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 Gloomhaven: Buttons & Bugs — Rulebook (corpus doc 769) | Scenario Setup | p.10 | 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)) | 166 |
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 39 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 Gloomhaven: Buttons & Bugs — Rulebook (corpus doc 769) | Scenario Setup | p.6 | #4 | 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)) | vector + the doc-priority boost arm | the re-ranker chose it |
| #2 | RULEBOOK Gloomhaven: Buttons & Bugs — Rulebook (corpus doc 769) | Scenario Setup | p.7 | #19 | 0.012658 (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 |
| #3 | RULEBOOK Gloomhaven: Buttons & Bugs — Rulebook (corpus doc 769) | Character Setup | p.4 | #1 | 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 |
| #4 | RULEBOOK Gloomhaven: Buttons & Bugs — Rulebook (corpus doc 769) | Scenario Setup | p.9 | #9 | 0.014493 (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 Gloomhaven: Buttons & Bugs — Rulebook (corpus doc 769) | Playing a Scenario | p.11 | #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)) | vector + the doc-priority boost arm | the re-ranker chose it |
| #6 | RULEBOOK Gloomhaven: Buttons & Bugs — Rulebook (corpus doc 769) | Scenario Setup | p.10 | #8 | 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 |
| #7 | RULEBOOK Gloomhaven: Buttons & Bugs — Rulebook (corpus doc 769) | Scenario Setup | p.8 | #5 | 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)) | vector + the doc-priority boost arm | the re-ranker chose it |
| #8 | RULEBOOK Gloomhaven: Buttons & Bugs — Rulebook (corpus doc 769) | Character Setup | p.5 | #3 | 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 |
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 Gloomhaven: Buttons & Bugs — Rulebook (corpus doc 769) | Scenario Setup | p.6 | no quote on the wire |
| [2] | RULEBOOK Gloomhaven: Buttons & Bugs — Rulebook (corpus doc 769) | Scenario Setup | p.7 | no quote on the wire |
| [3] | RULEBOOK Gloomhaven: Buttons & Bugs — Rulebook (corpus doc 769) | Scenario Setup | p.8 | no quote on the wire |
| [4] | RULEBOOK Gloomhaven: Buttons & Bugs — Rulebook (corpus doc 769) | Scenario Setup | p.10 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 73 ms · first delta 1418 ms · total 3274 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 73 ms · ask 3199 ms · gateway work 3274 ms · total 3274 ms
- tokens in (the prompt the answerer read)
- 863
- tokens out (what the answerer generated)
- 263
- tok/sec
- 143.3 tok/sec — 263 output tokens in 1.835 s of generation
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 13s 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
- 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 703), 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.