RuleSage cited table rulings
← Dragon Eclipse

You asked

When does the game end?

Answered counted as answered

Asked with: Dragon Eclipsebg-381247-en-1e

The timing for the end of different game elements is as follows:
Combat
Combat ends immediately when one of the following three conditions is fulfilled:[1][2][3]
* LOSE: Your Mystling has as many or more of its [damage/health/etc.] than its [limit/threshold],[1][2][3] or if only one player's Mystling reaches this state.[2]
* WIN: The Enemy has as many or more of its [damage/health/etc.] than its [limit/threshold] and you did not fulfill all Taming conditions.[1][2][3]
* TAME: You fulfill all Taming conditions from the Taming card.[1][3]
* Additionally, a player may decide to concede a fight at any time.[3]
Exploration
Exploration ends when you encounter the 'end the Exploration' instruction, which can be found on an Event card, as part of the story in the Adventure Journal, or via a player choice.[4]
Scenario
A phase starts when you reach a Script in the Adventure Journal that says: 'Congratulations! You've reached the end of the Scenario'.[5]
Run (Roguelite Mode)
A Run ends when you:
* Lose a Run (one of your Mystlings has equal to or more than its [limit/threshold]).[6]
* Win a Run by defeating a 3rd Boss.[6]
* Decide to end the Run without saving.[6]
[1] RULEBOOK Dragon Eclipse — Rulebook · p.18 · Combat rules · Actions · Golden Rules of Combat
[2] RULEBOOK Dragon Eclipse — Rulebook · p.25
[3] RULEBOOK Dragon Eclipse — Rulebook · p.25 · End of Combat · LOSE · WIN · TAME · Conceding · After Lose/Tame/Win
[4] RULEBOOK Dragon Eclipse — Rulebook · p.13 · End of Exploration
[5] RULEBOOK Dragon Eclipse — Rulebook · p.26 · AFTER THE SCENARIO · 1. Gaining access to new Scenarios · 2. Opening Boosters · 3. Gaining Advancement cards
[6] RULEBOOK Dragon Eclipse — Rulebook · p.31 · Run Resolution · · Gain Essence: · Saving game (optional)

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 156 ms · ask 3310 ms · total 5790 ms
single-flight (PR-5)
queued 2321 ms · generation 3469 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read
[{"page": 31, "score": 0.047379, "snippet": "III When you lose a Run (i.e., one of your Mystlings has equal to or more than its ), win a Run by defeating a 3rd Boss, or decide to end the Run without saving, resolve the following steps: II · Discard all and locked Artifacts. Gain Silver: III -Take all Tier cards of the Mystlings you have defeat", "headingPath": "Run Resolution · · Gain Essence: · Saving game (optional)", "sharpsignalDocId": 1288}, {"page": 25, "score": 0.046751, "snippet": "Combat ends immediately when one of 3 conditions is fulfilled: If, at any moment, there are equal to or more on your Mystling sheet than the Mystling's , you immediately Lose the Combat. You may end Combat by defeating the Enemy. If at any moment there is equal to or more on the Enemy sheet than its", "headingPath": "End of Combat · LOSE · WIN · TAME · Conceding · After Lose/Tame/Win", "sharpsignalDocId": 1288}, {"page": 26, "score": 0.043817, "snippet": "This phase starts when you reach a Script in the Adventure Journal that says: ' Congratulations! You've reached the end of the Scenario.' The text that follows contains instructions on how to end a Scenario. The following steps are also listed in the Adventure Journal, so don't worry about rememberi", "headingPath": "AFTER THE SCENARIO · 1. Gaining access to new Scenarios · 2. Opening Boosters · 3. Gaining Advancement cards", "sharpsignalDocId": 1288}, {"page": 13, "score": 0.032787, "snippet": "The Exploration ends when you encounter the 'end the Exploration' instruction. You may find it on an Event card, as a part of the story in the Adventure Journal, and sometimes, you'll have a choice to end the Exploration on your own. When you end the Exploration, follow the steps below: Discard all ", "headingPath": "End of Exploration", "sharpsignalDocId": 1288}, {"page": 25, "score": 0.031746, "snippet": "25 End of/uni00A0Combat Combat ends immediately when one of/uni00A03 conditions is ful/f_illed: LOSE If, at any moment, there are equal to/uni00A0or more on your Mystling sheet than the/uni00A0Mystling’s , you immediately Lose the/uni00A0Combat. : If/uni00A0 only one of/uni00A0 the/uni00A0 players’ ", "headingPath": "", "sharpsignalDocId": 1288}, {"page": 25, "score": 0.030769, "snippet": "64A Young Emberling A/uni00A0T aming card. Conceding We do not recommend it, but you can also decide to/uni00A0concede a/uni00A0/f_ight at any time during the/uni00A0Combat. If/uni00A0you do, deal to/uni00A0your Mystling so that/uni00A0 their equals their , and resolve the/uni00A0 LOSE outcome. If/u", "headingPath": "", "sharpsignalDocId": 1288}, {"page": 22, "score": 0.029851, "snippet": "After the player's turn, it's time for the Enemy to act. : Remember that the turn order is different. First, it is the turn of the player with the Taunt token, then the other player, and finally the Enemy. After the Enemy turn, the player with the Taunt token has their turn, and so on. Enemies have ", "headingPath": "Enemy Turn", "sharpsignalDocId": 1288}, {"page": 27, "score": 0.029412, "snippet": "Not available during the Campaign. In the PvP mode you can challenge your friends to an epic duel. All Mystlings can compete with each other in PvP mode. Depending on how much time you have, you can choose to play the following: Quick battle (30-45 minutes). Challenge (90 minutes). Both Quick battle", "headingPath": "PvP mode · Quick battle", "sharpsignalDocId": 1288}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show
[{"page": 18, "quote": null, "headingPath": "Combat rules · Actions · Golden Rules of Combat", "sharpsignalDocId": 1288}, {"page": 25, "quote": null, "headingPath": "", "sharpsignalDocId": 1288}, {"page": 25, "quote": null, "headingPath": "End of Combat · LOSE · WIN · TAME · Conceding · After Lose/Tame/Win", "sharpsignalDocId": 1288}, {"page": 13, "quote": null, "headingPath": "End of Exploration", "sharpsignalDocId": 1288}, {"page": 26, "quote": null, "headingPath": "AFTER THE SCENARIO · 1. Gaining access to new Scenarios · 2. Opening Boosters · 3. Gaining Advancement cards", "sharpsignalDocId": 1288}, {"page": 31, "quote": null, "headingPath": "Run Resolution · · Gain Essence: · Saving game (optional)", "sharpsignalDocId": 1288}]
boost provenance — errata + base rulebook (E2/E3)
no registered errata card matched this query; base rulebook doc 1288 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 1288 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.85998 of 1007 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row recorded
Oct 24, 2026 20:07 UTC

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 rankdocumentheadingpage fused RRF scoresnippet chars
#1 RULEBOOK Dragon Eclipse — Rulebook (corpus doc 1288) Run Resolution · · Gain Essence: · Saving game (optional) p.31 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
#2 RULEBOOK Dragon Eclipse — Rulebook (corpus doc 1288) End of Combat · LOSE · WIN · TAME · Conceding · After Lose/Tame/Win p.25 0.046751 (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 Dragon Eclipse — Rulebook (corpus doc 1288) AFTER THE SCENARIO · 1. Gaining access to new Scenarios · 2. Opening Boosters · 3. Gaining Advancement cards p.26 0.043817 (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 Dragon Eclipse — Rulebook (corpus doc 1288) End of Exploration p.13 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 Dragon Eclipse — Rulebook (corpus doc 1288) p.25 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 Dragon Eclipse — Rulebook (corpus doc 1288) p.25 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 Dragon Eclipse — Rulebook (corpus doc 1288) Enemy Turn p.22 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
#8 RULEBOOK Dragon Eclipse — Rulebook (corpus doc 1288) PvP mode · Quick battle p.27 0.029412 (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 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 80 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 atdocumentheadingpage fused rankfused RRF scorecarried byhow it got its slot
#1 RULEBOOK Dragon Eclipse — Rulebook (corpus doc 1288) Combat rules · Actions · Golden Rules of Combat p.18 #19 0.014286 (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
#2 RULEBOOK Dragon Eclipse — Rulebook (corpus doc 1288) End of Exploration p.13 #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
#3 RULEBOOK Dragon Eclipse — Rulebook (corpus doc 1288) AFTER THE SCENARIO · 1. Gaining access to new Scenarios · 2. Opening Boosters · 3. Gaining Advancement cards p.26 #3 0.043817 (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
#4 RULEBOOK Dragon Eclipse — Rulebook (corpus doc 1288) p.25 #12 0.026857 (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 Dragon Eclipse — Rulebook (corpus doc 1288) Resuming a Saved Run · Shortcuts · Expansion compatibility p.31 #9 0.029214 (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 Dragon Eclipse — Rulebook (corpus doc 1288) Run Resolution · · Gain Essence: · Saving game (optional) p.31 #1 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
#7 RULEBOOK Dragon Eclipse — Rulebook (corpus doc 1288) p.25 #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
#8 RULEBOOK Dragon Eclipse — Rulebook (corpus doc 1288) End of Combat · LOSE · WIN · TAME · Conceding · After Lose/Tame/Win p.25 #2 0.046751 (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

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 Dragon Eclipse — Rulebook (corpus doc 1288) Combat rules · Actions · Golden Rules of Combat p.18 no quote on the wire
[2] RULEBOOK Dragon Eclipse — Rulebook (corpus doc 1288) p.25 no quote on the wire
[3] RULEBOOK Dragon Eclipse — Rulebook (corpus doc 1288) End of Combat · LOSE · WIN · TAME · Conceding · After Lose/Tame/Win p.25 no quote on the wire
[4] RULEBOOK Dragon Eclipse — Rulebook (corpus doc 1288) End of Exploration p.13 no quote on the wire
[5] RULEBOOK Dragon Eclipse — Rulebook (corpus doc 1288) AFTER THE SCENARIO · 1. Gaining access to new Scenarios · 2. Opening Boosters · 3. Gaining Advancement cards p.26 no quote on the wire
[6] RULEBOOK Dragon Eclipse — Rulebook (corpus doc 1288) Run Resolution · · Gain Essence: · Saving game (optional) p.31 no quote on the wire
timing split
retrieval 156 ms · first delta 1685 ms · total 5790 ms (retrieval and first-delta both measured from the START of gateway work, so first-delta INCLUDES retrieval — do not subtract)
full breakdown
queued 2321 ms · retrieval 156 ms · ask 3310 ms · gateway work 3469 ms · total 5790 ms
tokens in (the prompt the answerer read)
4654
tokens out (what the answerer generated)
341
tok/sec
199.5 tok/sec — 341 output tokens in 1.709 s of generation
live seat (read from the running child)
answering — gemma4:26b think:false · num_ctx 32768 (live-verified 56s ago)
gateway schema (read from the running child)
schema head 0042_definer_search_path (live revision not readable by this principal)
answerer host (measured by rulesage)
reachable (for 5h, checked 9s 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.
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 1218), 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.