Ruling — Five Tribes: The Djinns of Naqala

You asked

How do I set up the game?

Answered counted as answered

Asked with: Five Tribes: The Djinns of Naqalabg-157354-en-1e

1. If this is the first play, punch out all the pieces from the game's punchboards.[1]

2. Insert empty frames under the vacuum tray inside the game box to help the tray stay flush with the box top.[1]

3. In 3- and 4-player games, each player takes 8 Camels and 1 Turn marker of his choice; in 2-player games, one player takes all 11 Pink Camels and 2 Turn markers, and the other takes all 11 Blue Camels and 2 Turn markers.[1]

4. In 2-player games, each player also gets 50 Gold Coins (9 coins worth '5' each + 5 worth '1' each).[1]

5. Players should keep the value of their held Gold Coins face down until the end of the game.[1]

6. Mix all 30 Tiles and place them randomly face up to form a 5 x 6 rectangle called the Sultanate.[1]

7. Mix all 90 wooden Meeples in the bag, then grab and drop them in random sets of 3 on each Tile.[1]

8. Place the Bid Order & Turn Order Tracks next to the Sultanate.[1]

9. Randomly place the players' Turn markers on the Bid Order track.[1]

10. Shuffle all Resource cards to form a face down draw pile, then draw the top 9 cards and lay them face up in a row next to the draw pile.[1]

11. Shuffle the Djinns' cards and set them face down in a draw pile, then draw the top 3 and lay them face up next to the draw pile.[1]

12. Place the Palm Trees, Palaces and all remaining Gold Coins in a bank within easy reach of the players.[1]

[1] RULEBOOK Five Tribes: The Djinns of Naqala — Rulebook · p.2 · Settingupthegame

