RuleSage cited table rulings
← Camel Up (Second Edition)

You asked

How do I set up the game?

Answered counted as answered

Asked with: Camel Up (Second Edition)bg-260605-en-1e

1. Place the game board in the middle of the table [1]. 2. Sort the betting tickets by color (5 colors in total) [1]. 3. Stack the 4 tickets of each color by placing both -Pound tickets on the bottom, the -Pound ticket on top of them, and the -Pound ticket on the very top [1]. 4. Place each stack onto its matching ticket tent on the game board [1]. 5. Place the 5 pyramid tickets as a stack onto their space on the game board [1]. 6. Sort the Egyptian Pound coins by value and place them as a supply (the “bank”) next to the game board [1]. 7. Give each player 3 Egyptian Pounds to place in front of them [1]. 8. Give each player the 5 finish cards of one character and their character's spectator tile [1]. 9. Each player keeps their hand of five cards hidden from other players and places their spectator tile in front of them [1]. 10. In games with fewer than 6 players, leave partnership cards in the box [1]. 11. In games with 6 or more players, give each player his character's partnership card, placed in front of him with its “available” side face up [1]. 12. To determine the starting positions of the 5 racing camels, roll the 5 racing dice together once and place each racing camel onto the race track as indicated by the dice (a 1 places a camel on space 1, a 2 on space 2, and a 3 on space 3) [1][2]. 13. Stack all camels standing on the same space in any order and ensure they all face clockwise [1][2]. 14. Determine the starting positions of the 2 crazy camels (black and white) by rolling the grey die; place a camel onto the track as indicated by the number rolled (a white number moves the white camel, a black number moves the black camel) [1][3]. 15. If the second roll for a crazy camel results in the same space as the first, place the second camel on top of the first and ensure they face counterclockwise [2]. 16. Put the 5 racing dice into the pyramid by removing the cap and dropping them through the hole [2]. 17. Drop the grey die into the pyramid, put the cap back on, and place the pyramid onto its space on the game board [2]. 18. Give the starting player marker to the youngest player to begin the race [2].

