You asked
How do I set up the game?
Answered counted as answeredAsked with: Star Wars: Imperial Assaultbg-164153-en-1e
Depending on the type of mission being played, the setup is as follows: **Skirmish Mission Setup** 1. Both players simultaneously place their Deployment cards faceup in their play areas [1]. 2. Each player shuffles his deck of 15 Command cards and places it by his Deployment cards [1]. 3. The player who has the lowest total cost of Deployment cards chooses which player begins the game with the initiative token (if there is a tie, players determine initiative randomly) [1]. 4. The player with initiative shuffles his deck of Skirmist Mission cards and draws one card to determine the mission name, map, and special rules [1]. 5. Players refer to the matching skirmish mission's diagram to build the map and place tokens on it as shown (players only place 'A' or 'B' tokens that match the card's letter) [1]. 6. The player with initiative chooses either the red or blue deployment zone shown on the diagram and deploys all of his figures there; then his opponent deploys all of his figures in the other deployment zone [1]. 7. Each player draws three cards from his Command deck [1][2]. **Campaign Mission Setup** 1. The Imperial player assembles the mission's map using map tiles as shown in the Campaign Guide and places all tokens on the map as indicated in the diagram [3]. 2. The Imperial player sets the threat dial to zero and the round dial to one [3]. 3. The Imperial player takes all Deployment cards and sorts them as listed in the 'Deployment and Setup' box of the mission rules (this includes placing Initial Groups faceup, placing Reserved Groups in a facedown pile, and choosing Open Groups to place in his hand) [3]. 4. Follow any Special Setup rules listed in the mission rules [3]. 5. The Imperial player deploys figures on the map as indicated in the diagram [3]. 6. All dice, the Condition and Supply decks, damage tokens, strain tokens, and condition tokens are placed within easy reach of all players [3]. 7. The Imperial player reads the 'Mission Briefing' section of the mission's rules aloud to all players [3]. 8. Rebel players choose the order in which their figures are deployed and place all Rebel figures in the space containing and as close as possible to the entrance token [3]. 9. Before placing figures, Rebel players choose the Item cards they will bring (each hero may bring up to 1 Armor, 2 Weapons, and 3 Equipment) [3][4]. 10. After deploying hero figures, Rebel players may choose to deploy an ally that they have gained as a reward [3]. 11. Each hero receives one activation token and places it ready (green side faceup) on his Hero sheet [3]. **Campaign Setup (Before starting a new campaign)** 1. Players choose one player to be the Imperial player; all other players are Rebel players [5]. 2. Each Rebel player chooses one Hero sheet and places that hero's Class deck and figure in his play area, then retrieves any Item cards without a cost from his Class deck and places them faceup in his play area (in 2-hero games, each hero claims a 'Legendary' Reward card; in 3-hero games, each hero claims a 'Heroic' Reward card) [5]. 3. The Imperial player chooses an Imperial Class deck and places the basic card faceup in his play area [5]. 4. The Imperial player builds his deck of Agenda cards [5]. 5. Rebel players build the Side Mission deck [5].
🔧 debug — where this ruling came from
- outcome
- ANSWERED — Answered
- corpus profile
- live
- answerer pin (deploy-frozen, attribution only)
- gemma4:26b think:false 5571076f3d70
- timings
- search 306 ms · ask 17079 ms · total 951166 ms
- single-flight (PR-5)
- queued 933769 ms · generation 17397 ms
- retrieval refs (raw)
- [{"page": 7, "score": 0.048412, "snippet": "Before starting a new campaign, perform the following steps. Choose Player Roles: Players choose one player to take on the role of the Imperial player. All other players are Rebel players. Players retain these roles for the entirety of the campaign. Choose Heroes: Each Rebel player chooses one Hero ", "headingPath": "campaIGn setup", "sharpsignalDocId": 284}, {"page": 18, "score": 0.04741, "snippet": "To set up a skirmish mission, perform the following steps. Bring Armies and Command Cards: Both players simultaneously place their Deployment cards faceup in their play areas. Then each player shuffles his deck of 15 Command cards and places it by his Deployment cards. Determine Initiative: The play", "headingPath": "skirmish mission seTup", "sharpsignalDocId": 284}, {"page": 18, "score": 0.047131, "snippet": "To setup a campaign mission, perform the following steps. Assemble Map: The Imperial player assembles the mission's map using map tiles as shown in the Campaign Guide. He places all tokens on the map as indicated in the diagram. Prepare Threat and Round Dial: The Imperial player sets the threat dial", "headingPath": "CAmpAign mission seTup", "sharpsignalDocId": 284}, {"page": 11, "score": 0.045956, "snippet": "The Imperial player deploys figures throughout the course of every mission. The 'Deployment and Setup' box in the mission's rules lists which figures the Imperial player can deploy throughout the mission (see 'Mission Setup' on page 18). Deployment location is determined by named tiles or icons, suc", "headingPath": "CAmpAign deploymenT · skirmish deploymenT", "sharpsignalDocId": 284}, {"page": 8, "score": 0.043549, "snippet": "During a skirmish, players play Command cards to resolve a wide range of powerful abilities. During setup, each player draws three Command cards into his hand. Command cards in a player's hand are kept secret from his opponent. Each player draws one Command card each Status Phase, plus one additiona", "headingPath": "command cards · component lImItatIons", "sharpsignalDocId": 284}, {"page": 17, "score": 0.030769, "snippet": "During a campaign, players resolve a series of story and side missions. The rules and maps for each mission are found in the Campaign Guide. During each Mission Stage, the heroes choose one active mission to resolve. -The campaign log lists the type of active mission the heroes can choose during eac", "headingPath": "sTory And side missions · Building the Side MiSSion deck · forCed missions", "sharpsignalDocId": 284}, {"page": 14, "score": 0.030303, "snippet": "During a campaign, most missions provide the Imperial player certain Deployment cards called initial groups. The figures for these groups are placed according to the map in the mission's diagram. These cards are not part of his hand and are placed faceup at the start of the mission. When the last fi", "headingPath": "InItIal Groups · InItIatIve", "sharpsignalDocId": 284}, {"page": 18, "score": 0.030159, "snippet": "Forced missions are resolved between campaign stages. After resolving a forced mission, players should perform the 'postmission cleanup' step of a Mission Stage. Then they resolve the next available stage of the campaign. -If the mission occurs immediately after another mission is resolved, they res", "headingPath": "forCed missions · skirmish missions · mIssIon setup", "sharpsignalDocId": 284}]
- citations (raw)
- [{"page": 18, "quote": null, "headingPath": "skirmish mission seTup", "sharpsignalDocId": 284}, {"page": 8, "quote": null, "headingPath": "command cards · component lImItatIons", "sharpsignalDocId": 284}, {"page": 18, "quote": null, "headingPath": "CAmpAign mission seTup", "sharpsignalDocId": 284}, {"page": 15, "quote": null, "headingPath": "Item cards · modifiCATions", "sharpsignalDocId": 284}, {"page": 7, "quote": null, "headingPath": "campaIGn setup", "sharpsignalDocId": 284}]
- boost provenance — errata + base rulebook (E2/E3)
-
no registered errata card matched this query; base rulebook doc 284 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 284 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)
- debug row retained until
- Nov 6, 2026 14:24
retrieval — what the search arm returned
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: Imperial Assault — Rulebook (corpus doc 284) | campaIGn setup | p.7 | 0.048412 (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: Imperial Assault — Rulebook (corpus doc 284) | skirmish mission seTup | p.18 | 0.04741 (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: Imperial Assault — Rulebook (corpus doc 284) | CAmpAign mission seTup | p.18 | 0.047131 (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: Imperial Assault — Rulebook (corpus doc 284) | CAmpAign deploymenT · skirmish deploymenT | p.11 | 0.045956 (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: Imperial Assault — Rulebook (corpus doc 284) | command cards · component lImItatIons | p.8 | 0.043549 (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: Imperial Assault — Rulebook (corpus doc 284) | sTory And side missions · Building the Side MiSSion deck · forCed missions | p.17 | 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)) | 300 |
| #7 | RULEBOOK Star Wars: Imperial Assault — Rulebook (corpus doc 284) | InItIal Groups · InItIatIve | p.14 | 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 Star Wars: Imperial Assault — Rulebook (corpus doc 284) | forCed missions · skirmish missions · mIssIon setup | p.18 | 0.030159 (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 |
chosen chunks — what the answer actually cited
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.
| # | document | heading | page | quote chars |
|---|---|---|---|---|
| [1] | RULEBOOK Star Wars: Imperial Assault — Rulebook (corpus doc 284) | skirmish mission seTup | p.18 | no quote on the wire |
| [2] | RULEBOOK Star Wars: Imperial Assault — Rulebook (corpus doc 284) | command cards · component lImItatIons | p.8 | no quote on the wire |
| [3] | RULEBOOK Star Wars: Imperial Assault — Rulebook (corpus doc 284) | CAmpAign mission seTup | p.18 | no quote on the wire |
| [4] | RULEBOOK Star Wars: Imperial Assault — Rulebook (corpus doc 284) | Item cards · modifiCATions | p.15 | no quote on the wire |
| [5] | RULEBOOK Star Wars: Imperial Assault — Rulebook (corpus doc 284) | campaIGn setup | p.7 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 306 ms · first delta 12038 ms · total 951166 ms (retrieval and first-delta both measured from the START of gateway work, so first-delta INCLUDES retrieval — do not subtract)
- full breakdown
- queued 933769 ms · retrieval 306 ms · ask 17079 ms · gateway work 17397 ms · total 951166 ms
- tokens in (the prompt the answerer read)
- 3852
- tokens out (what the answerer generated)
- 773
- tok/sec
- 146.6 tok/sec — 773 output tokens in 5.273 s of generation
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 3s ago)
- 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)
-
set up
errata registry — what the gate above had to match against
this game registers NO errata cards (edition 208), 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.