Ruling — Bonfire

You asked

How do I setup the game?

Answered counted as answered

Asked with: Bonfirebg-304420-en-1e

**Game Board Setup**

1. Place the Game Board in the play area.[1]

2. Shuffle the Tasks and place them with the dark side face up on the islands: for 4 players, place 3 Tasks on each island; for 3 players, place 2 Tasks on each of the 4 corner islands and 3 Tasks on each remaining island; for 1 or 2 players, place 2 Tasks on each island (return any remaining Tasks to the box).[1]

3. Place each Guardian on the island of its respective color.[1]

4. Stack the Countdown Tiles in ascending order and place the pile on the designated space on the Game Board.[1]

5. Place the 6 Elders face up on the designated spaces on the Game and Board.[1]

6. In a 1 or 2 player game, return 1 of each of the 7 Portal Tiles back to the box; shuffle the Portal Tiles and distribute them evenly among the 7 spaces surrounding the Great Bonfire on the Game Board.[1]

7. Place the Great Bonfire on its space on the Game Board and make sure its tip is pointing in the direction shown.[1]

8. Shuffle the Path Tiles and place them as 2-3 face down piles next to the Game Board, then reveal 4 Tiles and place them on the designated spaces on the Game Board creating the display.[1]

9. Shuffle the Specialists and place the Gnome Pile face down beside the Board; draw 6 Specialists and place them face up on the designated spaces of the Game Board.[1]

10. Place 1 Neutral Novice on each of the 5 Common Tasks printed on the Game Board.[1]

11. Take all components of your player color: place your Score Marker and your 0/50-Marker on the space 0 of the Scoring Track (flip your 0/50-Marker as soon as you exceed 50 Points) and place your Ship on the landing stage on the Game Board.[1]

12. Place the Action Tiles and Resources in a general supply next to the Game Board.[1]

13. Shuffle your Fate Tiles and create a face up personal supply with 7 of them next to your Action Overview, keeping the remaining Tile in front of you.[2]

14. Shuffle the 10 Offering Tiles face down and place them as 2 piles with 5 Offering Tiles each on your Action Overview, then flip the topmost Tile of each pile face up.[2]

**Player Board Setup**

1. Place your Player Board in front of you.[2]

2. Attach a Starting Tile for Guardians to your Player Board and place your Guardian onto it.[2]

3. For 1 player: Take 1 Extension for each player (ensuring the one with the oval Building is included) and distribute 1 to each player at random; attach the Extension to your Player Board; whoever received the oval Building is the Starting Player.[2]

4. Place your Novices on the 7 corresponding spaces.[2]

5. Before taking your first turn, decide to either use the Fate Tile in front of you or swap it with the one in the middle of your personal supply, then place the chosen Tile on the marked spaces in the center of your Fate Area.[2]

6. Take 1 of each of the 6 Resources and place them in your supply on the left side of the Player Board.[2]

7. Take 5 Action Tiles (2 yellow Tiles and 3 Tiles matching the 3 colors on your chosen Fate Tile) and place these in your supply on the right side of your Player Board.[2]

8. Place the Action Overview next to your Player Board.[2]

9. Place your Overview Card nearby.[2]

**Solo Play Setup (for playing against "Tom")**

1. Randomly take 7 blue, 7 red, and 6 yellow Tasks and distribute them randomly among the islands, ensuring each island contains 2 differently colored Tasks.[3]

2. All Portals on a single space of the Great Bonfire must be different.[3]

3. Do not use the 3 Specialists; use the Extension showing the oval Building as you are always the Starting Player.[3]

4. For Tom's Player Board: take a Player Board and attach an Extension and a Starting Tile for Guardians, then place his Guardian on her Starting Tile.[3]

5. Place 4 of Tom's Novices next to his Player Board and place his Score Marker on the space 0 of the Scoring Track.[3]

6. Shuffle the 8 Tom Cards to form a draw pile ('Tom Pile') and place it nearby, face down.[3]

[1] RULEBOOK Bonfire — Rulebook · p.4

[2] RULEBOOK Bonfire — Rulebook · p.5 · PLAYER BOARDS

[3] RULEBOOK Bonfire — Rulebook · p.12 · SOLO PLAY · SETUP · COURSE OF THE GAME

