Ruling — Star Wars: Legion

← Star Wars: Legion

You asked

How do I play?

Answered counted as answered

Asked with: Star Wars: Legionbg-233571-en-1e

Star Wars: Legion is played over a series of five Rounds.[1] Each Round is divided into Turns, taken by each player.[1]

Setup

1. Build an Army, a Command Hand, and a Battle Deck [2]

2. Establish the Battlefield and Gather Components [2]

3. Declare Terrain [2]

4. Determine Blue Player [2]

5. Build a Mission [2]

6. Resolve Setup Effects [2]

7. Deploy in Prepared Positions [2]

The Command Phase

During the Command Phase, players perform the following:

1. Select and Play Command Cards: Each player secretly chooses a Command Card from their Command Hand and places it facedown on the battlefield.[1]

2. Resolve Command Cards: Players reveal their Command Cards by flipping them faceup and resolve the effects.[1]

3. Determine Priority: Priority is determined by the number of pips on the played card; the player with the fewest pips gains priority.[3] If cards have the same number of pips, a player rolls a red defense die; if they do not roll a blank, they gain priority.[3]

4. Nominate Commanders and Issue Orders: Players nominate a Commander (a specific unit if the Command Card requires it, otherwise any 1 p unit) and issue Orders to units.[3] A unit cannot receive more than one Order each Round, and the unit must match the type listed on the Command Card.[3]

5. Create the Order Pool: Players create an Order Pool by taking one Order token that matches the Rank of each undefeated unit that was not issued an Order and shuffling those tokens together.[3]

6. Create the Pass Pool: [1]

The Activation Phase

[1]

The End Phase

[1]

[1] RULEBOOK Star Wars: Legion — Rulebook · p.21 · GAME MECHANICS · PARTS OF A ROUND · THE COMMAND PHASE · PARTS OF THE COMMAND PHASE · SELECT AND PLAY COMMAND CARDS · RESOLVING COMMAND CARD EFFECTS · …

[2] RULEBOOK Star Wars: Legion — Rulebook · p.16 · SETUP · BUILD AN ARMY, A COMMAND HAND, AND A BATTLE DECK · FACTIONS, LIGHT SIDE, AND DARK SIDE · POINTS · RANKS AND RANK REQUIREMENTS

[3] RULEBOOK Star Wars: Legion — Rulebook · p.22 · EXAMPLE: PLAYING A COMMAND CARD AND DETERMINING PRIORITY · NOMINATE COMMANDERS AND ISSUE ORDERS · OTHER WAYS TO ISSUE ORDERS · CREATE THE ORDER POOL

The book has spoken.

