Ruling — Star Wars: X-Wing (Second Edition)

You asked

How do I setup the game?

Answered counted as answered

Asked with: Star Wars: X-Wing (Second Edition)bg-252328-en-1e

Before playing, each player chooses the ship and upgrade cards they wish to use.[1][2] After players build their squads, they set up by resolving the following steps:

1. Gather Forces: Each player places their ships and upgrade cards on the table in front of them.[1][2] For each ship that has a shield value, charge limit, or Force capacity, place the corresponding shields or charges above the ship and/or upgrade cards.[1][2] All players assign ID tokens to each of their ships.[1][2]

2. Determine Player Order: The player with the lowest squad point total chooses who is the first player; otherwise, randomly determine the first player.[1][2]

3. Establish Play Area: Establish a 3' x 3' (91 cm) play area on a flat surface or use a playmat.[1][2] Players pick opposite edges of the play area to be their player edges.[1]

4. Place Obstacles: In player order, players take turns choosing an obstacle and placing it into the play area until all six obstacles have been placed.[1][2] Obstacles must be placed beyond range 1 of each other and beyond range 2 of each edge of the play area.[1][2]

5. Place Forces: Players place their ships into the play area in initiative order from lowest to highest initiative, using player order as a tiebreaker.[1][2] Players must place ships within range 1 of their player edge.[1]

6. Prepare Other Components: Shuffle the damage deck and place it facedown outside the play area.[1][2] If players have more than one damage deck, each player uses their own deck.[1][2] Then, create the supply of range rulers, templates, dice, and tokens near the play area.[1][2]

[1] RULEBOOK Star Wars: X-Wing (Second Edition) — Rulebook · p.5 · SETUP

[2] RULEBOOK Star Wars: X-Wing (Second Edition) — Rulebook · p.5

Answer in hand — your move.

