Ruling — Las Vegas

← Las Vegas

You asked

How do I play?

Answered counted as answered

Asked with: Las Vegasbg-117959-en-1e

1. Place the 6 casinos next to each other in the middle of the table in die value order.[1]

2. Shuffle the 54 banknotes and place them in a face-down pile next to the casinos.[1]

3. Add banknotes to each casino until the total value is at least $50,000, arranging them so all values are visible.[1]

4. Give each player 8 dice in a color of their choice.[1]

5. Give the oldest player the start player card.[1]

6. The oldest player begins, and play continues in a clockwise direction.[1]

7. On your turn, roll all of the dice you have left.[1]

8. Choose exactly one of the numbers rolled and add all of those dice to the matching-numbered casino.[1]

9. If you have run out of dice, you pass for the rest of the round.[2]

10. Continue turns until all players have placed all of their dice.[1]

11. Once the last player has added their final dice, check each casino: if two or more players have the same number of dice there, those players return all of their affected dice to their supplies and get nothing.[2]

12. Distribute banknotes from the first casino: the player with the most dice takes all their dice back and receives the highest-value banknote; remaining banknotes are distributed to remaining players in descending order of dice count; if there are not enough banknotes, remaining players receive nothing and take their dice back.[2]

13. Any leftover notes from a casino are placed face down beneath the pile.[2]

14. Repeat the payout process for the other five casinos.[2]

15. Any money won is placed in front of the player, face down.[2]

16. To start the next round, resupply the six casinos with banknotes so they have at least $50,000.[3]

17. Pass the start player card to the player to the left.[4]

18. The game ends after four rounds.[4]

19. The player with the most money is the winner.[5][4]

20. In the event of a tie, the winner is the player with the most banknotes.[4]

21. If there is still a tie, there are multiple winners.[4]

[1] RULEBOOK Las Vegas — Rulebook · p.2 · GAME SETUP · GAMEPLAY

[2] RULEBOOK Las Vegas — Rulebook · p.3

[3] RULEBOOK Las Vegas — Rulebook · p.3

[4] RULEBOOK Las Vegas — Rulebook · p.4 · GAMEPLAY · GAME END · Variant (2 to 4 players) · VARIANT

[5] RULEBOOK Las Vegas — Rulebook · p.1 · GAME IDEA · GAME COMPONENTS

So says the rulebook. So plays the table.

