Ruling — Blood Rage

You asked

How do I setup the game?

Answered counted as answered

Asked with: Blood Ragebg-170216-en-1e

To setup the game, follow these steps:

1. Separate the cards by their card backs to create three different decks: 1, 2, and 3.[1][2]

2. Depending on the number of players, remove specific cards marked with "3+" or "4+" to ensure balance: for a 4-player game, remove no cards; for a 3-player game, remove all 4+ cards; for a 2-player game, remove all 3+ and 4+ cards.[1][2]

3. Place any removed cards back in the game box.[1][2]

4. Shuffle each of the three decks separately and place them, face down, on the appropriate Gods’ Gifts spots of the Age Track.[1][2]

5. Place the Valhalla sheet and the Age Track sheet next to the Game Board.[3]

6. Place the Pillage token with the green border on the Yggdrasil province at the center of the board, with the reward side facing up.[3]

7. Shuffle the other 8 Pillage tokens and place them randomly on the other 8 provinces surrounding Yggdrasil, face up.[3]

8. Shuffle the 8 Ragnarök tokens and place one on each of the three Ragnarök spots on the Age Track, with the text side facing up.[3]

9. Place the Doom token on the province indicated by the Ragnarök token on the First Age track.[3]

10. Depending on the number of players, randomly take a specific number of Ragnarök tokens and place them on the indicated provinces with the 'destroyed' side facing up: 1 province for a 4-player game, 2 provinces for a 3-player game, and 3 provinces for a 2-player game; place any remaining Ragnarök tokens back in the box.[3]

11. Place all Monster figures next to the board, within reach of all players.[1]

12. Place the Saga token on the first spot of the First Age on the Story Track (the “Gods’ Gifts – Age 1” spot).[1]

13. Give the First Player token to the player who was born furthest to the north.[1]

14. Each player chooses a clan by placing a Clan Sheet in front of them.[4]

15. For each chosen clan, take the Leader figure, 8 Warrior figures (ensuring small plastic bases in the clan's color are attached), and one Ship figure (with a sail attached in the clan's color) and keep them in your reserve.[4]

16. Keep the clan's extra 2 small bases and 2 large bases next to you for recruiting Monsters.[4]

17. Place the clan's Glory Marker on the '0' spot of the Glory Track.[4]

18. Place one Clan Token on the first spot of each of the three Clan Stats (Rage, Axes, and Horns) on the clan sheet, such that the starting stats are 6 Rage, 3 Axes, and 4 Horns.[4]

19. Place the final Clan token on the '6' spot of the Rage Track on the clan sheet.[4]

[1] RULEBOOK Blood Rage — Rulebook · p.11

[2] RULEBOOK Blood Rage — Rulebook · p.11 · pRepaRe The CaRds

[3] RULEBOOK Blood Rage — Rulebook · p.10 · pRepaRe The bOaRd

[4] RULEBOOK Blood Rage — Rulebook · p.9 · pRepaRe YOuR Clan

The table has its answer — dice up.

