Ruling — Ticket to Ride: Märklin

You asked

What needs to be placed on the table before the first round begins?

Answered counted as answered

Asked with: Ticket to Ride: Märklinbg-21348-en-1e

To set up the game before the first round begins, follow these steps: 1. Place the board in the center of the table [1]. 2. Create stacks of Tokens with the highest number on top and the lowest number on the bottom (one stack of black Tokens, six stacks of red Tokens, twelve stacks of Yellow Tokens, and sixteen independent white Tokens) and place these different stacks on the corresponding cities [1]. 3. Each player takes a set of 45 Colored Train Cars, matching Passengers, and a Scoring Marker [2]. 4. Each player places their Scoring Marker on "Start" on the Scoring Track [2]. 5. Shuffle the Train Car Cards, deal a starting hand of 4 cards to each player, place the remaining deck near the board, and turn the top five cards from the deck face-up [2]. 6. Place the Most Completed Tickets Bonus Tile face up next to the board [2]. 7. Separate the Destination Ticket decks into one stack of short routes (Blue background) and a second stack of long routes (Brown background), and place each next to the board [2]. 8. Each player draws four Tickets, decides which ones to keep (keeping at least two), and places unwanted tickets back into their respective stacks [2]. 9. Reshuffle the two stacks and place the two separate decks of short and long Destination Tickets next to the board [2].

[1] RULEBOOK Ticket to Ride: Märklin — Rulebook · p.2 · COMPONENTS · IMPORTANT NOTE · SETTING UP THE GAME

[2] RULEBOOK Ticket to Ride: Märklin — Rulebook · p.3 · SETTING UP THE GAME · OBJECT OF THE GAME

🔧 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 262 ms · ask 5058 ms · total 57484 ms
single-flight (PR-5): queued 52154 ms · generation 5330 ms
retrieval refs (raw): [{"page": 3, "score": 0.032787, "snippet": "The player who has the best collection of Märklin trains or is the youngest player goes first. Play then proceeds clockwise around the table, each player taking one turn at a time until the game ends. On his turn, a player must perform one (and only one) of the following four actions: 1. Draw Cards ", "headingPath": "THE GAME TURN", "sharpsignalDocId": 537}, {"page": 3, "score": 0.032258, "snippet": "Each player takes a set of 45 Colored Train Cars along with the matching Passengers and Scoring Marker ❸ . Each player places his Scoring Marker on Start ❹ on the Scoring Track running along the map's border. Throughout the game, each time a player scores points, he will advance his marker according", "headingPath": "SETTING UP THE GAME · OBJECT OF THE GAME", "sharpsignalDocId": 537}, {"page": 6, "score": 0.031746, "snippet": "Players should have already accounted for the points earned as they completed different routes and collected various Merchandise tokens. To make sure no mistakes were made, you may want to re-count the points for each player's routes and Merchandise tokens collected by Passengers. Players should the", "headingPath": "Calculating Scores", "sharpsignalDocId": 537}, {"page": 5, "score": 0.03125, "snippet": "A route is a set of continuous colored spaces (in some instances, gray spaces) between two adjacent cities on the map. To claim a route, a player must play a set of Train Cards whose color and quantity match the color and number of spaces of the chosen route. A set of cards must be of the same type.", "headingPath": "CLAIMING ROUTES · IMPORTANT NOTE", "sharpsignalDocId": 537}, {"page": 6, "score": 0.030769, "snippet": "A player can use his turn to draw more Destination Ticket Cards. To do so, he draws 4 new cards from the top of the two Destination Ticket Decks. A player may draw any combination of the two types of Tickets, but he must first announce what combination of Tickets he is drawing. If there are less tha", "headingPath": "DRAWING DESTINATION TICKET CARDS · GAME END", "sharpsignalDocId": 537}, {"page": 4, "score": 0.030303, "snippet": "A player may have any number of cards in his hand at one time. When the deck is exhausted, the discards are reshuffled into a new draw pile deck. The cards should be shuffled thoroughly, since all the cards have been discarded in sets. In the unlikely event that there are no cards left in the deck a", "headingPath": "TRAIN CAR AND PASSENGER CARDS · Train cards · Locomotive cards · Locomotive + 4+ Cards · Passenger Cards", "sharpsignalDocId": 537}, {"page": 2, "score": 0.029851, "snippet": "◆ 1 Board map of Germany with train routes ◆ 240 Colored Train Cars (45 each in White, Red, Purple, Yellow and Black, plus 3 extra \"replacement\" cars in each color) ◆ 165 Illustrated cards: 118 Train Car cards - 11 each of Blue, Red, Green, Yellow, Black, Purple, White and Orange 14 Locomotives 6 Lo", "headingPath": "COMPONENTS · IMPORTANT NOTE · SETTING UP THE GAME", "sharpsignalDocId": 537}, {"page": 7, "score": 0.029412, "snippet": "Learn more at www.daysofwonder.com A ll aboard this computer game version of the famous award-winning board game : Ticket to Ride! Play against the game on the classic US and European maps, and discover the exclusive map of Switzerland. Play online against tens of thousand of other players all over ", "headingPath": "Mac OSX and PC Windows", "sharpsignalDocId": 537}]
citations (raw): [{"page": 2, "quote": null, "headingPath": "COMPONENTS · IMPORTANT NOTE · SETTING UP THE GAME", "sharpsignalDocId": 537}, {"page": 3, "quote": null, "headingPath": "SETTING UP THE GAME · OBJECT OF THE GAME", "sharpsignalDocId": 537}]
boost provenance — errata + base rulebook (E2/E3): no registered errata card matched this query; base rulebook doc 537 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 537 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 7, 2026 08:03