🔧 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 89 ms · ask 4441 ms · total 4531 ms
single-flight (PR-5): queued 0 ms · generation 4531 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read: [{"page": 2, "score": 0.04918, "snippet": "If this is the first play, punch out all the pieces from the game's punchboards. Rather than discarding the empty frames, insert them under the vacuum tray inside your game box. This will help your tray stay flush with your game's box top, preventing pieces inside from spilling over when storing you", "headingPath": "Settingupthegame", "sharpsignalDocId": 285}, {"page": 4, "score": 0.032258, "snippet": "Once his/her turn comes up, each player takes all of the following actions, before letting the next Turn Marker owner play: Take your Turn Marker off the Turn Order Track and place it onto the first empty spot on the Bid Order Track. Note: If you go first, this means you will also bid first for Turn", "headingPath": "2. Player's Actions · 2.1 Move Turn Marker · 2.2 Move Meeples", "sharpsignalDocId": 285}, {"page": 8, "score": 0.031746, "snippet": "We invite you to join our online community of players at Days of Wonder Online, where we host a number of online versions of our games. To use your Days of Wonder Online number, add it to your existing Days of Wonder Online account or create a new account at: www.daysofwonder.com/five-tribes and cli", "headingPath": "Days of Wonder Online", "sharpsignalDocId": 285}, {"page": 3, "score": 0.03125, "snippet": "The player whose Turn marker is in first position (spot marked '1') on the Bid Order track goes first and announces which spot of the Turn Order Track she wishes to place her Turn Marker on; she immediately pays to the bank the amount of Gold Coins indicated on that spot, and places her Turn Marker ", "headingPath": "1. Bid for Turn Order", "sharpsignalDocId": 285}, {"page": 3, "score": 0.030769, "snippet": "There can never be more than 3 Turn Markers placed on '0's, so if all three '0's are taken, the last player must bid at least 1 (and will get to play first, this turn!). Players take their turn based on the position of their Markers on the Turn Order Track, with the highest value Markers going first", "headingPath": "1. Bid for Turn Order", "sharpsignalDocId": 285}, {"page": 5, "score": 0.030303, "snippet": "Once you finish moving the Meeples, take the last Meeple you dropped on the final Tile back in your hand, along with ALL other Meeples of same color that were already on that Tile before your move. You should now have at least 2 Meeples of identical color in your hand: the one you dropped last, and ", "headingPath": "2.3 Tile Control Check · 2.4 Tribes Actions · Yellow Viziers Tribe · White Elders Tribe", "sharpsignalDocId": 285}, {"page": 3, "score": 0.029851, "snippet": "In Five Tribes, you play the role of a stranger venturing into the legendary city-state of Naqala to maneuver the local Tribes, invoke old Djinns and gain influence. At the end of the game, the player with the most Victory Points is declared The Great Sultan and wins. You score Victory Points (VPs) ", "headingPath": "Object of the game · Victory Points · Gameturn", "sharpsignalDocId": 285}, {"page": 5, "score": 0.029412, "snippet": "Taking all the Meeples from the Small Market tile in hand, the player then drops a green Meeple on the Oasis (1), a blue Meeple on the Big Market (2), a red Meeple on the Sacred Place (3), a yellow Meeple on the Small Market (4), and the last green Meeple on the Oasis (5). This move let the player r", "headingPath": "There are 3 rules you must respect while moving these Meeples:", "sharpsignalDocId": 285}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show: [{"page": 2, "quote": null, "headingPath": "Settingupthegame", "sharpsignalDocId": 285}]
boost provenance — errata + base rulebook (E2/E3): no registered errata card matched this query; base rulebook doc 285 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 285 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.88412 of 1096 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row retained until: Nov 12, 2026 18:38

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 Five Tribes: The Djinns of Naqala — Rulebook (corpus doc 285)	Settingupthegame	p.2	0.04918 (at the 3-arm ceiling (0.04918) — every arm ranked it #1)	300
#2	RULEBOOK Five Tribes: The Djinns of Naqala — Rulebook (corpus doc 285)	2. Player's Actions · 2.1 Move Turn Marker · 2.2 Move Meeples	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
#3	RULEBOOK Five Tribes: The Djinns of Naqala — Rulebook (corpus doc 285)	Days of Wonder Online	p.8	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 Five Tribes: The Djinns of Naqala — Rulebook (corpus doc 285)	1. Bid for Turn Order	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 Five Tribes: The Djinns of Naqala — Rulebook (corpus doc 285)	1. Bid for Turn Order	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
#6	RULEBOOK Five Tribes: The Djinns of Naqala — Rulebook (corpus doc 285)	2.3 Tile Control Check · 2.4 Tribes Actions · Yellow Viziers Tribe · White Elders Tribe	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 Five Tribes: The Djinns of Naqala — Rulebook (corpus doc 285)	Object of the game · Victory Points · Gameturn	p.3	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 Five Tribes: The Djinns of Naqala — Rulebook (corpus doc 285)	There are 3 rules you must respect while moving these Meeples:	p.5	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 16 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 Five Tribes: The Djinns of Naqala — Rulebook (corpus doc 285)	Settingupthegame	p.2	#1	0.04918 (at the 3-arm ceiling (0.04918) — every arm ranked it #1)	vector + full-text + the doc-priority boost arm	the re-ranker chose it
#2	RULEBOOK Five Tribes: The Djinns of Naqala — Rulebook (corpus doc 285)	1. Bid for Turn Order	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
#3	RULEBOOK Five Tribes: The Djinns of Naqala — Rulebook (corpus doc 285)	There are 3 rules you must respect while moving these Meeples:	p.5	#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
#4	RULEBOOK Five Tribes: The Djinns of Naqala — Rulebook (corpus doc 285)	Object of the game · Victory Points · Gameturn	p.3	#7	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))	vector + the doc-priority boost arm	the re-ranker chose it
#5	RULEBOOK Five Tribes: The Djinns of Naqala — Rulebook (corpus doc 285)	1. Bid for Turn Order	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
#6	RULEBOOK Five Tribes: The Djinns of Naqala — Rulebook (corpus doc 285)	Days of Wonder Online	p.8	#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))	vector + the doc-priority boost arm	the re-ranker chose it
#7	RULEBOOK Five Tribes: The Djinns of Naqala — Rulebook (corpus doc 285)	3. Clean-Up · ✦ Replenish the row of Resource cards: · ✦ Replenish the row of Djinns cards:	p.7	#10	0.014286 (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
#8	RULEBOOK Five Tribes: The Djinns of Naqala — Rulebook (corpus doc 285)	2. Player's Actions · 2.1 Move Turn Marker · 2.2 Move Meeples	p.4	#2	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

chosen chunks — what the answer actually cited

#	document	heading	page	quote chars
[1]	RULEBOOK Five Tribes: The Djinns of Naqala — Rulebook (corpus doc 285)	Settingupthegame	p.2	no quote on the wire

generation — timing and the path taken

timing split: retrieval 89 ms · first delta 1690 ms · total 4531 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 89 ms · ask 4441 ms · gateway work 4531 ms · total 4531 ms
tokens in (the prompt the answerer read): 2468
tokens out (what the answerer generated): 395
tok/sec: 140.8 tok/sec — 395 output tokens in 2.806 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 23s 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.

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): set up

errata registry — what the gate above had to match against

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