Ruling — Rolling Heights

You asked

How do I setup the game?

Answered counted as answered

Asked with: Rolling Heightsbg-331820-en-1e

To setup the game, follow these steps:

1. Flip the 6 Neighborhood boards to the following sides depending on the number of players: 2 players use all 6 A sides; 3 players use 4 randomly selected A sides and 2 randomly selected B sides; 4 players use 3 randomly selected A sides and 3 randomly selected B sides.[1]

2. Arrange the 6 Neighborhood boards randomly in a 2x3 grid to form the map (icons do not all have to face the same direction).[1]

3. Place the Score Board next to the map and place the 2 Market Strips alongside the map.[1]

4. Sort Building Plan tiles into 2 groups based on their backs and shuffle them face-down.[1]

5. Stack LEVEL 1 tiles face-down by the draw area on Market Strip Level 1 and lay out 9 tiles face-up along the indicated spaces on the strip; repeat this process for LEVEL 2 tiles and Market Strip Level 2.[1]

6. Sort cubes into piles by color, leaving miscellaneous cubes to the side.[1]

7. Depending on the number of players, remove the following number of cubes (except misc.) and return them to the box: 2 players remove 25 cubes of each color; 3 players remove 13 cubes of each color; 4 players use all cubes.[1]

8. Sort meeples by color and place them near the boards to form the supply.[1]

9. Place the Wild Tokens near the boards.[1]

10. Shuffle the rectangular Ad tiles face-down, select 3 randomly, and place them face-up on the indicated spaces on the score board.[1]

11. Shuffle the Target tiles face-down and deal 2 to each player; players should look at these but keep them hidden.[1]

12. Each player chooses a player color and takes the player token and 18 ownership markers of that color.[2][1]

13. Place the player tokens on space '0' on the score track on the score board.[2][1]

14. Each player takes a rolling box, 2 Carpenter meeples, and 2 Construction Worker meeples, which can be placed in their box for now.[2]

15. Randomly determine a start player, who takes the start player token.[3]

16. Beginning with the last player and going counter-clockwise, players select their starting Building Plan and starting location on the map.[3] A player may choose any face-up Building Plan tile along Market Strip Level 1 and place it on any land space (not water) that does not show an icon indicating cubes must be spent to build there.[3] After placing the tile, the player places one of their color ownership markers on the tile.[3] Players following in counter-clockwise order do the same, but may not place their starting tile within 2 orthogonal spaces of another player's tile.[3] Continue until all players have placed a starting tile.[3]

17. Slide down the remaining tiles along Market Strip Level 1 to fill blank spaces, then refill remaining blank spaces with LEVEL 1 tiles from the draw area.[3]

[1] RULEBOOK Rolling Heights — Rulebook · p.2 · SET UP

[2] RULEBOOK Rolling Heights — Rulebook · p.2 · SET UP

[3] RULEBOOK Rolling Heights — Rulebook · p.4 · SET UP · STARTING PLACEMENT AND BUILDING PLANS · GAME TURN

That settles it — whose turn was it?

