You asked
How do I setup the game?
Abstained — no grounded answer; closest passages below counted as honest abstainAnswered before
This question didn't get an answer just now — but Gloomhaven: Jaws of the Lion has been asked something like it before. The corpus may have changed since, so check the date and the answerer on each one before you rule from it.
The answerer couldn't ground a confident answer in the rulebook. The closest rulebook passages are below — check them before ruling.
The last new aspect of setup is the deck of battle goals. From now on, at the start of each scenario, retrieve the deck of battle goals from the game box, shuffle it, and deal two random cards to each character in secret. Each character will then choose one of these goals to keep for the scenario, d
Introduction. Scenario I Rules Play Area Setup. Scenario Book Features Playing the Game Card Selection. Ordering of Initiative. Move. Character Turns.. Attack. Attack Modifier Cards. Range and Melee Advantage and Disadvantage. Line-of-Sight.. Damage and Killing Monsters. Target. Conditions.. Suffer
If you are playing the game by yourself, you will need to control two separate characters. Take note that this is a more complex experience. If there are two to four players, it is highly recommended that each player only controls a single character. To choose which character to play, find the large
Using these character materials and other components, we will now set up Scenario 1. Each player should place their character mat ①, player reference , six level "A" ability cards 3 , attack modifier deck (the deck of smaller cards) , and hit point dial in front of them. The red side of the dial sho
Starting now, each time you successfully complete a scenario, you must encounter a city event. Before doing this for the first time, however, retrieve the "events" deck from the game box and shuffle the cards. Then, draw the top card of the deck and read the introductory text ①on the front. This wil
Strategy guides → — community tips, kept separate from rulings
🔧 debug — where this ruling came from
- outcome
- ABSTAINED — Abstained — no grounded answer; closest passages below
- corpus profile
- live
- answerer pin (deploy-frozen, attribution only)
- gemma4:26b think:false 5571076f3d70
- timings
- search 226 ms · ask 8623 ms · total 8860 ms
- single-flight (PR-5)
- queued 0 ms · generation 8860 ms
- retrieval refs (raw)
- [{"page": 25, "score": 0.032522, "snippet": "The last new aspect of setup is the deck of battle goals. From now on, at the start of each scenario, retrieve the deck of battle goals from the game box, shuffle it, and deal two random cards to each character in secret. Each character will then choose one of these goals to keep for the scenario, d", "headingPath": "Battle Goals", "sharpsignalDocId": 61}, {"page": 2, "score": 0.027032, "snippet": "Introduction. Scenario I Rules Play Area Setup. Scenario Book Features Playing the Game Card Selection. Ordering of Initiative. Move. Character Turns.. Attack. Attack Modifier Cards. Range and Melee Advantage and Disadvantage. Line-of-Sight.. Damage and Killing Monsters. Target. Conditions.. Suffer ", "headingPath": "Table of Contents", "sharpsignalDocId": 61}, {"page": 3, "score": 0.016129, "snippet": "If you are playing the game by yourself, you will need to control two separate characters. Take note that this is a more complex experience. If there are two to four players, it is highly recommended that each player only controls a single character. To choose which character to play, find the large", "headingPath": "Playing by Yourself?", "sharpsignalDocId": 61}, {"page": 4, "score": 0.015873, "snippet": "Using these character materials and other components, we will now set up Scenario 1. Each player should place their character mat ①, player reference , six level \"A\" ability cards 3 , attack modifier deck (the deck of smaller cards) , and hit point dial in front of them. The red side of the dial sho", "headingPath": "Play Area Setup", "sharpsignalDocId": 61}, {"page": 24, "score": 0.015625, "snippet": "Starting now, each time you successfully complete a scenario, you must encounter a city event. Before doing this for the first time, however, retrieve the \"events\" deck from the game box and shuffle the cards. Then, draw the top card of the deck and read the introductory text ①on the front. This wil", "headingPath": "New City Interaction: Events", "sharpsignalDocId": 61}, {"page": 14, "score": 0.015385, "snippet": "And so, we move on to Scenario 2! First, start by turning to Scenario 2 in the Scenario Book. Then, the setup will be largely the same as the setup in Scenario 1 (see p. 4), with the following changes:", "headingPath": "Scenario 2 Rules", "sharpsignalDocId": 61}, {"page": 25, "score": 0.015152, "snippet": "Set the monsters to level \"1\" and then, because this scenario is a single large room, set up all indicated monsters. Instead of introducing new monsters to the scenario by opening doors, more monsters will be added later through spawning. The special rules of the scenario will dictate how and when t", "headingPath": "Spawning Monsters", "sharpsignalDocId": 61}, {"page": 13, "score": 0.014925, "snippet": "Now that you have recorded everything important pertaining to the outcome of Scenario 1, you can continue reading the next page to start playing Scenario 2, or you can put everything back in the box to continue the campaign another time. The most important thing is to put all the materials currently", "headingPath": "Saving", "sharpsignalDocId": 61}]
- citations (raw)
- []
- boost provenance — errata + base rulebook (E2/E3)
-
no registered errata card matched this query; base-rulebook boost: not recorded (this ruling predates it); rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base-rulebook boost: not recorded (this ruling predates it)
- answered-before recall
-
past answered rulings were found and offered
similarity threshold in force: 0.55 (rulesage.answered-before.similarity-threshold; the exact-question tier is not gated by it)
- ruling 1750 — matched by the same question (normalized, punctuation folded) — measured similarity 1.0
- ruling 661 — matched by the same question (normalized, punctuation folded) — measured similarity 1.0
- debug row retained until
- Oct 23, 2026 20:54
retrieval — what the search arm returned
score = the fused retrieval score (reciprocal-rank fusion over the search arms) — NOT a cosine similarity. How many arms fused this ruling was NOT RECORDED (it predates the boost trail, ran on the path that stored none, or stored one that could not be read), and the ceiling depends on that count (ceiling = arms/(k+1) at k=60): 2 arms top out at 0.03279; 3 arms top out at 0.04918. So a score above 0.03279 here is not an anomaly: it is arithmetic proof a boost arm voted, and the measured band 0.016–0.033 (taken on two-arm asks) is what does not apply. 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: Jaws of the Lion — Rulebook (corpus doc 61) | Battle Goals | p.25 | 0.032522 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded)) | 300 |
| #2 | RULEBOOK Gloomhaven: Jaws of the Lion — Rulebook (corpus doc 61) | Table of Contents | p.2 | 0.027032 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded)) | 300 |
| #3 | RULEBOOK Gloomhaven: Jaws of the Lion — Rulebook (corpus doc 61) | Playing by Yourself? | p.3 | 0.016129 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded)) | 300 |
| #4 | RULEBOOK Gloomhaven: Jaws of the Lion — Rulebook (corpus doc 61) | Play Area Setup | p.4 | 0.015873 (below the measured healthy band (< 0.016) — a weak fuse on a two-arm ask, and this ruling's arm count was never recorded) | 300 |
| #5 | RULEBOOK Gloomhaven: Jaws of the Lion — Rulebook (corpus doc 61) | New City Interaction: Events | p.24 | 0.015625 (below the measured healthy band (< 0.016) — a weak fuse on a two-arm ask, and this ruling's arm count was never recorded) | 300 |
| #6 | RULEBOOK Gloomhaven: Jaws of the Lion — Rulebook (corpus doc 61) | Scenario 2 Rules | p.14 | 0.015385 (below the measured healthy band (< 0.016) — a weak fuse on a two-arm ask, and this ruling's arm count was never recorded) | 201 |
| #7 | RULEBOOK Gloomhaven: Jaws of the Lion — Rulebook (corpus doc 61) | Spawning Monsters | p.25 | 0.015152 (below the measured healthy band (< 0.016) — a weak fuse on a two-arm ask, and this ruling's arm count was never recorded) | 300 |
| #8 | RULEBOOK Gloomhaven: Jaws of the Lion — Rulebook (corpus doc 61) | Saving | p.13 | 0.014925 (below the measured healthy band (< 0.016) — a weak fuse on a two-arm ask, and this ruling's arm count was never recorded) | 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 |
|---|
generation — timing and the path taken
- timing split
- retrieval 226 ms · first delta n/a · total 8860 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 226 ms · ask 8623 ms · gateway work 8860 ms · total 8860 ms
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 38s ago)
- stream path
- not recorded — this ruling predates the stream-path column (V41)
- 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
- the answerer offered no rationale text with this refusal (or the ruling predates the abstain_rationale column, V41)
setup-shape — why the checklist band did or didn't render
- decision
- SERVED — setup-shaped and this game's approved setup checklist is offered above
- 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 9), 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.