🔧 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 84 ms · ask 3502 ms · total 3587 ms
single-flight (PR-5): queued 0 ms · generation 3587 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read: [{"page": 2, "score": 0.048916, "snippet": "Place the 6 casinos next to each other in the middle of the table in die value order (see fi gure) . Shuffl e the 54 banknotes and place them in a face-down pile next to the casinos. Afterwards, place banknotes above the casinos. Keep adding banknotes to a casino until the total value is at least $5", "headingPath": "GAME SETUP · GAMEPLAY", "sharpsignalDocId": 603}, {"page": 1, "score": 0.048139, "snippet": "The players play as risk-taking gamblers trying their luck in the glitzy world of Las Vegas. Six casinos can be visited, each of them showing a diff erent number and each with a diff erent amount of money available to be won overall. Round after round the same questions are asked: Where should I pla", "headingPath": "GAME IDEA · GAME COMPONENTS", "sharpsignalDocId": 603}, {"page": 4, "score": 0.032258, "snippet": "player card and starts the next round ... The game ends after four rounds and the players count their money. The player with the most is the winner. In the event of a tie, then the winner is the player with the most banknotes. If there is still a tie then there are multiple winners. All previous rul", "headingPath": "GAMEPLAY · GAME END · Variant (2 to 4 players) · VARIANT", "sharpsignalDocId": 603}, {"page": 3, "score": 0.03125, "snippet": "3 If you are out of dice, then you pass for the rest of the round. (So it is possible that only one player has any dice left and thus gets to take multiple turns in a row toward the end of a round.) Once the last player has added his /f_i nal dice to a casino, then the casinos pay out: First, check ", "headingPath": "", "sharpsignalDocId": 603}, {"page": 3, "score": 0.030769, "snippet": "The Next Round Resupply the six casinos with banknotes so that they once again have at least $50,000 on them (see game setup). The player to the left of the previous start player receives the start Players who have run out of dice pass on their turns Important! Players with equal numbers of dice in ", "headingPath": "", "sharpsignalDocId": 603}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show: [{"page": 2, "quote": null, "headingPath": "GAME SETUP · GAMEPLAY", "sharpsignalDocId": 603}, {"page": 3, "quote": null, "headingPath": "", "sharpsignalDocId": 603}, {"page": 3, "quote": null, "headingPath": "", "sharpsignalDocId": 603}, {"page": 4, "quote": null, "headingPath": "GAMEPLAY · GAME END · Variant (2 to 4 players) · VARIANT", "sharpsignalDocId": 603}, {"page": 1, "quote": null, "headingPath": "GAME IDEA · GAME COMPONENTS", "sharpsignalDocId": 603}]
boost provenance — errata + base rulebook (E2/E3): no registered errata card matched this query; base rulebook doc 603 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 603 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.88938 of 1600 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row recorded: Aug 28, 2026 01:24 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 Las Vegas — Rulebook (corpus doc 603)	GAME SETUP · GAMEPLAY	p.2	0.048916 (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 Las Vegas — Rulebook (corpus doc 603)	GAME IDEA · GAME COMPONENTS	p.1	0.048139 (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 Las Vegas — Rulebook (corpus doc 603)	GAMEPLAY · GAME END · Variant (2 to 4 players) · VARIANT	p.4	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
#4	RULEBOOK Las Vegas — Rulebook (corpus doc 603)		p.3	0.03125 (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 Las Vegas — Rulebook (corpus doc 603)		p.3	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

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 5 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 Las Vegas — Rulebook (corpus doc 603)	GAME IDEA · GAME COMPONENTS	p.1	#2	0.048139 (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 Las Vegas — Rulebook (corpus doc 603)	GAMEPLAY · GAME END · Variant (2 to 4 players) · VARIANT	p.4	#3	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))	vector + the doc-priority boost arm	the re-ranker chose it
#3	RULEBOOK Las Vegas — Rulebook (corpus doc 603)		p.3	#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))	vector + the doc-priority boost arm	the re-ranker chose it
#4	RULEBOOK Las Vegas — Rulebook (corpus doc 603)		p.3	#4	0.03125 (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
#5	RULEBOOK Las Vegas — Rulebook (corpus doc 603)	GAME SETUP · GAMEPLAY	p.2	#1	0.048916 (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 Las Vegas — Rulebook (corpus doc 603)	GAME SETUP · GAMEPLAY	p.2	no quote on the wire
[2]	RULEBOOK Las Vegas — Rulebook (corpus doc 603)		p.3	no quote on the wire
[3]	RULEBOOK Las Vegas — Rulebook (corpus doc 603)		p.3	no quote on the wire
[4]	RULEBOOK Las Vegas — Rulebook (corpus doc 603)	GAMEPLAY · GAME END · Variant (2 to 4 players) · VARIANT	p.4	no quote on the wire
[5]	RULEBOOK Las Vegas — Rulebook (corpus doc 603)	GAME IDEA · GAME COMPONENTS	p.1	no quote on the wire

generation — timing and the path taken

timing split: retrieval 84 ms · first delta 1040 ms · total 3587 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 84 ms · ask 3502 ms · gateway work 3587 ms · total 3587 ms
tokens in (the prompt the answerer read): 2378
tokens out (what the answerer generated): 507
tok/sec: 202.9 tok/sec — 507 output tokens in 2.499 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 9s ago)
answerer host (measured by rulesage): reachable (for 23h, checked 0s 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 535), 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.