Ruling — Blood Bowl: Team Manager – The Card Game

← Blood Bowl: Team Manager – The Card Game

You asked

How do I play?

Answered counted as answered

Asked with: Blood Bowl: Team Manager – The Card Gamebg-90137-en-1e

To play, follow these steps during the Matchup phase:

1. Beginning with the first manager and proceeding clockwise, each manager performs the following steps during his turn: [1]

2. Commit One Player to a Matchup: The manager takes one Player card from his hand and places it faceup next to a matchup.[1]

3. Resolve When Played Abilities: The manager resolves any 'When Played:' abilities on that Player card.[1]

4. Use Skills: The manager uses the player's skills in order from left-to-right.[1]

5. Resolve One Matchup Action (optional): The manager may exhaust one Staff Upgrade or Team Upgrade card in his play area and apply the card's text.[1]

[1] RULEBOOK Blood Bowl: Team Manager – The Card Game — Rulebook · p.8 · Matchup Phase · Types of Matchups

🔧 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 103 ms · ask 3775 ms · total 3885 ms
single-flight (PR-5): queued 0 ms · generation 3885 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read: [{"page": 8, "score": 0.048387, "snippet": "The Matchup phase is the heart of the game experience. During this phase, teams compete against other teams in head-to-head matchups. Generally speaking, the more matchups a team wins, the more it improves and the more fans it accumulates. Each manager typically has six turns over the course of the ", "headingPath": "Matchup Phase · Types of Matchups", "sharpsignalDocId": 487}, {"page": 20, "score": 0.046239, "snippet": "Refresh Cards Replenish Hand Restock the Cheating Token Pool Reveal the Spike! Magazine Card Roll the Highlights Prepare for Kickoff Commit One Player to a Matchup or Pass (mandatory) Resolve When Played Abilities Use Skills Resolve One Matchup Action (optional) Resolve Matchups Reveal Cheating Toke", "headingPath": "The Maintenance Phase · The Matchup phase · The Scoreboard Phase · Cheating Token Quantities · Cheating (mandatory) · Passing (optional) · …", "sharpsignalDocId": 487}, {"page": 1, "score": 0.045009, "snippet": "Rules of Play", "headingPath": "", "sharpsignalDocId": 487}, {"page": 10, "score": 0.044468, "snippet": "When a manager commits a player to a highlight, he is guaranteed to collect his team zone's payout (as long as he has players there during the Scoreboard phase; see 'Payout Sections' on page 15). The manager also has a chance to beat the opposing manager and win the central payout , shown between th", "headingPath": "Committing Players to a Highlight · Committing Players to a Tournament · 'When Played' Abilities · Skills", "sharpsignalDocId": 487}, {"page": 11, "score": 0.032787, "snippet": "A player can be in three possible states: standing , downed , and injured . Standing: When a manager commits a player to a highlight, he places the Player card perpendicular to the Highlight card in an upright position in his team zone. This position indicates that he is standing. While a player is ", "headingPath": "Player States · Resolving Matchup actions", "sharpsignalDocId": 487}, {"page": 10, "score": 0.03125, "snippet": "Cheating is mandatory . For each cheating icon, assign the player one cheating token. To assign a cheating token, draw one random cheating token from the pool and place it facedown (skull side up) on the Player card without looking at it . Cheating tokens are revealed and resolved during the Scorebo", "headingPath": "Cheating · Passing", "sharpsignalDocId": 487}, {"page": 4, "score": 0.030282, "snippet": "4 These tokens identify Star Players who belong to a team not of their race. This helps avoid confusion during the game. These tokens determine how cheating players are rewarded or punished for their shenanigans. Sometimes cheating can increase a player's Star Power or even gain fans for the team. B", "headingPath": "Staff Upgrade Cards · Team Tokens · Cheating Tokens · Ball Tokens · Golden Coin Marker · Scoreboards · …", "sharpsignalDocId": 487}, {"page": 5, "score": 0.029877, "snippet": "sPike! magazine Deck revealeD sPike! magazine carD tHe HigHligHt reel HigHligHt Deck Prepare the Staff Upgrade Deck: Shuffle all Staff Upgrade cards and place them facedown near the Highlight deck. Prepare the Spike! Magazine Deck: Follow these four steps: cHeating token Pool cWc star Player Deck st", "headingPath": "Setup Diagram (4-manager game)", "sharpsignalDocId": 487}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show: [{"page": 8, "quote": null, "headingPath": "Matchup Phase · Types of Matchups", "sharpsignalDocId": 487}]
boost provenance — errata + base rulebook (E2/E3): no registered errata card matched this query; base rulebook doc 487 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 487 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.91513 of 542 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row retained until: Nov 15, 2026 13:08

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 Bowl: Team Manager – The Card Game — Rulebook (corpus doc 487)	Matchup Phase · Types of Matchups	p.8	0.048387 (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 Bowl: Team Manager – The Card Game — Rulebook (corpus doc 487)	The Maintenance Phase · The Matchup phase · The Scoreboard Phase · Cheating Token Quantities · Cheating (mandatory) · Passing (optional) · …	p.20	0.046239 (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 Bowl: Team Manager – The Card Game — Rulebook (corpus doc 487)		p.1	0.045009 (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))	13
#4	RULEBOOK Blood Bowl: Team Manager – The Card Game — Rulebook (corpus doc 487)	Committing Players to a Highlight · Committing Players to a Tournament · 'When Played' Abilities · Skills	p.10	0.044468 (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 Bowl: Team Manager – The Card Game — Rulebook (corpus doc 487)	Player States · Resolving Matchup actions	p.11	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
#6	RULEBOOK Blood Bowl: Team Manager – The Card Game — Rulebook (corpus doc 487)	Cheating · Passing	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
#7	RULEBOOK Blood Bowl: Team Manager – The Card Game — Rulebook (corpus doc 487)	Staff Upgrade Cards · Team Tokens · Cheating Tokens · Ball Tokens · Golden Coin Marker · Scoreboards · …	p.4	0.030282 (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 Bowl: Team Manager – The Card Game — Rulebook (corpus doc 487)	Setup Diagram (4-manager game)	p.5	0.029877 (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 34 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 Bowl: Team Manager – The Card Game — Rulebook (corpus doc 487)		p.1	#3	0.045009 (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 Bowl: Team Manager – The Card Game — Rulebook (corpus doc 487)	List of Named Abilities	p.17	#18	0.026501 (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
#3	RULEBOOK Blood Bowl: Team Manager – The Card Game — Rulebook (corpus doc 487)	Cheating · Passing	p.10	#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))	vector + the doc-priority boost arm	the re-ranker chose it
#4	RULEBOOK Blood Bowl: Team Manager – The Card Game — Rulebook (corpus doc 487)	Setup Diagram (4-manager game)	p.5	#8	0.029877 (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
#5	RULEBOOK Blood Bowl: Team Manager – The Card Game — Rulebook (corpus doc 487)	The Teams	p.7	#11	0.028531 (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
#6	RULEBOOK Blood Bowl: Team Manager – The Card Game — Rulebook (corpus doc 487)	Matchup Phase · Types of Matchups	p.8	#1	0.048387 (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
#7	RULEBOOK Blood Bowl: Team Manager – The Card Game — Rulebook (corpus doc 487)	Committing Players to a Highlight · Committing Players to a Tournament · 'When Played' Abilities · Skills	p.10	#4	0.044468 (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 Blood Bowl: Team Manager – The Card Game — Rulebook (corpus doc 487)	Player States · Resolving Matchup actions	p.11	#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))	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 Blood Bowl: Team Manager – The Card Game — Rulebook (corpus doc 487)	Matchup Phase · Types of Matchups	p.8	no quote on the wire

generation — timing and the path taken

timing split: retrieval 103 ms · first delta 3086 ms · total 3885 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 103 ms · ask 3775 ms · gateway work 3885 ms · total 3885 ms
tokens in (the prompt the answerer read): 2856
tokens out (what the answerer generated): 155
tok/sec: 206.4 tok/sec — 155 output tokens in 0.751 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 35s 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: 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 418), 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.