🔧 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 236 ms · ask 4169 ms · total 4409 ms
single-flight (PR-5): queued 0 ms · generation 4409 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read: [{"page": 5, "score": 0.04866, "snippet": "Before playing a game, each player chooses the ship and upgrade cards they wish to use; this process is known as squAD builDing . How to build squads is described later. After you become the defender (before dice are rolled), you may recover 1 After players build their squads, they set up by resolvi", "headingPath": "SETUP", "sharpsignalDocId": 607}, {"page": 5, "score": 0.048387, "snippet": "5 SETUP Before playing a game, each player chooses the ship and upgrade cards they wish to use; this process is known as squAD builDing. How to build squads is described later. After players build their squads, they set up by resolving the following steps: 1. Gather Forces: Each player places their ", "headingPath": "", "sharpsignalDocId": 607}, {"page": 2, "score": 0.046671, "snippet": "Your T-65 X-wing's engines roar as you swerve into the asteroid field, skirting debris and fragments of past battles. You snap your S-foils shut and flare the thrusters, boosting through a narrow gap between two drifting, ponderous asteroids. As you clear the field, the worried clicks of your faithf", "headingPath": "INTRODUCTION · GAME OVERVIEW · GETTING STARTED · Assembling DiAls AnD ships · ID Tokens", "sharpsignalDocId": 607}, {"page": 3, "score": 0.046394, "snippet": "4. Insert the small peg on the bottom of the plastic ship figure into the second peg. 5. Place the ID tokens in the slots. One player chooses to be the Rebel player and takes the Blue Squadron Escort, the ship card that has that name, and a T-65 X-wing maneuver dial. The other player is the Imperial", "headingPath": "", "sharpsignalDocId": 607}, {"page": 3, "score": 0.044796, "snippet": "3 Setting Wings to Attack Position To open the S-foils of the T-65 X-wing, gently pinch the top engines with two fingers of one hand and the bottom engines with two fingers of the other hand. To close the S-foils, gently pinch the right side engines with two fingers of one hand and the left side eng", "headingPath": "", "sharpsignalDocId": 607}, {"page": 6, "score": 0.03125, "snippet": "X-Wing is played over a series of rounds. Each round consists of five phases: Planning Phase: Players choose maneuvers for their ships using maneuver dials. System Phase: Some ships can resolve specific abilities. Activation Phase: Each ship moves and performs actions. Engagement Phase: Each ship ma", "headingPath": "SETUP · PHASE 1: PLANNING PHASE · PHASE 2: SYSTEM PHASE · PHASE 3: ACTIVATION PHASE", "sharpsignalDocId": 607}, {"page": 16, "score": 0.030886, "snippet": "Instead of a normal match, players can enjoy an Escalation match, in which they control a series of increasingly dangerous ships. To play an Escalation match, players build a squad as described in the Quick Build section with a threat level of 4. (If playing with only the core set, see the 'Core Set", "headingPath": "ESCALATION · Core Set Escalation", "sharpsignalDocId": 607}, {"page": 19, "score": 0.029851, "snippet": "To lAunch a device, follow the steps below: Take the template indicated on the upgrade card. Set the template between the ship's front guides. Place the device indicated on the upgrade card into the play area and slide the guides of the device into the opposite end of the template. Then remove the t", "headingPath": "Dropping AnD lAunching Devices · OTHER MANEUVERS · segnor's loop ( 󲁣 AnD 󲁥 ) · stAtionAry ( 󲁡 ) · reverse strAight ( 󲁬 ) AnD reverse bAnk ( 󲁮 AnD 󲁭 ) · RESERVE · …", "sharpsignalDocId": 607}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show: [{"page": 5, "quote": null, "headingPath": "SETUP", "sharpsignalDocId": 607}, {"page": 5, "quote": null, "headingPath": "", "sharpsignalDocId": 607}]
boost provenance — errata + base rulebook (E2/E3): no registered errata card matched this query; base rulebook doc 607 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 607 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.89722 of 1333 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row recorded: Sep 11, 2026 19:14 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: X-Wing (Second Edition) — Rulebook (corpus doc 607)	SETUP	p.5	0.04866 (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: X-Wing (Second Edition) — Rulebook (corpus doc 607)		p.5	0.048387 (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: X-Wing (Second Edition) — Rulebook (corpus doc 607)	INTRODUCTION · GAME OVERVIEW · GETTING STARTED · Assembling DiAls AnD ships · ID Tokens	p.2	0.046671 (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: X-Wing (Second Edition) — Rulebook (corpus doc 607)		p.3	0.046394 (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: X-Wing (Second Edition) — Rulebook (corpus doc 607)		p.3	0.044796 (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: X-Wing (Second Edition) — Rulebook (corpus doc 607)	SETUP · PHASE 1: PLANNING PHASE · PHASE 2: SYSTEM PHASE · PHASE 3: ACTIVATION PHASE	p.6	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
#7	RULEBOOK Star Wars: X-Wing (Second Edition) — Rulebook (corpus doc 607)	ESCALATION · Core Set Escalation	p.16	0.030886 (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: X-Wing (Second Edition) — Rulebook (corpus doc 607)	Dropping AnD lAunching Devices · OTHER MANEUVERS · segnor's loop ( 󲁣 AnD 󲁥 ) · stAtionAry ( 󲁡 ) · reverse strAight ( 󲁬 ) AnD reverse bAnk ( 󲁮 AnD 󲁭 ) · RESERVE · …	p.19	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

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 40 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: X-Wing (Second Edition) — Rulebook (corpus doc 607)	SETUP	p.5	#1	0.04866 (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: X-Wing (Second Edition) — Rulebook (corpus doc 607)		p.3	#4	0.046394 (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: X-Wing (Second Edition) — Rulebook (corpus doc 607)	SETUP · PHASE 1: PLANNING PHASE · PHASE 2: SYSTEM PHASE · PHASE 3: ACTIVATION PHASE	p.6	#6	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
#4	RULEBOOK Star Wars: X-Wing (Second Edition) — Rulebook (corpus doc 607)	executing A mAneuver	p.6	#10	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
#5	RULEBOOK Star Wars: X-Wing (Second Edition) — Rulebook (corpus doc 607)	INTRODUCTION · GAME OVERVIEW · GETTING STARTED · Assembling DiAls AnD ships · ID Tokens	p.2	#3	0.046671 (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
#6	RULEBOOK Star Wars: X-Wing (Second Edition) — Rulebook (corpus doc 607)	ESCALATION · Core Set Escalation	p.16	#7	0.030886 (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
#7	RULEBOOK Star Wars: X-Wing (Second Edition) — Rulebook (corpus doc 607)	Maneuver Dial Assembly	p.2	#15	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
#8	RULEBOOK Star Wars: X-Wing (Second Edition) — Rulebook (corpus doc 607)		p.5	#2	0.048387 (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 Star Wars: X-Wing (Second Edition) — Rulebook (corpus doc 607)	SETUP	p.5	no quote on the wire
[2]	RULEBOOK Star Wars: X-Wing (Second Edition) — Rulebook (corpus doc 607)		p.5	no quote on the wire

generation — timing and the path taken

timing split: retrieval 236 ms · first delta 2383 ms · total 4409 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 236 ms · ask 4169 ms · gateway work 4409 ms · total 4409 ms
tokens in (the prompt the answerer read): 3805
tokens out (what the answerer generated): 395
tok/sec: 200.9 tok/sec — 395 output tokens in 1.966 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 8s ago)
answerer host (measured by rulesage): reachable (for 22h, checked 8s 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: NO_APPROVED_CHECKLIST — setup-shaped, but no approved setup checklist exists for this game
pattern that matched: SETUP — "setup" / "set up"
matched words (in the normalized question): setup

errata registry — what the gate above had to match against

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