Ruling — Andromeda's Edge

← Andromeda's Edge

You asked

How do I set up the game?

Answered counted as answered

Asked with: Andromeda's Edgebg-358661-en-1e

Based on the provided sources, the setup for Andromeda's Edge is as follows:

**Board and Component Setup**

1. Place the main board in the center of the table.[1]

2. Place the event board next to the main board and place the event marker on the start space for your player count.[1]

3. Choose an event deck, shuffle it, and place it face down on the event board.[1]

4. Place the Scrapyard board next to the main board.[1]

5. Separate the 15 planet tiles (excluding Alliance Base tiles), shuffle them, and stack them face down at the bottom of the main board.[1]

6. Draw a number of planets based on player count: 2 players (4 planets), 3 players (6 planets), or 4 players (8 planets).[1]

7. Shuffle the drawn planets together with the 6 Alliance Base tiles and lay them face up on the board, one at a time, starting from the top left and proceeding left to right, top to bottom.[1]

8. If playing with special regions, place the selected 2 Quasar or 2 Vortex tiles on the board in the spaces marked with their respective icons before placing other starting tiles; when placing other tiles, skip over these special regions.[2]

9. Shuffle the 6 nebula moons and place 1 face up on each nebula.[1]

10. Separately shuffle each of the 5 colors of planetary moon tokens; on each planet, stack 3 moons of the matching color face down, then flip the stack so the top moon is visible.[1]

11. Place any remaining moons face down near the main board in stacks of 3.[1]

12. Choose an S-Class raider card and build the matching S-Class standees; place the card face up next to the board with the standees near the main board.[1]

13. Roll 2 dice and place 1 S-Class raider standee on nebulae matching the numbers rolled.[1]

14. Select 1 A-Class, 1 B-Class, 1 C-Class, and 1 D-Class raider; build their standees and place the raider cards face down next to the board with the standees nearby.[1]

15. Return all unused raider cards and standees to the game box.[1]

16. Shuffle the discovery tokens and stack 5 face down on each of the 2 marked spaces on the science track, and another 5 face down on the observatory discoveries space at the top of the science track; return remaining tokens to the box.[3]

17. Shuffle the supremacy tokens and place 1 face up on each of the 3 marked spaces on the supremacy track; return remaining tokens to the box.[3]

18. Create a general supply area by shuffling the tactics cards deck and placing it face down, piling development cards by type with matching tiles nearby, and piling damage markers and resources.[3]

19. Shuffle each of the 4 module decks and place them in the marked spaces at the top of the main board, then reveal 3 modules from each deck to fill the columns below.[3]

20. Decide on game length (Short: 50 VP, Medium: 60 VP, or Long: 70 VP) and place the terminus marker on the appropriate space on the VP track.[3]

21. At the beginning of the game, deal each player 2 destiny cards; each player chooses 1 to keep and returns the other to the box.[2]

**Player Setup**

1. Each player places 1 leader on each Alliance Base on the board.[4]

2. Each player rolls a die and places 2 leaders on the nebula matching the die rolled.[4]

3. Each player places their remaining 1 leader in the leaders area of their station.[4]

4. Determine the start player by simulating a battle (highest single die roll) or, in 2-player teams, by comparing combined team rolls.[5][4]

5. The start player places their VP marker on the 1 space of the VP track; subsequent players place markers on the next empty space clockwise.[4]

6. At the start of the game, each player has 3 transports ready to Launch.[6]

[1] RULEBOOK Andromeda's Edge — Rulebook · p.4 · Table of Contents · Main Board: · Event Board: · Scrapyard: · Starting Regions: · Moon tokens: · …

[2] RULEBOOK Andromeda's Edge — Rulebook · p.26 · Setup · SCORING · Placing Raiders · DESTINY CARDS · Quasars · NO ACTION IN A QUASAR · …

[3] RULEBOOK Andromeda's Edge — Rulebook · p.5 · Progress Tracks:

[4] RULEBOOK Andromeda's Edge — Rulebook · p.7 · Leaders: · Start Player:

[5] RULEBOOK Andromeda's Edge — Rulebook · p.27 · Setup · Battle · CREDITS

