Ruling — Mythic Battles: Pantheon

You asked

How do I play?

Answered counted as answered

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

The game is played in a series of rounds, with each player taking a turn starting with the lead player and continuing clockwise around the table.[1]

**Setup**

1. Place the selected board in the center of the table.[2]

2. Add any 3D terrain elements, divine stones, tokens, and miniatures indicated on the scenario map; if the exact location of 3D terrain elements is not scenario-dictated, place them according to the description of the corresponding terrain type.[2]

3. Place the dice, the AoW card deck, and the omphalos card deck next to the board.[2]

4. Each player places their miniatures, dashboards, troop cards, and unit tokens in front of them.[2]

5. Starting with the lead player and moving clockwise, each player in turn places a troop unit on one of the deployment areas until all players have placed all their troop units on the board.[2]

6. Each player builds their deck from all the activation cards for every unit in their army and a number of AoW cards equal to the total of all the strategic values of their units.[2]

7. Each player forms their hand with 3 additional AoW cards, the first 3 cards from their deck, and any AoW cards gained during recruitment if they were no longer able to recruit.[2]

**Turn Sequence**

Each 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, or 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 to the end of turn phase.[1]

* 3.b: If the 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]

**Unit Actions**

There are 6 actions divided into two types: simple and complex.[3] Simple actions include walk, attack, and claim.[3]

* **Walk**: A unit may enter a number of areas equal to its movement stat, provided each new area is adjacent to the previous one and the terrain/boundary types allow it.[3] A unit's walk ends upon entering an area containing enemy units.[3]

* **Attack**: There are two types: normal and area attacks.[3] A normal attack follows a sequence of target choice, attack resolution, and retaliation.[3] An attacker can target enemy units that are visible and within range, or units in an adjacent full area.[3]

* **Restrictions**: For simple actions, the two actions must be different, each must be completed before the next begins, and if a unit attacks, it cannot walk away during the same activation.[3]

**Other Rules**

* **Discarding**: Players discard cards face up in a pile; this pile can be viewed by any player at any time.[4]

* **Deck Run Out**: The game pauses when a player can no longer draw a card because their deck has run out.[4]

* **Refreshing Decks**: To refresh, players add their remaining deck to their hand, shuffle their discard pile to form a new deck, and draw cards to reach a hand of 3.[3]

* **Troop Recall**: When recalling a troop, the player chooses a controlled unit (in play or destroyed) and moves all its miniatures to the area of their divinity; any divine stones are dropped in the original area, and any tokens on the unit are removed

