RuleSage cited table rulings
← Rummikub

You asked

How do I set up the game?

Answered counted as answered

Asked with: Rummikubbg-811-en-1e

1. Place the tiles face down on the table and mix them thoroughly [1]. 2. Each player picks a tile; the player with the highest number goes first [1]. 3. Return the tiles to the table and mix them [1]. 4. (Recommended) Stack the tiles in piles of 7 for ease of playing [1]. 5. Each player takes 14 tiles and places them on his/her rack [1].

[1] RULEBOOK Rummikub — Rulebook · p.1 · Assembly instructions: · Contents for Rummikub XP/Mini XP · Object of The Game: · Sets: · Set-up:
🔧 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 268 ms · ask 2738 ms · total 2036799 ms
single-flight (PR-5)
queued 2033786 ms · generation 3013 ms
retrieval refs (raw)
[{"page": 1, "score": 0.048652, "snippet": "1 2 3 Contents: 106 tiles (8 sets of tiles 1-13 in four colours, and 2 joker tiles), 4 racks + rack holders . for 5 or 6 players: use all of the 160 tiles (12 sets of tiles 1-13 in four colours, and 4 joker tiles), 6 racks + rack holders. To be the first player to play all the tiles from your rack b", "headingPath": "Assembly instructions: · Contents for Rummikub XP/Mini XP · Object of The Game: · Sets: · Set-up:", "sharpsignalDocId": 152}, {"page": 1, "score": 0.048412, "snippet": "Each tile is worth its face value (the number shown on the tile). In order to make an initial meld, each player must place tiles on the table in one or more sets that total at least 30 points. These points must come from the tiles on each player's rack; for their initial meld, players may not use ti", "headingPath": "Playing The Game:", "sharpsignalDocId": 152}, {"page": 4, "score": 0.047379, "snippet": "The player splits the run. He moves the black 1 to the group of ones, he moves the black 2 to the group of twos and frees the joker. Tiles on table There is a time limit of 1 minute per player, per turn. Players who go over the time limit must draw a tile from the pool, ending their turns. Players w", "headingPath": "4 ways to clear the joker are: · Time Limit: · Incomplete Runs: · Winning: · Scoring:", "sharpsignalDocId": 152}, {"page": 3, "score": 0.046176, "snippet": "There are two jokers in the game. Each joker can be used as any tile in a set, and its number and color are that of the tile needed to complete the set. On future turns, a joker can be retrieved from a set on the table by a player who can replace it during his/her turn with any tiles that can keep t", "headingPath": "The Joker: · 4 ways to clear the joker are:", "sharpsignalDocId": 152}, {"page": 4, "score": 0.031746, "snippet": "| Sample score table: | Player A | Player B | Player C 1 | Player D | | Game 1 | 24 + | 15 - | 16 - | 43 - | | Game 2 | 26 - | 11 - | 22 + | 45 - | | Game 3 | 32 - | 13 - | 22 - | 47 + | | Total Round's | 14 - | 29 - | 4 + | 39 + | The beginning of a game of Rummikub® may seem slow, but as the table", "headingPath": "Strategy:", "sharpsignalDocId": 152}, {"page": 2, "score": 0.030769, "snippet": "Manipulation is the most exciting part of playing \"Rummikub ® \". Players try to table the greatest amount of tiles by rearranging or adding to sets which are already on the table. Sets can be manipulated in many ways (examples follow) as long as at the end of each round only legitimate sets remain a", "headingPath": "Manipulation: · Add one or more tiles from rack to make new set: · Splitting a run:", "sharpsignalDocId": 152}]
citations (raw)
[{"page": 1, "quote": null, "headingPath": "Assembly instructions: · Contents for Rummikub XP/Mini XP · Object of The Game: · Sets: · Set-up:", "sharpsignalDocId": 152}]
boost provenance — errata + base rulebook (E2/E3)
no registered errata card matched this query; base rulebook doc 152 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 152 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:44

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 rankdocumentheadingpage fused RRF scoresnippet chars
#1 RULEBOOK Rummikub — Rulebook (corpus doc 152) Assembly instructions: · Contents for Rummikub XP/Mini XP · Object of The Game: · Sets: · Set-up: p.1 0.048652 (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 Rummikub — Rulebook (corpus doc 152) Playing The Game: p.1 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
#3 RULEBOOK Rummikub — Rulebook (corpus doc 152) 4 ways to clear the joker are: · Time Limit: · Incomplete Runs: · Winning: · Scoring: p.4 0.047379 (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 Rummikub — Rulebook (corpus doc 152) The Joker: · 4 ways to clear the joker are: p.3 0.046176 (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 Rummikub — Rulebook (corpus doc 152) Strategy: p.4 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 Rummikub — Rulebook (corpus doc 152) Manipulation: · Add one or more tiles from rack to make new set: · Splitting a run: p.2 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

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 Rummikub — Rulebook (corpus doc 152) Assembly instructions: · Contents for Rummikub XP/Mini XP · Object of The Game: · Sets: · Set-up: p.1 no quote on the wire
timing split
retrieval 268 ms · first delta 2272 ms · total 2036799 ms (retrieval and first-delta both measured from the START of gateway work, so first-delta INCLUDES retrieval — do not subtract)
full breakdown
queued 2033786 ms · retrieval 268 ms · ask 2738 ms · gateway work 3013 ms · total 2036799 ms
tokens in (the prompt the answerer read)
2405
tokens out (what the answerer generated)
95
tok/sec
135.5 tok/sec — 95 output tokens in 0.701 s of generation
live seat (read from the running child)
answering — gemma4:26b think:false · num_ctx 32768 (live-verified 4s 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.
outcome
ANSWERED — Answered
abstain rationale (n/a — this ruling answered)
answered — no abstain rationale applies
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

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