🔧 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 80 ms · ask 10582 ms · total 10664 ms
single-flight (PR-5): queued 0 ms · generation 10664 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read: [{"page": 12, "score": 0.048131, "snippet": "You will play a 2-player game against \"Tom\" (which is short for \"AuTOMatic Player\"), a virtual player who uses a modified set of rules. He performs actions determined by a deck of cards in order to score Points. Your goal is to score more Points than Tom. All rules of a 2-player game apply for Solo ", "headingPath": "SOLO PLAY · SETUP · COURSE OF THE GAME", "sharpsignalDocId": 523}, {"page": 2, "score": 0.047379, "snippet": "Setup: Game Board......................................................................................................................................................................................... Setup: Player Boards.............................................................................", "headingPath": "", "sharpsignalDocId": 523}, {"page": 2, "score": 0.046394, "snippet": "Setup: Player Boards....................................................................................................................................................................................... Game Overview...................................................................................", "headingPath": "", "sharpsignalDocId": 523}, {"page": 5, "score": 0.032787, "snippet": "Place your Player Board in front of you. Attach a Starting Tile for Guardians to your Player Board and place your Guardian onto it. 1 of the players: Take 1 Extension for each player (making sure the one with the oval Building is among them) and distribute 1 to each player at random. Every player: A", "headingPath": "PLAYER BOARDS", "sharpsignalDocId": 523}, {"page": 4, "score": 0.031746, "snippet": "When playing Bonfire for the first time, I recommend to place Tasks of different colors on each island. GAME BOARD The game is mostly independent of the player count. The exceptions are emphasized in green writing and summarized here: • Number of Tasks (Page 4, Step 2) • Number of Portals in a 1 or ", "headingPath": "", "sharpsignalDocId": 523}, {"page": 2, "score": 0.030886, "snippet": "Game Components....................................................................................................................................................................................... Setup: Game Board....................................................................................", "headingPath": "", "sharpsignalDocId": 523}, {"page": 8, "score": 0.030303, "snippet": "With the help of your Ship, you can move to 2 different types of islands: Those where you can retrieve Guardians and those where you can receive Tasks. When you move your Ship for the first time in a game, pay 1 Action Tile to move to any island of your choice. The next time, when you move your Ship", "headingPath": "Move your ShIP", "sharpsignalDocId": 523}, {"page": 6, "score": 0.029851, "snippet": "Here we provide a rough overview of the game; a more detailed description will follow in the next chapters. You alternate taking single turns in clockwise order (Page 7 onward, a PlayEr's Turn ). During the course of the game your will receive and fulfill Tasks (Page 9, rEcEivE a Task ). With a fulf", "headingPath": "GAME OVERVIEW · HOW DOES THE GAME PLAY? · WHAT CAN I DO ON MY TURN? · HOW DO I GAIN POINTS?", "sharpsignalDocId": 523}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show: [{"page": 4, "quote": null, "headingPath": "", "sharpsignalDocId": 523}, {"page": 5, "quote": null, "headingPath": "PLAYER BOARDS", "sharpsignalDocId": 523}, {"page": 12, "quote": null, "headingPath": "SOLO PLAY · SETUP · COURSE OF THE GAME", "sharpsignalDocId": 523}]
boost provenance — errata + base rulebook (E2/E3): no registered errata card matched this query; base rulebook doc 523 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 523 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 11, 2026 09:03

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 Bonfire — Rulebook (corpus doc 523)	SOLO PLAY · SETUP · COURSE OF THE GAME	p.12	0.048131 (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 Bonfire — Rulebook (corpus doc 523)		p.2	0.047379 (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 Bonfire — Rulebook (corpus doc 523)		p.2	0.046394 (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 Bonfire — Rulebook (corpus doc 523)	PLAYER BOARDS	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
#5	RULEBOOK Bonfire — Rulebook (corpus doc 523)		p.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))	300
#6	RULEBOOK Bonfire — Rulebook (corpus doc 523)		p.2	0.030886 (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 Bonfire — Rulebook (corpus doc 523)	Move your ShIP	p.8	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 Bonfire — Rulebook (corpus doc 523)	GAME OVERVIEW · HOW DOES THE GAME PLAY? · WHAT CAN I DO ON MY TURN? · HOW DO I GAIN POINTS?	p.6	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 36 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 Bonfire — Rulebook (corpus doc 523)		p.2	#2	0.047379 (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 Bonfire — Rulebook (corpus doc 523)		p.2	#3	0.046394 (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 Bonfire — Rulebook (corpus doc 523)	GAME OVERVIEW · HOW DOES THE GAME PLAY? · WHAT CAN I DO ON MY TURN? · HOW DO I GAIN POINTS?	p.6	#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
#4	RULEBOOK Bonfire — Rulebook (corpus doc 523)	Tips for the first game:	p.6	#14	0.013514 (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 Bonfire — Rulebook (corpus doc 523)	PLAYER BOARDS	p.5	#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))	vector + the doc-priority boost arm	the re-ranker chose it
#6	RULEBOOK Bonfire — Rulebook (corpus doc 523)		p.2	#6	0.030886 (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
#7	RULEBOOK Bonfire — Rulebook (corpus doc 523)	SOLO PLAY · SETUP · COURSE OF THE GAME	p.12	#1	0.048131 (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
#8	RULEBOOK Bonfire — Rulebook (corpus doc 523)		p.4	#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))	vector + the doc-priority boost arm	the re-ranker chose it

chosen chunks — what the answer actually cited

#	document	heading	page	quote chars
[1]	RULEBOOK Bonfire — Rulebook (corpus doc 523)		p.4	no quote on the wire
[2]	RULEBOOK Bonfire — Rulebook (corpus doc 523)	PLAYER BOARDS	p.5	no quote on the wire
[3]	RULEBOOK Bonfire — Rulebook (corpus doc 523)	SOLO PLAY · SETUP · COURSE OF THE GAME	p.12	no quote on the wire

generation — timing and the path taken

timing split: retrieval 80 ms · first delta 3534 ms · total 10664 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 80 ms · ask 10582 ms · gateway work 10664 ms · total 10664 ms
tokens in (the prompt the answerer read): 2471
tokens out (what the answerer generated): 999
tok/sec: 140.8 tok/sec — 999 output tokens in 7.094 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 3s 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 454), 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.