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

← Star Wars: X-Wing (Second Edition)

You asked

How do I play?

Answered counted as answered

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

To play, follow these procedures:

Ship Assembly

1. Punch out the ship tokens named Blue Squadron Escort, Academy Pilot, and Black Squadron Ace.[1]

2. Place the ship token on a base with its firing arc oriented over the chevron in the base.[1]

3. Insert one peg into the tower of the base.[1]

4. Insert the second peg into the top of the first peg.[1]

5. Insert the small peg on the bottom of the plastic ship figure into the second peg.[1]

6. Place the ID tokens in the slots.[1]

Maneuver Dial Assembly

1. Connect the dial back to the dial front marked with 'T65'.[2]

2. Connect the dial backs to the dial fronts marked with 'TF'.[2]

(Note: Another source states to connect backplate “T65” to the “X-wing” faceplate, and backplate “TF” to the “TIE Fighter” faceplate [1]).

Setup

1. Each player chooses the ship and upgrade cards they wish to use (squAD builD ing).[3][4]

2. Gather Forces: Each player places their ships and upgrade cards on the table in front of them; place corresponding shields or charges above the ship and/or upgrade cards, and assign ID tokens to each ship.[3][4]

3. Determine Player Order: The player with the lowest squad point total chooses the first player, otherwise, determine the first player randomly.[3][4]

4. Establish Play Area: Establish a 3' x 3' (91 cm) play area on a flat surface or playmat, and players pick opposite edges to be their player edges.[3][4]

5. 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, ensuring they are beyond range 1 of each other and beyond range 2 of each edge.[3][4]

6. Place Forces: Players place ships into the play area in initiative order from lowest to highest initiative (using player order as a tiebreaker), placing ships within range 1 of their player edge.[3][4]

7. Prepare Other Components: Shuffle the damage deck and place it facedown outside the play area (each player uses their own deck if there is more than one); create the supply of range rulers, templates, dice, and tokens near the play area.[3][4]

Executing a Maneuver

1. Take the template that matches the maneuver from the supply.[5]

2. Set the template between the ship's front guides so that it is flush against the base.[5]

3. Pick up and place the ship at the opposite end of the template, sliding the rear guides of the ship into the template.[5]

4. Return the template to the supply.[5]

5. Check the difficulty (color) of the maneuver: if red, the ship gains one stress token; if blue, the ship removes one stress token.[5]

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

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

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

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

[5] RULEBOOK Star Wars: X-Wing (Second Edition) — Rulebook · p.6 · executing A mAneuver

One rule clearer, zero feelings hurt.

🔧 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 360 ms · ask 6977 ms · total 7340 ms
single-flight (PR-5): queued 0 ms · generation 7340 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read: [{"page": 5, "score": 0.04918, "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": 16, "score": 0.045476, "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": 2, "score": 0.045262, "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": 6, "score": 0.044796, "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": 2, "score": 0.044408, "snippet": "Before playing, assemble each dial as shown. Connect the dial back to the dial front marked with 'T65', then connect the dial backs to the dial fronts marked with 'TF'.", "headingPath": "Maneuver Dial Assembly", "sharpsignalDocId": 607}, {"page": 7, "score": 0.043817, "snippet": "The player revealed a blue 2 right bank [2 󲁟 ]. Then they take the [2 󲁟 ] template from the supply. The player places the [2 󲁟 ] template in the play area in front of the ship, sliding the template between the front guides. A ship is stresseD while it has one or more stress tokens. A stressed ship c", "headingPath": "Example of Executing a Maneuver · performing Actions · Example of Position Marker Usage", "sharpsignalDocId": 607}, {"page": 6, "score": 0.031746, "snippet": "When a ship executes a maneuver, the player uses a template to change the ship's position. Then, the ship may be affected by the maneuver's difficulty. To move the ship, the player follows these steps: Take the template that matches the maneuver from the supply. Set the template between the ship's f", "headingPath": "executing A mAneuver", "sharpsignalDocId": 607}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show: [{"page": 3, "quote": null, "headingPath": "", "sharpsignalDocId": 607}, {"page": 2, "quote": null, "headingPath": "Maneuver Dial Assembly", "sharpsignalDocId": 607}, {"page": 5, "quote": null, "headingPath": "SETUP", "sharpsignalDocId": 607}, {"page": 5, "quote": null, "headingPath": "", "sharpsignalDocId": 607}, {"page": 6, "quote": null, "headingPath": "executing A mAneuver", "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.89257 of 2141 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row recorded: Sep 7, 2026 13:34 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.04918 (at the 3-arm ceiling (0.04918) — every arm ranked it #1)	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)	ESCALATION · Core Set Escalation	p.16	0.045476 (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)	INTRODUCTION · GAME OVERVIEW · GETTING STARTED · Assembling DiAls AnD ships · ID Tokens	p.2	0.045262 (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)	SETUP · PHASE 1: PLANNING PHASE · PHASE 2: SYSTEM PHASE · PHASE 3: ACTIVATION PHASE	p.6	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)	Maneuver Dial Assembly	p.2	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))	168
#7	RULEBOOK Star Wars: X-Wing (Second Edition) — Rulebook (corpus doc 607)	Example of Executing a Maneuver · performing Actions · Example of Position Marker Usage	p.7	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))	303
#8	RULEBOOK Star Wars: X-Wing (Second Edition) — Rulebook (corpus doc 607)	executing A mAneuver	p.6	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

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)	Maneuver Dial Assembly	p.2	#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
#2	RULEBOOK Star Wars: X-Wing (Second Edition) — Rulebook (corpus doc 607)	SETUP	p.5	#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
#3	RULEBOOK Star Wars: X-Wing (Second Edition) — Rulebook (corpus doc 607)		p.3	#9	0.029644 (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
#4	RULEBOOK Star Wars: X-Wing (Second Edition) — Rulebook (corpus doc 607)	BEYOND THE CORE SET	p.16	#31	0.011236 (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: X-Wing (Second Edition) — Rulebook (corpus doc 607)	executing A mAneuver	p.6	#8	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 Star Wars: X-Wing (Second Edition) — Rulebook (corpus doc 607)		p.3	#14	0.026847 (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)	ESCALATION · Core Set Escalation	p.16	#3	0.045476 (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 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)		p.3	no quote on the wire
[2]	RULEBOOK Star Wars: X-Wing (Second Edition) — Rulebook (corpus doc 607)	Maneuver Dial Assembly	p.2	no quote on the wire
[3]	RULEBOOK Star Wars: X-Wing (Second Edition) — Rulebook (corpus doc 607)	SETUP	p.5	no quote on the wire
[4]	RULEBOOK Star Wars: X-Wing (Second Edition) — Rulebook (corpus doc 607)		p.5	no quote on the wire
[5]	RULEBOOK Star Wars: X-Wing (Second Edition) — Rulebook (corpus doc 607)	executing A mAneuver	p.6	no quote on the wire

generation — timing and the path taken

timing split: retrieval 360 ms · first delta 2441 ms · total 7340 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 360 ms · ask 6977 ms · gateway work 7340 ms · total 7340 ms
tokens in (the prompt the answerer read): 3658
tokens out (what the answerer generated): 666
tok/sec: 138.8 tok/sec — 666 output tokens in 4.799 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 24s ago)
answerer host (measured by rulesage): reachable (for 22h, 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 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.