retrieval — what the search arm returned

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 Ticket to Ride: Märklin — Rulebook (corpus doc 537)	THE GAME TURN	p.3	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 Ticket to Ride: Märklin — Rulebook (corpus doc 537)	SETTING UP THE GAME · OBJECT OF THE GAME	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
#3	RULEBOOK Ticket to Ride: Märklin — Rulebook (corpus doc 537)	Calculating Scores	p.6	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 Ticket to Ride: Märklin — Rulebook (corpus doc 537)	CLAIMING ROUTES · IMPORTANT NOTE	p.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))	300
#5	RULEBOOK Ticket to Ride: Märklin — Rulebook (corpus doc 537)	DRAWING DESTINATION TICKET CARDS · GAME END	p.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))	300
#6	RULEBOOK Ticket to Ride: Märklin — Rulebook (corpus doc 537)	TRAIN CAR AND PASSENGER CARDS · Train cards · Locomotive cards · Locomotive + 4+ Cards · Passenger Cards	p.4	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 Ticket to Ride: Märklin — Rulebook (corpus doc 537)	COMPONENTS · IMPORTANT NOTE · SETTING UP THE GAME	p.2	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 Ticket to Ride: Märklin — Rulebook (corpus doc 537)	Mac OSX and PC Windows	p.7	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

chosen chunks — what the answer actually cited

#	document	heading	page	quote chars
[1]	RULEBOOK Ticket to Ride: Märklin — Rulebook (corpus doc 537)	COMPONENTS · IMPORTANT NOTE · SETTING UP THE GAME	p.2	no quote on the wire
[2]	RULEBOOK Ticket to Ride: Märklin — Rulebook (corpus doc 537)	SETTING UP THE GAME · OBJECT OF THE GAME	p.3	no quote on the wire

generation — timing and the path taken

timing split: retrieval 262 ms · first delta 3104 ms · total 57484 ms (retrieval and first-delta both measured from the START of gateway work, so first-delta INCLUDES retrieval — do not subtract)
full breakdown: queued 52154 ms · retrieval 262 ms · ask 5058 ms · gateway work 5330 ms · total 57484 ms
tokens in (the prompt the answerer read): 3008
tokens out (what the answerer generated): 296
tok/sec: 136.8 tok/sec — 296 output tokens in 2.163 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 55s 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: 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 469), 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.