RuleSage cited table rulings
← Detective: A Modern Crime Board Game

You asked

How should we prepare everything before the first turn?

Answered counted as answered

Asked with: Detective: A Modern Crime Board Gamebg-223321-en-1e

To prepare for each case, follow these steps: 1. Place the board on the table within reach of all players [1]. 2. Place the Investigation Team marker (or IT marker) on the Headquarters Location [1]. 3. Place the Time marker on the 8:00 AM space of the Time track [1]. 4. Place the Day marker on the day 1 space of the Day track [1]. 5. Give each player the investigator tile of their choice, placing it face up [1]. 6. Collect the Skill token depicted in the bottom right-hand corner of your chosen investigator tile [1]. 7. Turn any unused investigator tiles to their Consultant side and collect the Skill tokens depicted on those tiles [1]. 8. Create a Token pool using all Skill tokens provided by investigators and consultants [1]. 9. Log into the Antares website at antaresdatabase.com, then choose your campaign and the case [1]. 10. Place the case deck next to the board [1]. 11. Open the casebook and read the introduction to the case, special rules, and set-up changes [1]. 12. Ensure you have plenty of space for notes and/or a mind map (using a whiteboard or bulletin board if available) [1]. 13. Ensure an Internet browser is within reach to search for case-related information [1].

[1] RULEBOOK Detective: A Modern Crime Board Game — Rulebook · p.4 · ▸ TO SET UP FOR EACH CASE:
🔧 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 195 ms · ask 8634 ms · total 45195 ms
single-flight (PR-5)
queued 36355 ms · generation 8840 ms
retrieval refs (raw)
[{"page": 13, "score": 0.032787, "snippet": "It's good to spend a few minutes at the end of a case to summarize the most important facts, names, and theories that you had during the game. This will be very helpful when you continue the game after a few days - or weeks! After all, approaching the next case with only a vague memory of the previo", "headingPath": "#playtestingtip", "sharpsignalDocId": 437}, {"page": 9, "score": 0.032258, "snippet": "You can spend one Perception Skill token to analyze the evidence mentioned in the file. You have to decide now, if you are going to Dig Deeper or not. If you do, read the back side, follow any instructions there and go to the next step. If you don’t, go to the next step. Note any further leads to ke", "headingPath": "", "sharpsignalDocId": 437}, {"page": 9, "score": 0.031746, "snippet": "First, you draw the appropriate card . Look through the deck for it without reading anything but the numbers at the top of the cards. In this example, you are looking for card #336. You update your Location. If you were in any other Location than Richmond PD you would have to move your IT marker the", "headingPath": "card resolution example", "sharpsignalDocId": 437}, {"page": 2, "score": 0.03125, "snippet": "Each case has many paths to completion. Due to time constraints, you will never see the whole deck or discover all of the clues. In fact, the average number of cards drawn in each case is about twenty! After finishing the game, don't be disappointed that you didn't go through the entire deck. This i", "headingPath": "▶ Solving cases without a full deck · ▶ There is no 'You Won' card · #playtestingtip", "sharpsignalDocId": 437}, {"page": 4, "score": 0.030769, "snippet": "Place the board on the table within reach of all players. Place the Investigation Team marker (or IT marker) on the Headquarters Location. Place the Time marker on the 8:00 AM space of the Time track. Place the Day marker on the day 1 space of the Day track. Give each player the investigator tile of", "headingPath": "▸ TO SET UP FOR EACH CASE:", "sharpsignalDocId": 437}, {"page": 8, "score": 0.030303, "snippet": "At the beginning of a case, the 'Further Leads' section in the casebook will present a list of lead cards. You can Follow Leads in any order you wish, and you can ignore any that you don't wish to follow. However, once you draw a lead card, you MUST resolve it; you may NOT check the hour value and S", "headingPath": "▸ FOLLOW A LEAD · ▶ further leads · ▶ Spending authority tokens · IN ANY ORDER, YOU MAY TAKE ANY OF THESE AVAILABLE ACTIONS AS A TEAM:", "sharpsignalDocId": 437}, {"page": 5, "score": 0.029851, "snippet": "You have a limited number of days, i.e. game rounds, in which to learn as much as possible about a case and achieve the stated goal. Once you run out of days, navigate to that case's 'Final Report' on the Antares website and attempt to answer questions related to it. Your answers will determine your", "headingPath": "▸ SUMMARY · ▶ Days and hours · #playtestingtip · ▶ Daily activity", "sharpsignalDocId": 437}, {"page": 9, "score": 0.029412, "snippet": "Lead cards are double-sided. The Dig Deeper action allows you to reveal additional information by reading the back side of the lead card. To Dig Deeper, you must spend the token depicted in the Dig Deeper section of the card. After you do so, flip the card over, read it, note Further Leads, etc. Exa", "headingPath": "▸ DIG DEEPER · #playtestingtip", "sharpsignalDocId": 437}]
citations (raw)
[{"page": 4, "quote": null, "headingPath": "▸ TO SET UP FOR EACH CASE:", "sharpsignalDocId": 437}]
boost provenance — errata + base rulebook (E2/E3)
no registered errata card matched this query; base rulebook doc 437 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 437 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 05:03

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 Detective: A Modern Crime Board Game — Rulebook (corpus doc 437) #playtestingtip p.13 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 Detective: A Modern Crime Board Game — Rulebook (corpus doc 437) p.9 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 Detective: A Modern Crime Board Game — Rulebook (corpus doc 437) card resolution example p.9 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 Detective: A Modern Crime Board Game — Rulebook (corpus doc 437) ▶ Solving cases without a full deck · ▶ There is no 'You Won' card · #playtestingtip 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
#5 RULEBOOK Detective: A Modern Crime Board Game — Rulebook (corpus doc 437) ▸ TO SET UP FOR EACH CASE: p.4 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 Detective: A Modern Crime Board Game — Rulebook (corpus doc 437) ▸ FOLLOW A LEAD · ▶ further leads · ▶ Spending authority tokens · IN ANY ORDER, YOU MAY TAKE ANY OF THESE AVAILABLE ACTIONS AS A TEAM: p.8 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 Detective: A Modern Crime Board Game — Rulebook (corpus doc 437) ▸ SUMMARY · ▶ Days and hours · #playtestingtip · ▶ Daily activity p.5 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 Detective: A Modern Crime Board Game — Rulebook (corpus doc 437) ▸ DIG DEEPER · #playtestingtip p.9 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 Detective: A Modern Crime Board Game — Rulebook (corpus doc 437) ▸ TO SET UP FOR EACH CASE: p.4 no quote on the wire
timing split
retrieval 195 ms · first delta 6274 ms · total 45195 ms (retrieval and first-delta both measured from the START of gateway work, so first-delta INCLUDES retrieval — do not subtract)
full breakdown
queued 36355 ms · retrieval 195 ms · ask 8634 ms · gateway work 8840 ms · total 45195 ms
tokens in (the prompt the answerer read)
4196
tokens out (what the answerer generated)
297
tok/sec
117.6 tok/sec — 297 output tokens in 2.526 s of generation
live seat (read from the running child)
answering — gemma4:26b think:false · num_ctx 32768 (live-verified 31s 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
NOT_SETUP_SHAPED — no setup-shape pattern matched this question

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