Ruling — Gloomhaven: Jaws of the Lion

You asked

how long does an average game take?

Abstained — no grounded answer; closest passages below counted as honest abstain

I looked through Gloomhaven: Jaws of the Lion'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.

RULEBOOK Gloomhaven: Jaws of the Lion — Rulebook · p.12 · Running Out of Cards

Given enough rounds, characters will run out of cards to play because they have lost too many through resting. If a character is unable to play two cards at the start of a round because they do not have at least two cards in their hand, that character becomes exhausted, as described at the top of th

RULEBOOK Gloomhaven: Jaws of the Lion — Rulebook · p.6 · Playing the Game

Now that the game has been set up properly, we can start playing! Gameplay within a scenario is broken up into a series of rounds. In each round, all players will select which ability cards they would like to play. The chosen cards will determine the "initiative order", which is the sequence in whic

RULEBOOK Gloomhaven: Jaws of the Lion — Rulebook · p.3 · Playing by Yourself?

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

RULEBOOK Gloomhaven: Jaws of the Lion — Rulebook · p.23 · Recording Experience Rewards

Each character should now note their experience total, tracked during the scenario on their experience dial each time they gained experience through an action. From now on, you will also gain additional experience for completing a scenario. Completing this and all other scenarios covered in this boo

RULEBOOK Gloomhaven: Jaws of the Lion — Rulebook · p.22 · Long Rest

Characters now have a new type of turn. Instead of selecting two ability cards to play at the beginning of a round, they can declare they will be performing a long rest. The long rest will constitute the character's entire turn for the round, which will occur on initiative 99. performs a "Heal 2, Se

Strategy guides → — community tips, kept separate from rulings

🔧 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

answerer pin (deploy-frozen, attribution only)

unset-dev (corpus lane freezes the deploy value)

timings

search 112 ms · ask 2790 ms · total 2910 ms

single-flight (PR-5)

queued 0 ms · generation 2910 ms

retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read

[{"page": 12, "score": 0.016393, "snippet": "Given enough rounds, characters will run out of cards to play because they have lost too many through resting. If a character is unable to play two cards at the start of a round because they do not have at least two cards in their hand, that character becomes exhausted, as described at the top of th", "headingPath": "Running Out of Cards", "sharpsignalDocId": 61}, {"page": 6, "score": 0.016129, "snippet": "Now that the game has been set up properly, we can start playing! Gameplay within a scenario is broken up into a series of rounds. In each round, all players will select which ability cards they would like to play. The chosen cards will determine the \"initiative order\", which is the sequence in whic", "headingPath": "Playing the Game", "sharpsignalDocId": 61}, {"page": 3, "score": 0.015873, "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": 23, "score": 0.015625, "snippet": "Each character should now note their experience total, tracked during the scenario on their experience dial each time they gained experience through an action. From now on, you will also gain additional experience for completing a scenario. Completing this and all other scenarios covered in this boo", "headingPath": "Recording Experience Rewards", "sharpsignalDocId": 61}, {"page": 22, "score": 0.015385, "snippet": "Characters now have a new type of turn. Instead of selecting two ability cards to play at the beginning of a round, they can declare they will be performing a long rest. The long rest will constitute the character's entire turn for the round, which will occur on initiative 99. performs a \"Heal 2, Se", "headingPath": "Long Rest", "sharpsignalDocId": 61}, {"page": 30, "score": 0.015152, "snippet": "There are a few other rules we weren't able to introduce yet that you will need as you go deeper into the campaign. These are outlined below, but also note that the Rules Glossary contains a comprehensive detailing of all the rules in the game. If you ever have a question about anything, you will fi", "headingPath": "Final Rules", "sharpsignalDocId": 61}, {"page": 18, "score": 0.014925, "snippet": "Congratulations on completing Scenario 2! Remember the scenario doesn't end until the end of the round in which the goal was completed, so you might have extra time at the end to pick up some last-minute loot. After that, make sure to read the conclusion text and rewards, take out the city map board", "headingPath": "Scenario 2 Complete", "sharpsignalDocId": 61}, {"page": 12, "score": 0.014706, "snippet": "Any time a character suffers damage, they reduce their current hit point value by that amount by rotating their hit point dial. If a character ever reaches \"O\" on their hit point dial, they are immediately exhausted. Their figure is removed from the map, and they can no longer participate in the gam", "headingPath": "Character Damage and Exhaustion", "sharpsignalDocId": 61}]

citations (raw) — what the answer cited, chosen from a retrieval this page cannot show

[]

boost provenance — errata + base rulebook (E2/E3)

gate not evaluated for this ruling (boost, supersedence, and wrench all off at ask time), and the base-rulebook arm went unrecorded for the same reason — the wrench that would have stored it was off; rulesage.errata.boost-enabled=false, rulesage.errata.supersedence-enabled=false

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 retained until

Oct 9, 2026 00:12

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. How much wider that pool was is set gateway-side and is NOT REPORTED for this ruling, and neither are the answerer's final rows — so rulesage has nothing of its own to show beside these.

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)	Running Out of Cards	p.12	0.016393 (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)	Playing the Game	p.6	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
#3	RULEBOOK Gloomhaven: Jaws of the Lion — Rulebook (corpus doc 61)	Playing by Yourself?	p.3	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
#4	RULEBOOK Gloomhaven: Jaws of the Lion — Rulebook (corpus doc 61)	Recording Experience Rewards	p.23	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
#5	RULEBOOK Gloomhaven: Jaws of the Lion — Rulebook (corpus doc 61)	Long Rest	p.22	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)	300
#6	RULEBOOK Gloomhaven: Jaws of the Lion — Rulebook (corpus doc 61)	Final Rules	p.30	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
#7	RULEBOOK Gloomhaven: Jaws of the Lion — Rulebook (corpus doc 61)	Scenario 2 Complete	p.18	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
#8	RULEBOOK Gloomhaven: Jaws of the Lion — Rulebook (corpus doc 61)	Character Damage and Exhaustion	p.12	0.014706 (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

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.

the passages the answerer read: NOT RECORDED for this ruling. Any of three things leaves this empty, and they are all different from the answerer having had nothing to read: this ask may never have reached a gateway at all; a multi-book ask keeps each book's own context on that book's own page rather than here; or the gateway build that answered may simply not report it. What this NEVER means is that the answerer read nothing — an answer was composed from passages either way, and their absence here is a gap in what we were told, not in what it read.

chosen chunks — what the answer actually cited

#	document	heading	page	quote chars

generation — timing and the path taken

timing split: retrieval 112 ms · first delta n/a · total 2910 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 112 ms · ask 2790 ms · gateway work 2910 ms · total 2910 ms
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 26s 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: 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 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.