🔧 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 300 ms · ask 5140 ms · total 5442 ms
single-flight (PR-5): queued 0 ms · generation 5442 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read: [{"page": 11, "score": 0.048652, "snippet": "pRepaRe The CaRds Separate the cards by their card backs, creating three dif- ferent decks: 1, 2, and 3. Depending on how many people are playing the game, some cards may need to be removed from each deck to make sure the game is balanced properly. The cards that may need to be removed show on the l", "headingPath": "", "sharpsignalDocId": 272}, {"page": 13, "score": 0.045285, "snippet": "This is the main part of the game, where invading and pillaging takes place, battles are fought, and blood is spilled. All players begin the Action phase with the amount of Rage indicated by the Rage stat on their clan sheet. If this is the first Age, you've already taken care of this by placing you", "headingPath": "aCTiOn phase", "sharpsignalDocId": 272}, {"page": 9, "score": 0.032787, "snippet": "First, each player chooses one of the available clans to play, by placing one of the Clan Sheets in front of them. At the start of the game, all clans are equal, but they'll soon become unique with each player's choice of upgrades. Take your clan's Leader figure and 8 Warrior figures, and make sure ", "headingPath": "pRepaRe YOuR Clan", "sharpsignalDocId": 272}, {"page": 11, "score": 0.031746, "snippet": "Separate the cards by their card backs, creating three different decks: 1, 2, and 3. Depending on how many people are playing the game, some cards may need to be removed from each deck to make sure the game is balanced properly. The cards that may need to be removed show on the left side a small num", "headingPath": "pRepaRe The CaRds", "sharpsignalDocId": 272}, {"page": 10, "score": 0.03125, "snippet": "Next to the Game Board , place the Valhalla sheet and the Age Track sheet. Take all the Pillage tokens and place the one with the green border on the Yggdrasil province at the center of the board, with the reward side facing up. Shuffle the other 8 Pillage tokens and place them randomly on the other", "headingPath": "pRepaRe The bOaRd", "sharpsignalDocId": 272}, {"page": 12, "score": 0.030769, "snippet": "Blood Rage is played over a series of three rounds, known as Ages. Each Age is divided into six phases: GODS' GIFTS ACTION DISCARD QUEST RAGNARÖK RELEASE VALHALLA The phases must be played in order, and a phase must be completely finished before moving to the next one. Move the Saga token on the Age", "headingPath": "pRepaRe The CaRds · GOds' GifTs phase · FIRST GAME?", "sharpsignalDocId": 272}, {"page": 17, "score": 0.030303, "snippet": "Once you have declared your intent to Pillage that province, the other players have a chance to join the battle. Starting with the player to your left and going around in clockwise order, each player (including you) may, if they wish, move one of their figures from an adjacent province into an empty", "headingPath": "1. CALL TO BATTLE", "sharpsignalDocId": 272}, {"page": 13, "score": 0.029851, "snippet": "Now each player looks at the cards they've been passed, selects one to keep, and places it face down on their clan sheet. Then everyone passes their remaining cards to the left. Continue picking and passing cards until each player has placed six new cards on their clan sheet. By that point, everyone", "headingPath": "FIRST GAME? · STRATEGY TIPS FOR DRAFTING · DRAFTING IN A 2-PLAYER GAME", "sharpsignalDocId": 272}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show: [{"page": 11, "quote": null, "headingPath": "", "sharpsignalDocId": 272}, {"page": 11, "quote": null, "headingPath": "pRepaRe The CaRds", "sharpsignalDocId": 272}, {"page": 10, "quote": null, "headingPath": "pRepaRe The bOaRd", "sharpsignalDocId": 272}, {"page": 9, "quote": null, "headingPath": "pRepaRe YOuR Clan", "sharpsignalDocId": 272}]
boost provenance — errata + base rulebook (E2/E3): no registered errata card matched this query; base rulebook doc 272 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 272 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.88501 of 2035 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row recorded: Aug 31, 2026 16:22 UTC

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 Blood Rage — Rulebook (corpus doc 272)		p.11	0.048652 (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 Blood Rage — Rulebook (corpus doc 272)	aCTiOn phase	p.13	0.045285 (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 Blood Rage — Rulebook (corpus doc 272)	pRepaRe YOuR Clan	p.9	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
#4	RULEBOOK Blood Rage — Rulebook (corpus doc 272)	pRepaRe The CaRds	p.11	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
#5	RULEBOOK Blood Rage — Rulebook (corpus doc 272)	pRepaRe The bOaRd	p.10	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
#6	RULEBOOK Blood Rage — Rulebook (corpus doc 272)	pRepaRe The CaRds · GOds' GifTs phase · FIRST GAME?	p.12	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
#7	RULEBOOK Blood Rage — Rulebook (corpus doc 272)	1. CALL TO BATTLE	p.17	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 Blood Rage — Rulebook (corpus doc 272)	FIRST GAME? · STRATEGY TIPS FOR DRAFTING · DRAFTING IN A 2-PLAYER GAME	p.13	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 28 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 Blood Rage — Rulebook (corpus doc 272)		p.11	#1	0.048652 (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 Blood Rage — Rulebook (corpus doc 272)	pRepaRe The CaRds	p.11	#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))	vector + the doc-priority boost arm	the re-ranker chose it
#3	RULEBOOK Blood Rage — Rulebook (corpus doc 272)	FIRST GAME? · STRATEGY TIPS FOR DRAFTING · DRAFTING IN A 2-PLAYER GAME	p.13	#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 Blood Rage — Rulebook (corpus doc 272)	pRepaRe The bOaRd	p.10	#5	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
#5	RULEBOOK Blood Rage — Rulebook (corpus doc 272)	1. CALL TO BATTLE	p.17	#7	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))	vector + the doc-priority boost arm	the re-ranker chose it
#6	RULEBOOK Blood Rage — Rulebook (corpus doc 272)	pRepaRe The CaRds · GOds' GifTs phase · FIRST GAME?	p.12	#6	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
#7	RULEBOOK Blood Rage — Rulebook (corpus doc 272)	pRepaRe YOuR Clan	p.9	#3	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
#8	RULEBOOK Blood Rage — Rulebook (corpus doc 272)	aCTiOn phase	p.13	#2	0.045285 (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

chosen chunks — what the answer actually cited

#	document	heading	page	quote chars
[1]	RULEBOOK Blood Rage — Rulebook (corpus doc 272)		p.11	no quote on the wire
[2]	RULEBOOK Blood Rage — Rulebook (corpus doc 272)	pRepaRe The CaRds	p.11	no quote on the wire
[3]	RULEBOOK Blood Rage — Rulebook (corpus doc 272)	pRepaRe The bOaRd	p.10	no quote on the wire
[4]	RULEBOOK Blood Rage — Rulebook (corpus doc 272)	pRepaRe YOuR Clan	p.9	no quote on the wire

generation — timing and the path taken

timing split: retrieval 300 ms · first delta 1943 ms · total 5442 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 300 ms · ask 5140 ms · gateway work 5442 ms · total 5442 ms
tokens in (the prompt the answerer read): 2978
tokens out (what the answerer generated): 695
tok/sec: 202.2 tok/sec — 695 output tokens in 3.438 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 42s ago)
answerer host (measured by rulesage): reachable (for 22h, checked 1s ago)
answerer node (the seat proxy's own header — this probe, not this ask): node1
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 200), 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.