Ruling — Mythic Battles: Pantheon

← Mythic Battles: Pantheon

You asked

How do I take my turn?

Answered counted as answered

Asked with: Mythic Battles: Pantheonbg-186751-en-1e

A turn consists of the following phases:

1. **Start of Turn Phase**:

1.a: Effects of powers triggered during the previous turn of the active player that only last for one round, end.[1]

1.b: The active player draws 1 card from their deck.[1]

1.c: If the player passes their turn, they can draw another card and go directly to the end of turn phase.[1]

2. **Activate a Unit Phase**:

2.a: The active player discards 1 activation card of the unit they wish to activate and declares if the unit will carry out simple actions or one complex action.[1]

2.b: Any powers triggered at the start of the unit's activation are resolved.[1]

2.c: The unit is activated and can carry out 0, 1, or 2 simple actions, and 0 or 1 complex action.[1]

2.d: Any powers triggered at the end of the unit's activation are resolved.[1]

3. **Activate Another Unit Phase**:

3.a: If the active player has activated a number of units equal to their activation limit or no longer wishes to activate another unit, they go directly to the end of turn phase.[1]

3.b: If the active player chooses to activate another unit, they discard 1 AoW card and return to the activate a unit phase.[1]

4. **End of Turn Phase**:

4.a: The active player decides whether or not to discard 1 AoW card to perform a troop recall.[1]

4.b: The next player in a clockwise direction becomes the new active player.[1]

[1] RULEBOOK Mythic Battles: Pantheon — Rulebook · p.13 · VII · PLAYING THE GAME · A · TURN SEQUENCE · 1  START OF TURN PHASE · 2  ACTIVATE A UNIT PHASE · 3  ACTIVATE ANOTHER UNIT PHASE · 4  END OF TURN PHASE · …

Rule found, game on.

