RuleSage cited table rulings
← Catan

You asked

How do I setup the game?

Answered counted as answered

For a beginner's starting set-up, follow these steps: 1. Assemble the frame exactly as shown in Illustration R [1]. 2. Place the terrain hexes exactly as shown in Illustration R [1]. 3. Place 2 settlements and 2 roads of each color as shown [1]. 4. If only 3 players are playing, remove the red pieces [1]. 5. Each player receives the 3 resources from the terrain hexes adjacent to their settlement marked by a white star [1]. 6. The oldest player is the starting player and takes the first turn, rolling for resource production [1].

[1] RULEBOOK Catan — Rulebook · p.13 · startinG set-up for BeGinners

Strategy guides → — community tips, kept separate from rulings

🔧 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 245 ms · ask 7935 ms · total 8193 ms
single-flight (PR-5)
queued 0 ms · generation 8193 ms
retrieval refs (raw)
[{"page": 12, "score": 0.030886, "snippet": "Once all players have built their first settlement, the player who went last in the first round begins round two. That player builds their second settlement and its adjacent road. Important: After the starting player builds, the other players follow counterclockwise , so the starting player in round", "headingPath": "Round Two", "sharpsignalDocId": 43}, {"page": 8, "score": 0.016393, "snippet": "Here is a summary of the the game sequence, plus some more specific entries where you can find details: Lay out the game board: Set-up, Variable Y Initial set-up: Set-up Phase Y Play The starting player begins the game. The other players follow in clockwise order. On your turn, you complete these 3 ", "headingPath": "Game play", "sharpsignalDocId": 43}, {"page": 13, "score": 0.016129, "snippet": "If you want to use the starting set-up, lay out the board as shown in Illustration R (and the Game Overview): Assemble the frame exactly as shown in Illustration R. Place the terrain hexes exactly as shown in Illustration R. Place 2 settlements and 2 roads of each color as shown. If only 3 are playi", "headingPath": "startinG set-up for BeGinners", "sharpsignalDocId": 43}, {"page": 12, "score": 0.015873, "snippet": "Begin the 'set-up phase' after you build the game map (see Illustration N and Set-up, Variable Y ). Everyone chooses a color and takes the corresponding game pieces: 5 settlements; 4 cities;", "headingPath": "set-up phase", "sharpsignalDocId": 43}, {"page": 2, "score": 0.015625, "snippet": "You can play the game Catan on a variable game board. For your first game, however, we suggest that you use the 'Starting Set-up for Beginners Y .' (See Illus. A on page 3.) This set-up is well-balanced for all players. Before your first game, you must remove the die-cut components from the cardboar", "headingPath": "Starting Set-up for Beginners", "sharpsignalDocId": 43}, {"page": 12, "score": 0.015385, "snippet": "Suggested Beginners' Map Set-up 15 roads; and 1 building costs card. Sort the resource cards into 5 stacks and place them face up beside the board. Shuffle the development cards Y and place them face down beside the resource cards. Place the 2 special cards and the dice beside the board. Place the r", "headingPath": "Illustration N", "sharpsignalDocId": 43}, {"page": 3, "score": 0.015152, "snippet": "Select a color and take your 5 settlements, 4 cities, and 15 roads (no more and no less!). Place your 2 roads and your 2 settlements on the game board. Place your remaining settlements, roads, and cities down in front of you. Note: If you are playing a 3-player game, nobody plays the red position in", "headingPath": "settinG up the Game", "sharpsignalDocId": 43}, {"page": 3, "score": 0.014925, "snippet": "It is more fun to play with a variable game board-with the game board laid out randomly. The board changes each game. If you would like to use the variable set-up, you can find the guidelines in the Almanac under Set-up, Variable Y . Also look for useful tips under Set-up Phase Y and Tactics Y .", "headingPath": "Starting Set-up for Experienced Players", "sharpsignalDocId": 43}]
citations (raw)
[{"page": 13, "quote": null, "headingPath": "startinG set-up for BeGinners", "sharpsignalDocId": 43}]
boost provenance — errata + base rulebook (E2/E3)
no registered errata card matched this query; base-rulebook boost: not recorded (this ruling predates it); rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base-rulebook boost: not recorded (this ruling predates it)
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
Oct 24, 2026 04:47

score = the fused retrieval score (reciprocal-rank fusion over the search arms) — NOT a cosine similarity. How many arms fused this ruling was NOT RECORDED (it predates the boost trail, ran on the path that stored none, or stored one that could not be read), and the ceiling depends on that count (ceiling = arms/(k+1) at k=60): 2 arms top out at 0.03279; 3 arms top out at 0.04918. So a score above 0.03279 here is not an anomaly: it is arithmetic proof a boost arm voted, and the measured band 0.016–0.033 (taken on two-arm asks) is what does not apply. 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 rankdocumentheadingpage fused RRF scoresnippet chars
#1 RULEBOOK Catan — Rulebook (corpus doc 43) Round Two p.12 0.030886 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded)) 300
#2 RULEBOOK Catan — Rulebook (corpus doc 43) Game play p.8 0.016393 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded)) 300
#3 RULEBOOK Catan — Rulebook (corpus doc 43) startinG set-up for BeGinners p.13 0.016129 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded)) 300
#4 RULEBOOK Catan — Rulebook (corpus doc 43) set-up phase p.12 0.015873 (below the measured healthy band (< 0.016) — a weak fuse on a two-arm ask, and this ruling's arm count was never recorded) 190
#5 RULEBOOK Catan — Rulebook (corpus doc 43) Starting Set-up for Beginners p.2 0.015625 (below the measured healthy band (< 0.016) — a weak fuse on a two-arm ask, and this ruling's arm count was never recorded) 300
#6 RULEBOOK Catan — Rulebook (corpus doc 43) Illustration N p.12 0.015385 (below the measured healthy band (< 0.016) — a weak fuse on a two-arm ask, and this ruling's arm count was never recorded) 300
#7 RULEBOOK Catan — Rulebook (corpus doc 43) settinG up the Game p.3 0.015152 (below the measured healthy band (< 0.016) — a weak fuse on a two-arm ask, and this ruling's arm count was never recorded) 300
#8 RULEBOOK Catan — Rulebook (corpus doc 43) Starting Set-up for Experienced Players p.3 0.014925 (below the measured healthy band (< 0.016) — a weak fuse on a two-arm ask, and this ruling's arm count was never recorded) 296

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.

#documentheadingpagequote chars
[1] RULEBOOK Catan — Rulebook (corpus doc 43) startinG set-up for BeGinners p.13 no quote on the wire
timing split
retrieval 245 ms · first delta n/a · total 8193 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 245 ms · ask 7935 ms · gateway work 8193 ms · total 8193 ms
live seat (read from the running child)
answering — gemma4:26b think:false · num_ctx 32768 (live-verified 34s ago)
stream path
not recorded — this ruling predates the stream-path column (V41)
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.
outcome
ANSWERED — Answered
abstain rationale (n/a — this ruling answered)
answered — no abstain rationale applies
decision
SERVED — setup-shaped and this game's approved setup checklist is offered above
pattern that matched
SETUP — "setup" / "set up"
matched words (in the normalized question)
setup

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