🔧 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 122 ms · ask 5800 ms · total 5924 ms
single-flight (PR-5): queued 0 ms · generation 5924 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read: [{"page": 21, "score": 0.046696, "snippet": "Star Wars: Legion is played over a series of five Rounds. Each Round is divided into Turns, taken by each player. The following sections contain the rules that specify the parts of each Round and how to play them. Each of the five Rounds in a game of Star Wars: Legion are divided into the following ", "headingPath": "GAME MECHANICS · PARTS OF A ROUND · THE COMMAND PHASE · PARTS OF THE COMMAND PHASE · SELECT AND PLAY COMMAND CARDS · RESOLVING COMMAND CARD EFFECTS · …", "sharpsignalDocId": 1163}, {"page": 21, "score": 0.046642, "snippet": "Once players have resolved all relevant Command Card effects, compare the number of pips on the Command Cards that were played this Round. The player whose card has the least number of pips has priority for the Round. If both players reveal Command Cards with the same number of pips, one player roll", "headingPath": "DETERMINE PRIORITY", "sharpsignalDocId": 1163}, {"page": 22, "score": 0.045541, "snippet": "Michael and Kevin are choosing their Command Cards for the turn. They each secretly choose a card from their hands to play, then they reveal their cards at the same time. Michael has played a 3-pip card, Assault, and Kevin has played a 1-pip card, Ambush. Because Kevin played the card with the fewes", "headingPath": "EXAMPLE: PLAYING A COMMAND CARD AND DETERMINING PRIORITY · NOMINATE COMMANDERS AND ISSUE ORDERS · OTHER WAYS TO ISSUE ORDERS · CREATE THE ORDER POOL", "sharpsignalDocId": 1163}, {"page": 44, "score": 0.044343, "snippet": "The process of getting ready to play a game of Star Wars : Legion is called Setup. Setup consists of the following steps: Army Building Establish the Battlefield and Gather Components Declare Terrain Place Terrain Determine Blue Player Build a Mission Resolve Setup Effects Deploy in Prepared Positio", "headingPath": "SETUP · PARTS OF A ROUND · PARTS OF THE COMMAND PHASE · RESOLVING COMMAND CARD EFFECTS · PARTS OF THE ACTIVATION PHASE", "sharpsignalDocId": 1163}, {"page": 19, "score": 0.032787, "snippet": "Now that the blue player is determined, it is time to build the mission. Place the game dashboard with the mission side face up near the table. Then each player separates their Battle Deck by type-Advantage, Objective, and Secondary Objectiveand shuffles each of their three decks, placing them near ", "headingPath": "BUILDING A MISSION", "sharpsignalDocId": 1163}, {"page": 28, "score": 0.032258, "snippet": "The only way a unit can Move or be placed into base contact with an enemy miniature is to Move into Melee. While a unit that has at least one weapon with a 9 is Moving or being placed, it can Move into Melee by Moving or placing that unit's unit leader into base contact with an enemy miniature. When", "headingPath": "MOVING INTO MELEE", "sharpsignalDocId": 1163}, {"page": 19, "score": 0.031746, "snippet": "Players determine what pieces of terrain to use in their game and their rules. Players should be sure to agree with their opponent on the rules for each terrain piece before the game begins. Once players have determined what terrain is being used and any applicable rules, they then cooperatively set", "headingPath": "DECLARE AND PLACE TERRAIN · DETERMINE BLUE PLAYER", "sharpsignalDocId": 1163}, {"page": 26, "score": 0.03125, "snippet": "Units on notched bases follow all the above rules for movement. Additionally, a unit on a notched base must execute the following steps to make a Standard Move: The player may rotate the unit leader's base up to 90° to the left or right, keeping the center of the base in the same place. The player t", "headingPath": "NOTCHED BASE MOVEMENT", "sharpsignalDocId": 1163}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show: [{"page": 21, "quote": null, "headingPath": "GAME MECHANICS · PARTS OF A ROUND · THE COMMAND PHASE · PARTS OF THE COMMAND PHASE · SELECT AND PLAY COMMAND CARDS · RESOLVING COMMAND CARD EFFECTS · …", "sharpsignalDocId": 1163}, {"page": 16, "quote": null, "headingPath": "SETUP · BUILD AN ARMY, A COMMAND HAND, AND A BATTLE DECK · FACTIONS, LIGHT SIDE, AND DARK SIDE · POINTS · RANKS AND RANK REQUIREMENTS", "sharpsignalDocId": 1163}, {"page": 22, "quote": null, "headingPath": "EXAMPLE: PLAYING A COMMAND CARD AND DETERMINING PRIORITY · NOMINATE COMMANDERS AND ISSUE ORDERS · OTHER WAYS TO ISSUE ORDERS · CREATE THE ORDER POOL", "sharpsignalDocId": 1163}]
boost provenance — errata + base rulebook (E2/E3): no registered errata card matched this query; base rulebook doc 1163 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 1163 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.89977 of 1287 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row recorded: Sep 6, 2026 12:53 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 Star Wars: Legion — Rulebook (corpus doc 1163)	GAME MECHANICS · PARTS OF A ROUND · THE COMMAND PHASE · PARTS OF THE COMMAND PHASE · SELECT AND PLAY COMMAND CARDS · RESOLVING COMMAND CARD EFFECTS · …	p.21	0.046696 (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 Star Wars: Legion — Rulebook (corpus doc 1163)	DETERMINE PRIORITY	p.21	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
#3	RULEBOOK Star Wars: Legion — Rulebook (corpus doc 1163)	EXAMPLE: PLAYING A COMMAND CARD AND DETERMINING PRIORITY · NOMINATE COMMANDERS AND ISSUE ORDERS · OTHER WAYS TO ISSUE ORDERS · CREATE THE ORDER POOL	p.22	0.045541 (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 Star Wars: Legion — Rulebook (corpus doc 1163)	SETUP · PARTS OF A ROUND · PARTS OF THE COMMAND PHASE · RESOLVING COMMAND CARD EFFECTS · PARTS OF THE ACTIVATION PHASE	p.44	0.044343 (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 Star Wars: Legion — Rulebook (corpus doc 1163)	BUILDING A MISSION	p.19	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 Star Wars: Legion — Rulebook (corpus doc 1163)	MOVING INTO MELEE	p.28	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
#7	RULEBOOK Star Wars: Legion — Rulebook (corpus doc 1163)	DECLARE AND PLACE TERRAIN · DETERMINE BLUE PLAYER	p.19	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
#8	RULEBOOK Star Wars: Legion — Rulebook (corpus doc 1163)	NOTCHED BASE MOVEMENT	p.26	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

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 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 at	document	heading	page	fused rank	fused RRF score	carried by	how it got its slot
#1	RULEBOOK Star Wars: Legion — Rulebook (corpus doc 1163)	GAME MECHANICS · PARTS OF A ROUND · THE COMMAND PHASE · PARTS OF THE COMMAND PHASE · SELECT AND PLAY COMMAND CARDS · RESOLVING COMMAND CARD EFFECTS · …	p.21	#1	0.046696 (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 Star Wars: Legion — Rulebook (corpus doc 1163)	EXAMPLE: PLAYING A COMMAND CARD AND DETERMINING PRIORITY · NOMINATE COMMANDERS AND ISSUE ORDERS · OTHER WAYS TO ISSUE ORDERS · CREATE THE ORDER POOL	p.22	#3	0.045541 (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 Star Wars: Legion — Rulebook (corpus doc 1163)	MOVING INTO MELEE	p.28	#6	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 Star Wars: Legion — Rulebook (corpus doc 1163)	TIMING	p.6	#19	0.014085 (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 Star Wars: Legion — Rulebook (corpus doc 1163)	SETUP · BUILD AN ARMY, A COMMAND HAND, AND A BATTLE DECK · FACTIONS, LIGHT SIDE, AND DARK SIDE · POINTS · RANKS AND RANK REQUIREMENTS	p.16	#10	0.027032 (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 Star Wars: Legion — Rulebook (corpus doc 1163)	EMPTY DECKS	p.19	#22	0.013699 (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
#7	RULEBOOK Star Wars: Legion — Rulebook (corpus doc 1163)	ESTABLISH THE BATTLEFIELD AND PREPARE COMPONENTS	p.18	#39	0.011111 (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
#8	RULEBOOK Star Wars: Legion — Rulebook (corpus doc 1163)	DECLARE AND PLACE TERRAIN · DETERMINE BLUE PLAYER	p.19	#7	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

chosen chunks — what the answer actually cited

#	document	heading	page	quote chars
[1]	RULEBOOK Star Wars: Legion — Rulebook (corpus doc 1163)	GAME MECHANICS · PARTS OF A ROUND · THE COMMAND PHASE · PARTS OF THE COMMAND PHASE · SELECT AND PLAY COMMAND CARDS · RESOLVING COMMAND CARD EFFECTS · …	p.21	no quote on the wire
[2]	RULEBOOK Star Wars: Legion — Rulebook (corpus doc 1163)	SETUP · BUILD AN ARMY, A COMMAND HAND, AND A BATTLE DECK · FACTIONS, LIGHT SIDE, AND DARK SIDE · POINTS · RANKS AND RANK REQUIREMENTS	p.16	no quote on the wire
[3]	RULEBOOK Star Wars: Legion — Rulebook (corpus doc 1163)	EXAMPLE: PLAYING A COMMAND CARD AND DETERMINING PRIORITY · NOMINATE COMMANDERS AND ISSUE ORDERS · OTHER WAYS TO ISSUE ORDERS · CREATE THE ORDER POOL	p.22	no quote on the wire

generation — timing and the path taken

timing split: retrieval 122 ms · first delta 3973 ms · total 5924 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 122 ms · ask 5800 ms · gateway work 5924 ms · total 5924 ms
tokens in (the prompt the answerer read): 2609
tokens out (what the answerer generated): 382
tok/sec: 202.4 tok/sec — 382 output tokens in 1.887 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 23s ago)
answerer host (measured by rulesage): reachable (for 22h, 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 1093), 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.