🔧 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 84 ms · ask 8240 ms · total 8326 ms
single-flight (PR-5): queued 0 ms · generation 8326 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read: [{"page": 13, "score": 0.048916, "snippet": "Mythic Battles is played in a series of rounds. During each round, each player takes a turn. The round starts with the lead player's turn, and continues clockwise around the table. Each turn consists of the following phases as described below. The player, whose turn it currently is, is known as the ", "headingPath": "VII · PLAYING THE GAME · A · TURN SEQUENCE · 1  START OF TURN PHASE · 2  ACTIVATE A UNIT PHASE · 3  ACTIVATE ANOTHER UNIT PHASE · 4  END OF TURN PHASE · …", "sharpsignalDocId": 579}, {"page": 39, "score": 0.032258, "snippet": "8, 9, 11, 12, 13, 16, 19, 20, 21, 22, 25, 27 , 28 turn ..............................10, 11, 12, 13, 16, 19, 20, 22, 26, 28 U unclaimed (divine stone) ..............................................19 unit ......................................6, 7, 8, 9, 10, 11, 12, 13, 14, 15, .....................", "headingPath": "", "sharpsignalDocId": 579}, {"page": 14, "score": 0.031746, "snippet": "All players refresh their decks, using the following steps: 1  Each player adds their entire remaining deck to their hand. 2  Each player shuffles their discard pile to form a new deck. 3  If necessary, each player draws a card (or cards) in order to have a hand of 3 cards. 4  Play resumes from ", "headingPath": "D · DECK · VIII · ACTIONS · A · SIMPLE ACTIONS · 1 · walk · 2 · attack · a · NORMAL ATTACK · …", "sharpsignalDocId": 579}, {"page": 12, "score": 0.03125, "snippet": "During setup, regardless of game mode, the table is set up using the following steps: 1  Place the selected board in the center of the table. Add any 3D terrain elements, divine stones, tokens, and miniatures indicated on the scenario map. If the exact location of the 3D terrain elements is not sce", "headingPath": "D · TABLE SETUP · E · TEAM PLAY", "sharpsignalDocId": 579}, {"page": 13, "score": 0.030769, "snippet": "DISCARD: players discard their cards face up in a pile to form their discard pile. This pile may be looked at by any player at any time during gameplay. DECK RUN OUT: The game pauses when a player can no longer draw a card because their deck has run out.", "headingPath": "D · DECK", "sharpsignalDocId": 579}, {"page": 19, "score": 0.030366, "snippet": "a unit can drop a claimed divine stone in their area at any moment during their activation. Dropping a divine stone is not an action. Once dropped, it is then considered unclaimed. Some game elements are treated in the same way as omphalos or divine stones. Whenever a rule or effect indicates that a", "headingPath": "droppIng a dIvIne stone: · effect of an omphalos:", "sharpsignalDocId": 579}, {"page": 28, "score": 0.030303, "snippet": "A power can only be used by a unit if it is available; that is, if its icon (or a number on a background of the same color) appears in the window of the dashboard's stat slide. The powers of troop units are always available. A player must pay the cost of the power in AoW cards in order to apply its ", "headingPath": "C · USING POWERS · permanent · passIve · actIve · offensIve", "sharpsignalDocId": 579}, {"page": 11, "score": 0.029907, "snippet": "Each scenario dictates the type of recruitment process to use: draft or limited .  DRAFT: Recruitment points (RP) value is player number dependant and is scenario-dictated. Selection and counter selection occurs.  LIMITED: Each player's army is scenario-dictated. Players jointly arrange all the ga", "headingPath": "2 · recruItment · 3 · table setup · 4 · startIng the game · 1 · draft", "sharpsignalDocId": 579}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show: [{"page": 13, "quote": null, "headingPath": "VII · PLAYING THE GAME · A · TURN SEQUENCE · 1  START OF TURN PHASE · 2  ACTIVATE A UNIT PHASE · 3  ACTIVATE ANOTHER UNIT PHASE · 4  END OF TURN PHASE · …", "sharpsignalDocId": 579}]
boost provenance — errata + base rulebook (E2/E3): no registered errata card matched this query; base rulebook doc 579 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 579 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.88909 of 1118 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row retained until: Nov 23, 2026 12:41 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 Mythic Battles: Pantheon — Rulebook (corpus doc 579)	VII · PLAYING THE GAME · A · TURN SEQUENCE · 1  START OF TURN PHASE · 2  ACTIVATE A UNIT PHASE · 3  ACTIVATE ANOTHER UNIT PHASE · 4  END OF TURN PHASE · …	p.13	0.048916 (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 Mythic Battles: Pantheon — Rulebook (corpus doc 579)		p.39	0.032258 (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 Mythic Battles: Pantheon — Rulebook (corpus doc 579)	D · DECK · VIII · ACTIONS · A · SIMPLE ACTIONS · 1 · walk · 2 · attack · a · NORMAL ATTACK · …	p.14	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
#4	RULEBOOK Mythic Battles: Pantheon — Rulebook (corpus doc 579)	D · TABLE SETUP · E · TEAM PLAY	p.12	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
#5	RULEBOOK Mythic Battles: Pantheon — Rulebook (corpus doc 579)	D · DECK	p.13	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))	254
#6	RULEBOOK Mythic Battles: Pantheon — Rulebook (corpus doc 579)	droppIng a dIvIne stone: · effect of an omphalos:	p.19	0.030366 (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 Mythic Battles: Pantheon — Rulebook (corpus doc 579)	C · USING POWERS · permanent · passIve · actIve · offensIve	p.28	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 Mythic Battles: Pantheon — Rulebook (corpus doc 579)	2 · recruItment · 3 · table setup · 4 · startIng the game · 1 · draft	p.11	0.029907 (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 64 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 Mythic Battles: Pantheon — Rulebook (corpus doc 579)	VII · PLAYING THE GAME · A · TURN SEQUENCE · 1  START OF TURN PHASE · 2  ACTIVATE A UNIT PHASE · 3  ACTIVATE ANOTHER UNIT PHASE · 4  END OF TURN PHASE · …	p.13	#1	0.048916 (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 Mythic Battles: Pantheon — Rulebook (corpus doc 579)	droppIng a dIvIne stone: · effect of an omphalos:	p.19	#6	0.030366 (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 Mythic Battles: Pantheon — Rulebook (corpus doc 579)		p.39	#2	0.032258 (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 Mythic Battles: Pantheon — Rulebook (corpus doc 579)	· open ground · · polar · rIft · rock · · ruIns · · swamp (aquatIc) · …	p.22	#47	0.009346 (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 Mythic Battles: Pantheon — Rulebook (corpus doc 579)	D · DECK · VIII · ACTIONS · A · SIMPLE ACTIONS · 1 · walk · 2 · attack · a · NORMAL ATTACK · …	p.14	#3	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
#6	RULEBOOK Mythic Battles: Pantheon — Rulebook (corpus doc 579)		p.39	#9	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
#7	RULEBOOK Mythic Battles: Pantheon — Rulebook (corpus doc 579)	leader · mIghty throw · mobIlIty · monster slayer · phalanx · sneak attack	p.26	#11	0.028958 (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
#8	RULEBOOK Mythic Battles: Pantheon — Rulebook (corpus doc 579)	D · TABLE SETUP · E · TEAM PLAY	p.12	#4	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

chosen chunks — what the answer actually cited

#	document	heading	page	quote chars
[1]	RULEBOOK Mythic Battles: Pantheon — Rulebook (corpus doc 579)	VII · PLAYING THE GAME · A · TURN SEQUENCE · 1  START OF TURN PHASE · 2  ACTIVATE A UNIT PHASE · 3  ACTIVATE ANOTHER UNIT PHASE · 4  END OF TURN PHASE · …	p.13	no quote on the wire

generation — timing and the path taken

timing split: retrieval 84 ms · first delta 5461 ms · total 8326 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 84 ms · ask 8240 ms · gateway work 8326 ms · total 8326 ms
tokens in (the prompt the answerer read): 3887
tokens out (what the answerer generated): 370
tok/sec: 132.7 tok/sec — 370 output tokens in 2.789 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 47s 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 60h, checked 4s 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: 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 511), 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.