[1] RULEBOOK Camel Up (Second Edition) — Rulebook · p.1 ·
[2] RULEBOOK Camel Up (Second Edition) — Rulebook · p.1 ·
[3] RULEBOOK Camel Up (Second Edition) — Rulebook · p.3 · place your spectator tile 2 · take 1 pyramid ticket 3 · how to use the pyramid · Example:
🔧 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 252 ms · ask 7848 ms · total 2089480 ms
single-flight (PR-5)
queued 2081372 ms · generation 8108 ms
retrieval refs (raw)
[{"page": 1, "score": 0.032787, "snippet": "8 5 3 2 1 -1 8 5 3 2 1 -1 8 5 3 2 1 -1 8 5 3 2 1 -1 8 5 3 2 1 -1 8 5 3 2 1 -1 8 5 3 2 1 -1 8 5 3 2 1 -1 1.1. Place the game board in the middle of the table. 2.2. Sort the betting tickets by color (5 colors in total). Then stack the 4 tickets of each color in the following manner: Place both -Pound ", "headingPath": "", "sharpsignalDocId": 181}, {"page": 1, "score": 0.032258, "snippet": "Then place each racing camel onto the race track as indicated by the dice: Finally, stack all camels standing on the same space (in any order) and make sure they all face clockwise (as this is the direction the race is run). 8.8. Now determine the starting positions of the 2 crazy camels (black and ", "headingPath": "", "sharpsignalDocId": 181}, {"page": 3, "score": 0.031746, "snippet": "Place your spectator tile onto an empty space of the race track (that has no camels or spectator tile on it). However, you are not allowed to place it onto a space that is adjacent to a space containing a spectator tile. Also, you may never place it onto space 1 of the race track. If your spectator ", "headingPath": "place your spectator tile 2 · take 1 pyramid ticket 3 · how to use the pyramid · Example:", "sharpsignalDocId": 181}, {"page": 4, "score": 0.03125, "snippet": "8 5 3 2 1 -1 8 5 3 2 5 3 2 As your action, you can bet on the overall winner. This means you secretly back the racing camel that you believe will be in the lead at the end of the game. To do this, secretly choose 1 of your finish cards (in the color of the camel you think will win) and put it face d", "headingPath": "spectator tiles · Bet on the overall winner or the overall loser · end of a leg", "sharpsignalDocId": 181}, {"page": 2, "score": 0.030769, "snippet": "Take the top betting ticket from any stack on the game board and place it in front of you. By doing this, you back the camel of that color (which means that you hope it will be in the lead at the end of the leg). There is no limit to the number of betting tickets you may collect throughout the leg. ", "headingPath": "take 1 Betting ticket · the legs · IMPORTANT: · end of the game · money", "sharpsignalDocId": 181}, {"page": 5, "score": 0.030303, "snippet": "In games with 6 or more players, each player also has a partnership card in front of him. On his turn, a player can now choose to perform a 5 th possible action called 'Enter into a betting partnership'. You can only perform this action if you have your partnership card with the 'available' side fac", "headingPath": "ADDITIONAL RULES IN GAMES WITH 6 OR MORE PLAYERS · enter into a Betting partnership 5", "sharpsignalDocId": 181}, {"page": 4, "score": 0.029851, "snippet": "As soon as any camel unit crosses the fi nish line , the race ends immediately (even if a crazy camel crosses the finish line in a counterclockwise direction). Now, carry out one more leg scoring round (as described on the left). Next, the end of game scoring round for the overall winner and overall", "headingPath": "end of the game · Example:", "sharpsignalDocId": 181}, {"page": 2, "score": 0.029412, "snippet": "8 8 5 3 5 3 8 8 This overview describes important basics of the game. Detailed rules will follow in the section 'Playing the game'. 2 1 8 5 5 3 5 3 -1 3 2 1 -1 3 2 1 -1 2 1 2 1 -1 The 5 racing camels do not belong to any player. Instead each player can bet on any of them throughout the race by acqui", "headingPath": "OVERVIEW · 8 5 the racing camels · Camel stack: · Camel unit: · the crazy camels · PLAYING THE GAME", "sharpsignalDocId": 181}]
citations (raw)
[{"page": 1, "quote": null, "headingPath": "", "sharpsignalDocId": 181}, {"page": 1, "quote": null, "headingPath": "", "sharpsignalDocId": 181}, {"page": 3, "quote": null, "headingPath": "place your spectator tile 2 · take 1 pyramid ticket 3 · how to use the pyramid · Example:", "sharpsignalDocId": 181}]
boost provenance — errata + base rulebook (E2/E3)
no registered errata card matched this query; base rulebook doc 181 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 181 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:45

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 Camel Up (Second Edition) — Rulebook (corpus doc 181) p.1 0.032787 (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 Camel Up (Second Edition) — Rulebook (corpus doc 181) p.1 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
#3 RULEBOOK Camel Up (Second Edition) — Rulebook (corpus doc 181) place your spectator tile 2 · take 1 pyramid ticket 3 · how to use the pyramid · Example: p.3 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
#4 RULEBOOK Camel Up (Second Edition) — Rulebook (corpus doc 181) spectator tiles · Bet on the overall winner or the overall loser · end of a leg p.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)) 300
#5 RULEBOOK Camel Up (Second Edition) — Rulebook (corpus doc 181) take 1 Betting ticket · the legs · IMPORTANT: · end of the game · money 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
#6 RULEBOOK Camel Up (Second Edition) — Rulebook (corpus doc 181) ADDITIONAL RULES IN GAMES WITH 6 OR MORE PLAYERS · enter into a Betting partnership 5 p.5 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
#7 RULEBOOK Camel Up (Second Edition) — Rulebook (corpus doc 181) end of the game · Example: 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
#8 RULEBOOK Camel Up (Second Edition) — Rulebook (corpus doc 181) OVERVIEW · 8 5 the racing camels · Camel stack: · Camel unit: · the crazy camels · PLAYING THE GAME p.2 0.029412 (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 Camel Up (Second Edition) — Rulebook (corpus doc 181) p.1 no quote on the wire
[2] RULEBOOK Camel Up (Second Edition) — Rulebook (corpus doc 181) p.1 no quote on the wire
[3] RULEBOOK Camel Up (Second Edition) — Rulebook (corpus doc 181) place your spectator tile 2 · take 1 pyramid ticket 3 · how to use the pyramid · Example: p.3 no quote on the wire
timing split
retrieval 252 ms · first delta 4014 ms · total 2089480 ms (retrieval and first-delta both measured from the START of gateway work, so first-delta INCLUDES retrieval — do not subtract)
full breakdown
queued 2081372 ms · retrieval 252 ms · ask 7848 ms · gateway work 8108 ms · total 2089480 ms
tokens in (the prompt the answerer read)
4550
tokens out (what the answerer generated)
556
tok/sec
137.4 tok/sec — 556 output tokens in 4.048 s of generation
live seat (read from the running child)
answering — gemma4:26b think:false · num_ctx 32768 (live-verified 52s 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 99), 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.