[6] RULEBOOK Andromeda's Edge — Rulebook · p.15 · STARSHIPS · Building Your Fleet · Ship SPECS · SHIP ABILITIES

🔧 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 410 ms · ask 17506 ms · total 587023 ms
single-flight (PR-5): queued 569092 ms · generation 17931 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read: [{"page": 27, "score": 0.04866, "snippet": "Players form teams of 2. Each player sits next to their teammate. Each player chooses and controls their own faction, as in a normal 4-player game. To choose a start player, each player rolls their 6 dice as normal, but each team combines their rolls and compares their new team roll with the roll of", "headingPath": "Setup · Battle · CREDITS", "sharpsignalDocId": 320}, {"page": 7, "score": 0.046875, "snippet": "7Player SetupPlayer Setup RESOURCES ENERGY Use:Use: station modules, weapons, jumps TITANIUM Use:Use: factories, industry modules, building ships NANOCARBON Use:Use: observatories, science modules ICE Use:Use: cities, civilization modules CREDITS Use:Use: wild for titanium, ice, nanocarbon Over the ", "headingPath": "", "sharpsignalDocId": 320}, {"page": 26, "score": 0.045541, "snippet": "Special regions add unique effects and scoring bonuses to the game. You may choose either the 2 Quasar tiles or the 2 Vortex tiles to include in your game. Before you place any other starting tiles on the board, place the selected special region tiles on the board in the spaces marked with and . The", "headingPath": "Setup · SCORING · Placing Raiders · DESTINY CARDS · Quasars · NO ACTION IN A QUASAR · …", "sharpsignalDocId": 320}, {"page": 6, "score": 0.045455, "snippet": "Player Materials: Each player takes the following materials in their chosen color: 1 station mat 1 player aid 6 transports 1 fighter 1 science vessel 1 heavy cruiser 9 leaders 6 dice 5 track markers 1 VP marker Station mats are double-sided for flexibility. Note the orientation of the four colorful ", "headingPath": "PLAYER SETUP · Station Mat: · Factions: · Ship Upgrades: · Progress Tracks:", "sharpsignalDocId": 320}, {"page": 7, "score": 0.032258, "snippet": "Each player places 1 leader on each Alliance Base on the board. Each player rolls a die and places 2 leaders on the nebula matching the die rolled (more than 1 player can have leaders in the same nebula). Each player places their remaining 1 leader in the leaders area of their station. Choose a star", "headingPath": "Leaders: · Start Player:", "sharpsignalDocId": 320}, {"page": 5, "score": 0.031746, "snippet": "Shuffle the discovery tokens and stack 5 tokens face down on each of the 2 marked spaces on the science track. Stack another 5 discovery tokens face down on the observatory discoveries space at the top of the science track. Return the remaining tokens to the game box. Shuffle the supremacy tokens an", "headingPath": "Progress Tracks:", "sharpsignalDocId": 320}, {"page": 21, "score": 0.030769, "snippet": "During the final step of a Launch turn, if the active region is occupied by 2 or more players or by 1 or more players and the raiders, a battle must be resolved. Battle can occur even if the active player does not have any ships in the active region. Everyone with ships in the active region must par", "headingPath": "BATTLE · BATTLE preparations", "sharpsignalDocId": 320}, {"page": 4, "score": 0.029851, "snippet": "4 Place the main board in the center of the table. Place the event board next to the main board and place the event marker on the start space for your player count. Choose an event deck for this game. We recommend Galactic Dawn for your first foray into the Edge. Shuffle the chosen deck and place it", "headingPath": "Table of Contents · Main Board: · Event Board: · Scrapyard: · Starting Regions: · Moon tokens: · …", "sharpsignalDocId": 320}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show: [{"page": 4, "quote": null, "headingPath": "Table of Contents · Main Board: · Event Board: · Scrapyard: · Starting Regions: · Moon tokens: · …", "sharpsignalDocId": 320}, {"page": 26, "quote": null, "headingPath": "Setup · SCORING · Placing Raiders · DESTINY CARDS · Quasars · NO ACTION IN A QUASAR · …", "sharpsignalDocId": 320}, {"page": 5, "quote": null, "headingPath": "Progress Tracks:", "sharpsignalDocId": 320}, {"page": 7, "quote": null, "headingPath": "Leaders: · Start Player:", "sharpsignalDocId": 320}, {"page": 27, "quote": null, "headingPath": "Setup · Battle · CREDITS", "sharpsignalDocId": 320}, {"page": 15, "quote": null, "headingPath": "STARSHIPS · Building Your Fleet · Ship SPECS · SHIP ABILITIES", "sharpsignalDocId": 320}]
boost provenance — errata + base rulebook (E2/E3): no registered errata card matched this query; base rulebook doc 320 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 320 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:18

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. How much wider that pool was is set gateway-side and is NOT REPORTED for this ruling, and neither are the answerer's final rows — so rulesage has nothing of its own to show beside these.

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 Andromeda's Edge — Rulebook (corpus doc 320)	Setup · Battle · CREDITS	p.27	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 Andromeda's Edge — Rulebook (corpus doc 320)		p.7	0.046875 (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 Andromeda's Edge — Rulebook (corpus doc 320)	Setup · SCORING · Placing Raiders · DESTINY CARDS · Quasars · NO ACTION IN A QUASAR · …	p.26	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 Andromeda's Edge — Rulebook (corpus doc 320)	PLAYER SETUP · Station Mat: · Factions: · Ship Upgrades: · Progress Tracks:	p.6	0.045455 (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 Andromeda's Edge — Rulebook (corpus doc 320)	Leaders: · Start Player:	p.7	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
#6	RULEBOOK Andromeda's Edge — Rulebook (corpus doc 320)	Progress Tracks:	p.5	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
#7	RULEBOOK Andromeda's Edge — Rulebook (corpus doc 320)	BATTLE · BATTLE preparations	p.21	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
#8	RULEBOOK Andromeda's Edge — Rulebook (corpus doc 320)	Table of Contents · Main Board: · Event Board: · Scrapyard: · Starting Regions: · Moon tokens: · …	p.4	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.

the passages the answerer read: NOT RECORDED for this ruling. Any of three things leaves this empty, and they are all different from the answerer having had nothing to read: this ask may never have reached a gateway at all; a multi-book ask keeps each book's own context on that book's own page rather than here; or the gateway build that answered may simply not report it. What this NEVER means is that the answerer read nothing — an answer was composed from passages either way, and their absence here is a gap in what we were told, not in what it read.

chosen chunks — what the answer actually cited

#	document	heading	page	quote chars
[1]	RULEBOOK Andromeda's Edge — Rulebook (corpus doc 320)	Table of Contents · Main Board: · Event Board: · Scrapyard: · Starting Regions: · Moon tokens: · …	p.4	no quote on the wire
[2]	RULEBOOK Andromeda's Edge — Rulebook (corpus doc 320)	Setup · SCORING · Placing Raiders · DESTINY CARDS · Quasars · NO ACTION IN A QUASAR · …	p.26	no quote on the wire
[3]	RULEBOOK Andromeda's Edge — Rulebook (corpus doc 320)	Progress Tracks:	p.5	no quote on the wire
[4]	RULEBOOK Andromeda's Edge — Rulebook (corpus doc 320)	Leaders: · Start Player:	p.7	no quote on the wire
[5]	RULEBOOK Andromeda's Edge — Rulebook (corpus doc 320)	Setup · Battle · CREDITS	p.27	no quote on the wire
[6]	RULEBOOK Andromeda's Edge — Rulebook (corpus doc 320)	STARSHIPS · Building Your Fleet · Ship SPECS · SHIP ABILITIES	p.15	no quote on the wire

generation — timing and the path taken

timing split: retrieval 410 ms · first delta 11064 ms · total 587023 ms (retrieval and first-delta both measured from the START of gateway work, so first-delta INCLUDES retrieval — do not subtract)
full breakdown: queued 569092 ms · retrieval 410 ms · ask 17506 ms · gateway work 17931 ms · total 587023 ms
tokens in (the prompt the answerer read): 3484
tokens out (what the answerer generated): 931
tok/sec: 137.2 tok/sec — 931 output tokens in 6.784 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 39s 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 249), 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.