Ruling — Camel Up (Second Edition)

You asked

How do I play?

Answered counted as answered

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

Setup

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 1-Pound tickets on the bottom, the 2-Pound ticket on top of them, and the 3-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 and board.[1]

6. Sort the Egyptian Pound coins by value and place them as a "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 5 finish cards of one character and their character's spectator tile.[1]

9. Each player keeps their hand of five cards hidden and places their spectator tile in front of them.[1]

10. In games with 6 or more players, give each player their character's partnership card with the “available” side face up.[1]

11. Determine the starting positions of the 5 racing camels by rolling the 5 racing dice together once and placing each camel on the track as indicated by the dice.[1][2]

12. Stack all camels standing on the same space (in any order) and ensure they all face clockwise.[1][2]

13. Determine the starting positions of the 2 crazy camels (black and white) by rolling the grey die and placing them on the track as indicated.[1][2]

14. If the grey die roll places the second crazy camel on the same space as the first, put the second camel on top of the first.[2]

15. Ensure crazy camels face counterclockwise.[2]

16. Put the 5 racing dice into the pyramid and drop the grey die into the pyramid.[2]

17. Give the starting player marker to the youngest player.[2]

Playing the Game

The race comprises several legs.[3] A leg ends when 5 of the 6 dice have been revealed from the pyramid.[3] Play proceeds continuously in a clockwise direction.[4] The player with the starting player marker begins the first leg by performing 1 action.[4] Then the player to his left performs 1 action, and so on.[4] When it is your turn, you must choose and perform 1 of the following 4 possible actions:[4]

1. Take 1 Betting ticket: Take the top betting ticket from any stack on the game board to back the camel of that color.[4][3]

2. Take 1 pyramid ticket: Take the top pyramid ticket from the stack on the game board, then immediately shake the pyramid and reveal one die.[5]

* If a racing die is revealed, move the camel of its color forward as many spaces as shown (1, 2, or 3).[5]

* If a camel that is part of a stack moves, it carries all camels on top of it.[4][5]

* If the grey die is revealed, move the white camel if the die shows a white number, or the black camel if it shows a black number.[5]

3. Place your spectator tile: Place your spectator tile onto an empty space on the race track that is not adjacent to another spectator tile and is not space 1.[5] You may also use this action to move an existing tile.[5] You can place it with its cheering side or booing side up.[5]

4. Bet on the overall winner or overall loser: Secretly choose 1 of your finish cards and place it face down onto the betting space for the overall winner or the overall loser.[6]

Additional Action (6+ players only):

* Enter into a betting partnership: If you have your partnership card with the "available" side face up, you can choose another player who also has their card "available".[7] Exchange cards so that you both have the other's card with the "partnership" side face up.[7] You are now betting partners for the remainder of the leg.[7]

Scoring

End of a Leg:

A leg scoring round occurs after the last pyramid ticket is taken.[6]

1. The starting player marker is given to the player to the $left$ of the player who took the last ticket.[6]

2. Players receive or lose money according to the tickets acquired during the leg.[3]

3. (For betting partners): Each partner may choose one ticket belonging to their partner and add its reward to their own.[7]

4. All partnership cards