[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 · …

[2] RULEBOOK Mythic Battles: Pantheon — Rulebook · p.12 · D · TABLE SETUP · E · TEAM PLAY

[3] RULEBOOK Mythic Battles: Pantheon — Rulebook · p.14 · D · DECK · VIII · ACTIONS · A · SIMPLE ACTIONS · 1 · walk · 2 · attack · a · NORMAL ATTACK · …

[4] RULEBOOK Mythic Battles: Pantheon — Rulebook · p.13 · D · DECK

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 216 ms · ask 13175 ms · total 13395 ms
single-flight (PR-5): queued 0 ms · generation 13395 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read: [{"page": 12, "score": 0.04918, "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.047875, "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": 10, "score": 0.046642, "snippet": "Each unit has their own set of identical activation cards. An activation card only lists the unit's name, the associated artwork and the number of activation cards it has. These cards allow units to be activated during the game. These cards are all identical. They allow the players to pay for additi", "headingPath": " ACTIVATION CARDS  ·  ART OF WAR (AOW) CARDS  ·  OMPHALOS  · VI · GAME SETUP · A · SKIRMISH · 1 · recruItment type choIce · …", "sharpsignalDocId": 579}, {"page": 10, "score": 0.045772, "snippet": "If players decide to play in adventure mode, follow the steps below: Players select a scenario together, ensuring the scenariorecommended number of players is taken into account.", "headingPath": "B · ADVENTURE · 1 · scenarIo choIce", "sharpsignalDocId": 579}, {"page": 11, "score": 0.045688, "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}, {"page": 14, "score": 0.044408, "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": 11, "score": 0.043184, "snippet": "Constructed allows the recruitment of units from all players' available units. The number of players determines the number of RP available for each player to spend on their army:  2 players  18 RP  3 players  16 RP  4 players  14 RP Players must jointly decide on the type of divinity they wish", "headingPath": "2 · constructed · 3 · lImIted", "sharpsignalDocId": 579}, {"page": 13, "score": 0.029412, "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}]
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}, {"page": 12, "quote": null, "headingPath": "D · TABLE SETUP · E · TEAM PLAY", "sharpsignalDocId": 579}, {"page": 14, "quote": null, "headingPath": "D · DECK · VIII · ACTIONS · A · SIMPLE ACTIONS · 1 · walk · 2 · attack · a · NORMAL ATTACK · …", "sharpsignalDocId": 579}, {"page": 13, "quote": null, "headingPath": "D · DECK", "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.90366 of 3384 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row retained until: Nov 23, 2026 12:40 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)	D · TABLE SETUP · E · TEAM PLAY	p.12	0.04918 (at the 3-arm ceiling (0.04918) — every arm ranked it #1)	300
#2	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.047875 (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)	 ACTIVATION CARDS  ·  ART OF WAR (AOW) CARDS  ·  OMPHALOS  · VI · GAME SETUP · A · SKIRMISH · 1 · recruItment type choIce · …	p.10	0.046642 (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)	B · ADVENTURE · 1 · scenarIo choIce	p.10	0.045772 (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))	178
#5	RULEBOOK Mythic Battles: Pantheon — Rulebook (corpus doc 579)	2 · recruItment · 3 · table setup · 4 · startIng the game · 1 · draft	p.11	0.045688 (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 Mythic Battles: Pantheon — Rulebook (corpus doc 579)	D · DECK · VIII · ACTIONS · A · SIMPLE ACTIONS · 1 · walk · 2 · attack · a · NORMAL ATTACK · …	p.14	0.044408 (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)	2 · constructed · 3 · lImIted	p.11	0.043184 (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)	D · DECK	p.13	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))	254

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)	D · TABLE SETUP · E · TEAM PLAY	p.12	#1	0.04918 (at the 3-arm ceiling (0.04918) — every arm ranked it #1)	vector + full-text + the doc-priority boost arm	the re-ranker chose it
#2	RULEBOOK Mythic Battles: Pantheon — Rulebook (corpus doc 579)	B · ADVENTURE · 1 · scenarIo choIce	p.10	#4	0.045772 (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
#3	RULEBOOK Mythic Battles: Pantheon — Rulebook (corpus doc 579)	D · DECK	p.13	#8	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))	vector + the doc-priority boost arm	the re-ranker chose it
#4	RULEBOOK Mythic Battles: Pantheon — Rulebook (corpus doc 579)	2 · constructed · 3 · lImIted	p.11	#7	0.043184 (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
#5	RULEBOOK Mythic Battles: Pantheon — Rulebook (corpus doc 579)	D · POWER TOKENS	p.28	#10	0.028439 (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 Mythic Battles: Pantheon — Rulebook (corpus doc 579)	2 · recruItment · 3 · table setup · 4 · startIng the game · 1 · draft	p.11	#5	0.045688 (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 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	#2	0.047875 (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 Mythic Battles: Pantheon — Rulebook (corpus doc 579)	D · DECK · VIII · ACTIONS · A · SIMPLE ACTIONS · 1 · walk · 2 · attack · a · NORMAL ATTACK · …	p.14	#6	0.044408 (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 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
[2]	RULEBOOK Mythic Battles: Pantheon — Rulebook (corpus doc 579)	D · TABLE SETUP · E · TEAM PLAY	p.12	no quote on the wire
[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	no quote on the wire
[4]	RULEBOOK Mythic Battles: Pantheon — Rulebook (corpus doc 579)	D · DECK	p.13	no quote on the wire

generation — timing and the path taken

timing split: retrieval 216 ms · first delta 5650 ms · total 13395 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 216 ms · ask 13175 ms · gateway work 13395 ms · total 13395 ms
tokens in (the prompt the answerer read): 3439
tokens out (what the answerer generated): 1024
tok/sec: 133.3 tok/sec — 1024 output tokens in 7.682 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 46s 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 3s 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.