RuleSage cited table rulings
← Magic: The Gathering

You asked

When does the game end?

Answered counted as answered
A game ends immediately when:
- A player wins [1][2]
- The game is a draw [1][2]
- The game is restarted [1][2]
- A player is reduced to 0 life [3]
[1] RULEBOOK Magic: The Gathering — Comprehensive Rules (2026-06-19) · p.10 · 103. Starting the Game
[2] RULEBOOK Magic: The Gathering — Comprehensive Rules (2026-06-19) · p.10 · 103. Starting the Game
[3] RULEBOOK Magic: The Gathering — Magic 2014 Starter Rulebook · p.18 · T N T
🔧 debug — where this ruling came from
outcome
ANSWERED — Answered
corpus profile
live
answerer pin (deploy-frozen, attribution only)
gemma4:26b think:false 5571076f3d70
timings
search 297 ms · ask 15286 ms · total 15595 ms
single-flight (PR-5)
queued 0 ms · generation 15595 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read
[{"page": 10, "score": 0.032258, "snippet": "103.8b In a Two-Headed Giant game, the team who plays first skips the draw step of their first turn. 103.8c In all other multiplayer games, no player skips the draw step of their first turn. Ending the Game 104.1. A game ends immediately when a player wins, when the game is a draw, or when the game ", "headingPath": "103. Starting the Game", "sharpsignalDocId": 172}, {"page": 18, "score": 0.031778, "snippet": "Now it's your opponent's turn. That player untaps his or her permanents and goes from there. After that player is done, it will be your turn again. Keep going until a player is reduced to 0 life. As soon as a player has 0 life, the game ends immediately and the other player wins! UB02_M14", "headingPath": "T N T", "sharpsignalDocId": 163}, {"page": 10, "score": 0.031319, "snippet": "103.5d In a multiplayer game using the shared team turns option, first each player on the starting team declares whether that player will take a mulligan, then the players on each other team in turn order do the same. Teammates may consult while making their decisions. Then all mulligans are taken a", "headingPath": "103. Starting the Game", "sharpsignalDocId": 172}, {"page": 11, "score": 0.030777, "snippet": "104.3a A player can concede the game at any time. A player who concedes leaves the game immediately. That player loses the game. 104.3b If a player's life total is 0 or less, that player loses the game the next time a player would receive priority. (This is a state-based action. See rule 704.) 104.3", "headingPath": "103. Starting the Game", "sharpsignalDocId": 172}, {"page": 10, "score": 0.028259, "snippet": "When a spell resolves, one of two things happens. If the spell is an instant or sorcery, it has its effect (in other words, you follow the instructions on the card), then you put the card into your graveyard. If the spell is a creature, artifact, enchantment, or planeswalker, you put the card on the", "headingPath": "R  S", "sharpsignalDocId": 163}, {"page": 24, "score": 0.028205, "snippet": "To stop playing a game and give your opponent the victory. You can concede a game at any time (usually if you realize you won't be able to avoid losing). When you concede, you lose the game. A group of play formats that use decks you build in advance. A Constructed deck must have at least 60 cards, ", "headingPath": "C · C · C  · C · C · C  ", "sharpsignalDocId": 163}, {"page": 36, "score": 0.027151, "snippet": "119.1. Each player begins the game with a starting life total of 20. Some variant games have different starting life totals. 119.1a In a Two-Headed Giant game, each team's starting life total is 30. See rule 810, 'TwoHeaded Giant Variant.' 119.1b In a Vanguard game, each player's starting life total", "headingPath": "119. Life", "sharpsignalDocId": 172}, {"page": 36, "score": 0.026743, "snippet": "119.4b Players can always pay 0 life, no matter what their (or their team's) life total is, and even if an effect says players can't pay life. 119.5. If an effect sets a player's life total to a specific number, the player gains or loses the necessary amount of life to end up with the new total. 119", "headingPath": "119. Life", "sharpsignalDocId": 172}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show
[{"page": 10, "quote": null, "headingPath": "103. Starting the Game", "sharpsignalDocId": 172}, {"page": 10, "quote": null, "headingPath": "103. Starting the Game", "sharpsignalDocId": 172}, {"page": 18, "quote": null, "headingPath": "T N T", "sharpsignalDocId": 163}]
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
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
Oct 31, 2026 20:40

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 rankdocumentheadingpage fused RRF scoresnippet chars
#1 RULEBOOK Magic: The Gathering — Comprehensive Rules (2026-06-19) (corpus doc 172) 103. Starting the Game p.10 0.032258 (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 Magic: The Gathering — Magic 2014 Starter Rulebook (corpus doc 163) T N T p.18 0.031778 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded)) 289
#3 RULEBOOK Magic: The Gathering — Comprehensive Rules (2026-06-19) (corpus doc 172) 103. Starting the Game p.10 0.031319 (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 Magic: The Gathering — Comprehensive Rules (2026-06-19) (corpus doc 172) 103. Starting the Game p.11 0.030777 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded)) 300
#5 RULEBOOK Magic: The Gathering — Magic 2014 Starter Rulebook (corpus doc 163) R  S p.10 0.028259 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded)) 300
#6 RULEBOOK Magic: The Gathering — Magic 2014 Starter Rulebook (corpus doc 163) C · C · C  · C · C · C   p.24 0.028205 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded)) 300
#7 RULEBOOK Magic: The Gathering — Comprehensive Rules (2026-06-19) (corpus doc 172) 119. Life p.36 0.027151 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded)) 300
#8 RULEBOOK Magic: The Gathering — Comprehensive Rules (2026-06-19) (corpus doc 172) 119. Life p.36 0.026743 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded)) 300

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.

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.

#documentheadingpagequote chars
[1] RULEBOOK Magic: The Gathering — Comprehensive Rules (2026-06-19) (corpus doc 172) 103. Starting the Game p.10 no quote on the wire
[2] RULEBOOK Magic: The Gathering — Comprehensive Rules (2026-06-19) (corpus doc 172) 103. Starting the Game p.10 no quote on the wire
[3] RULEBOOK Magic: The Gathering — Magic 2014 Starter Rulebook (corpus doc 163) T N T p.18 no quote on the wire
timing split
retrieval 297 ms · first delta 15168 ms · total 15595 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 297 ms · ask 15286 ms · gateway work 15595 ms · total 15595 ms
tokens in (the prompt the answerer read)
3228
tokens out (what the answerer generated)
56
tok/sec
149.3 tok/sec — 56 output tokens in 0.375 s of generation
live seat (read from the running child)
answering — gemma4:26b think:false · num_ctx 32768 (live-verified 27s 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.
outcome
ANSWERED — Answered
abstain rationale (n/a — this ruling answered)
answered — no abstain rationale applies
decision
NOT_SETUP_SHAPED — no setup-shape pattern matched this question

this game registers NO errata cards (edition 85), 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.