[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.2 · take 1 Betting ticket · the legs · IMPORTANT: · end of the game · money

[4] RULEBOOK Camel Up (Second Edition) — Rulebook · p.2 · OVERVIEW · 8 5 the racing camels · Camel stack: · Camel unit: · the crazy camels · PLAYING THE GAME

[5] RULEBOOK Camel Up (Second Edition) — Rulebook · p.3 · place your spectator tile 2 · take 1 pyramid ticket 3 · how to use the pyramid · Example:

[6] RULEBOOK Camel Up (Second Edition) — Rulebook · p.4 · spectator tiles · Bet on the overall winner or the overall loser · end of a leg

[7] RULEBOOK Camel Up (Second Edition) — Rulebook · p.5 · ADDITIONAL RULES IN GAMES WITH 6 OR MORE PLAYERS · enter into a Betting partnership 5

Answer in hand — your move.

🔧 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 175 ms · ask 9870 ms · total 10048 ms
single-flight (PR-5): queued 0 ms · generation 10048 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read: [{"page": 2, "score": 0.046696, "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}, {"page": 5, "score": 0.032787, "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": 3, "score": 0.032258, "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.031746, "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.03125, "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": 1, "score": 0.030769, "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": 4, "score": 0.029851, "snippet": "Now, each player gains or loses Egyptian Pounds according to the tickets in front of him, by adding up his total and then taking it from (or paying it to) the bank accordingly. 8 5 3 2 1 -1 For each betting ticket of the leading racing camel, the player gains the number of Egyptian Pounds printed in", "headingPath": "remember: The crazy camels are entirely ignored for the ranking.", "sharpsignalDocId": 181}, {"page": 4, "score": 0.029412, "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}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show: [{"page": 1, "quote": null, "headingPath": "", "sharpsignalDocId": 181}, {"page": 1, "quote": null, "headingPath": "", "sharpsignalDocId": 181}, {"page": 2, "quote": null, "headingPath": "take 1 Betting ticket · the legs · IMPORTANT: · end of the game · money", "sharpsignalDocId": 181}, {"page": 2, "quote": null, "headingPath": "OVERVIEW · 8 5 the racing camels · Camel stack: · Camel unit: · the crazy camels · PLAYING THE GAME", "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}, {"page": 4, "quote": null, "headingPath": "spectator tiles · Bet on the overall winner or the overall loser · end of a leg", "sharpsignalDocId": 181}, {"page": 5, "quote": null, "headingPath": "ADDITIONAL RULES IN GAMES WITH 6 OR MORE PLAYERS · enter into a Betting partnership 5", "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)
answer fence: passed — letter density 0.89391 of 3299 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row recorded: Aug 24, 2026 17:40 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 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.046696 (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)	ADDITIONAL RULES IN GAMES WITH 6 OR MORE PLAYERS · enter into a Betting partnership 5	p.5	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
#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.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 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.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
#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.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
#6	RULEBOOK Camel Up (Second Edition) — Rulebook (corpus doc 181)		p.1	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 Camel Up (Second Edition) — Rulebook (corpus doc 181)	remember: The crazy camels are entirely ignored for the ranking.	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)	end of the game · Example:	p.4	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

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 15 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 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	#2	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))	vector + the doc-priority boost arm	the re-ranker chose it
#2	RULEBOOK Camel Up (Second Edition) — Rulebook (corpus doc 181)		p.1	#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
#3	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	#1	0.046696 (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
#4	RULEBOOK Camel Up (Second Edition) — Rulebook (corpus doc 181)	end of the game · Example:	p.4	#8	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))	vector + the doc-priority boost arm	the re-ranker chose it
#5	RULEBOOK Camel Up (Second Edition) — Rulebook (corpus doc 181)		p.1	#9	0.014493 (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
#6	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	#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))	vector + the doc-priority boost arm	the re-ranker chose it
#7	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	#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
#8	RULEBOOK Camel Up (Second Edition) — Rulebook (corpus doc 181)	take 1 Betting ticket · the legs · IMPORTANT: · end of the game · money	p.2	#5	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

chosen chunks — what the answer actually cited

#	document	heading	page	quote 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)	take 1 Betting ticket · the legs · IMPORTANT: · end of the game · money	p.2	no quote on the wire
[4]	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	no quote on the wire
[5]	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
[6]	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	no quote on the wire
[7]	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	no quote on the wire

generation — timing and the path taken

timing split: retrieval 175 ms · first delta 2128 ms · total 10048 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 175 ms · ask 9870 ms · gateway work 10048 ms · total 10048 ms
tokens in (the prompt the answerer read): 4547
tokens out (what the answerer generated): 1024
tok/sec: 131.2 tok/sec — 1024 output tokens in 7.807 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 23s ago)
answerer host (measured by rulesage): reachable (for 23h, checked 5s 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 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.