🔧 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 153 ms · ask 4716 ms · total 4871 ms
single-flight (PR-5): queued 0 ms · generation 4871 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read: [{"page": 2, "score": 0.04866, "snippet": "Players should look at their Target tiles but keep them hidden from other players. At the end of the game, each player will choose 1 of the 2 Target tiles to score. Finally, each player chooses a player color and takes the player token and 18 ownership markers of that color. Place the player tokens ", "headingPath": "SET UP", "sharpsignalDocId": 1218}, {"page": 4, "score": 0.048387, "snippet": "Example: The building type matches the bonus indicated on the map space, so this player would score 2 . Randomly determine a start player, who takes the start player token. Then, beginning with the last player and going counter-clockwise, players will select their starting Building Plan and starting", "headingPath": "SET UP · STARTING PLACEMENT AND BUILDING PLANS · GAME TURN", "sharpsignalDocId": 1218}, {"page": 2, "score": 0.046875, "snippet": "The 6 Neighborhood boards each have an A side and a B side. Depending on the number of players, flip the boards to the following sides: ◆ ◆ ◆ 2 players: Use all 6 A sides. 3 players: Use 4 randomly selected A sides and 2 randomly selected B sides. 4 players: Use 3 randomly selected A sides and 3 ran", "headingPath": "SET UP", "sharpsignalDocId": 1218}, {"page": 10, "score": 0.045805, "snippet": "When the supply of cubes of 1 or more colors runs out, immediately add to the supply all the miscellaneous cubes that were set aside at the beginning of the game. These can be used as substitutes for cubes of any color that has run out and can now be gained by any player. ◆ ◆ ◆ These cubes represent", "headingPath": "MISCELLANEOUS CUBES · GAME END · SCORING", "sharpsignalDocId": 1218}, {"page": 5, "score": 0.031746, "snippet": "◆ ◆ If you have 10 or fewer meeples, you will roll all of them. (At the start of the game, you have 4 meeples. ) If you have more than 10 meeples, choose 10 of them to roll this turn and place the rest to the side of your play area. They will not be used this turn, but you may choose from them to us", "headingPath": "PHASE 1: PREP · Cocked or Stacked Meeples", "sharpsignalDocId": 1218}, {"page": 5, "score": 0.030769, "snippet": "55 PHASE 1: PREP ◆ If you have 10 or fewer meeples, you will roll all of them. (At the start of the game, you have 4 meeples. ) ◆ If you have more than 10 meeples, choose 10 of them to roll this turn and place the rest to the side of your play area. They will not be used this turn, but you may choos", "headingPath": "", "sharpsignalDocId": 1218}, {"page": 9, "score": 0.030303, "snippet": "◆ Return all your unused cubes to the supply. ◆ ◆ ◆ Any remaining Spending Power is lost. Gather all your active and non-active meeples for your next turn. Slide down (in the direction of the printed arrows) the Building Plan tiles along the Market Strip to fill in any blank spaces, and refill the t", "headingPath": "PHASE 4: CLEANUP", "sharpsignalDocId": 1218}, {"page": 6, "score": 0.029851, "snippet": "Example: If you had 1 Working Hard meeple and 2 Working Steady meeples, you would have to return 1 of the meeples to your box as Exhausted . You then gain 1 Wild Token from the supply. Finally, proceed to your Main phase. Choose whether to stop and move on to your Main phase or push your luck and at", "headingPath": "How to Resolve a Strike · PHASE 2: RISK · PHASE 3: MAIN · Activating Meeples:", "sharpsignalDocId": 1218}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show: [{"page": 2, "quote": null, "headingPath": "SET UP", "sharpsignalDocId": 1218}, {"page": 2, "quote": null, "headingPath": "SET UP", "sharpsignalDocId": 1218}, {"page": 4, "quote": null, "headingPath": "SET UP · STARTING PLACEMENT AND BUILDING PLANS · GAME TURN", "sharpsignalDocId": 1218}]
boost provenance — errata + base rulebook (E2/E3): no registered errata card matched this query; base rulebook doc 1218 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 1218 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.90749 of 2270 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row recorded: Sep 6, 2026 18:52 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 Rolling Heights — Rulebook (corpus doc 1218)	SET UP	p.2	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 Rolling Heights — Rulebook (corpus doc 1218)	SET UP · STARTING PLACEMENT AND BUILDING PLANS · GAME TURN	p.4	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 Rolling Heights — Rulebook (corpus doc 1218)	SET UP	p.2	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
#4	RULEBOOK Rolling Heights — Rulebook (corpus doc 1218)	MISCELLANEOUS CUBES · GAME END · SCORING	p.10	0.045805 (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 Rolling Heights — Rulebook (corpus doc 1218)	PHASE 1: PREP · Cocked or Stacked Meeples	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
#6	RULEBOOK Rolling Heights — Rulebook (corpus doc 1218)		p.5	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 Rolling Heights — Rulebook (corpus doc 1218)	PHASE 4: CLEANUP	p.9	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 Rolling Heights — Rulebook (corpus doc 1218)	How to Resolve a Strike · PHASE 2: RISK · PHASE 3: MAIN · Activating Meeples:	p.6	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 22 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 Rolling Heights — Rulebook (corpus doc 1218)	SET UP · STARTING PLACEMENT AND BUILDING PLANS · GAME TURN	p.4	#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
#2	RULEBOOK Rolling Heights — Rulebook (corpus doc 1218)	SET UP	p.2	#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
#3	RULEBOOK Rolling Heights — Rulebook (corpus doc 1218)		p.5	#6	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))	vector + the doc-priority boost arm	the re-ranker chose it
#4	RULEBOOK Rolling Heights — Rulebook (corpus doc 1218)	CITY PLANNER BLACK	p.7	#12	0.014085 (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 Rolling Heights — Rulebook (corpus doc 1218)	MISCELLANEOUS CUBES · GAME END · SCORING	p.10	#4	0.045805 (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 Rolling Heights — Rulebook (corpus doc 1218)	PHASE 1: PREP · Cocked or Stacked Meeples	p.5	#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))	vector + the doc-priority boost arm	the re-ranker chose it
#7	RULEBOOK Rolling Heights — Rulebook (corpus doc 1218)	PHASE 4: CLEANUP	p.9	#7	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))	vector + the doc-priority boost arm	the re-ranker chose it
#8	RULEBOOK Rolling Heights — Rulebook (corpus doc 1218)	SET UP	p.2	#3	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))	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 Rolling Heights — Rulebook (corpus doc 1218)	SET UP	p.2	no quote on the wire
[2]	RULEBOOK Rolling Heights — Rulebook (corpus doc 1218)	SET UP	p.2	no quote on the wire
[3]	RULEBOOK Rolling Heights — Rulebook (corpus doc 1218)	SET UP · STARTING PLACEMENT AND BUILDING PLANS · GAME TURN	p.4	no quote on the wire

generation — timing and the path taken

timing split: retrieval 153 ms · first delta 1401 ms · total 4871 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 153 ms · ask 4716 ms · gateway work 4871 ms · total 4871 ms
tokens in (the prompt the answerer read): 3238
tokens out (what the answerer generated): 687
tok/sec: 201.3 tok/sec — 687 output tokens in 3.412 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 28s ago)
answerer host (measured by rulesage): reachable (for 22h, checked 7s 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 1148), 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.