RuleSage cited table rulings
← Mythos Tales

You asked

How do I play?

Answered counted as answered

Asked with: Mythos Talesbg-126100-en-1e

The game is played in two separate phases: the Investigation Phase and the Solution Phase.[1]
Investigation Phase
Beginning with the first player, each player in turn follows these steps until it is time to move to the Solution Phase:
1. Travel Step: All players first discuss which location should be visited next, though the active player can choose any location they desire.[2] The lead player selects a location using a letter and number combination, which can be found using the map of Arkham, the directory, or the ally list.[3][4] After selecting a location, the player advances the Time-Tracker by moving the Progress marker one space down (if it is Morning or Afternoon) or across to the Morning of the next Day (if it is Evening).[3] On the players' first turn, instead of advancing, the Progress marker is placed on Morning of Day 1.[3][5]
2. Encounter Step: The active player reads aloud the encounter from the Investigation Book based on the location coordinate.[5] If there is no entry for the chosen location, there are no relevant clues, and the same player may select another location, which requires advancing the Progress marker another space.[5] If an entry is found, players follow all directions in the text, which may include unexpected actions, such as advancing the Time-Tracker an additional space or checking for Requirement cards.[6]
Players may voluntarily end their investigation at any time before the Progress marker advances to the 'X' space on the Time-Tracker to avoid penalties.[1]
Solution Phase
Once the investigation ends, players proceed through the following steps in order:
1. Question and Answer Step: Players, usually as a group by consensus, decide on the best answer for each question listed in the investigation's Questions section based on notes and recalled information.[6] Players may not reread any materials in the book or newspapers during this step.[6]
2. Scoring Step: Players determine their score by comparing their answers to the ones found in the Answers section.[7] Players also assess and deduct points for various penalties, such as sanity penalties, points for excess time (if the Progress marker was advanced beyond the 'X'), or points for visiting more locations than Armitage.[7][8]
[1] RULEBOOK Mythos Tales — Rulebook · p.4 · SETUP · GAMEPLAY · Investigation Phase · 1. Travel Step 2. Encounter Step
[2] RULEBOOK Mythos Tales — Rulebook · p.4 · Travel Step
[3] RULEBOOK Mythos Tales — Rulebook · p.5 · Travel Step
[4] RULEBOOK Mythos Tales — Rulebook · p.2 · OVERVIEW
[5] RULEBOOK Mythos Tales — Rulebook · p.5 · Encounter Step · Encounter Step continued
[6] RULEBOOK Mythos Tales — Rulebook · p.6 · Encounter Step continued · SOLUTION PHASE · Question and Answer Step · Record-Keeping
[7] RULEBOOK Mythos Tales — Rulebook · p.6 · Scoring Step
[8] RULEBOOK Mythos Tales — Rulebook · p.7 · Scoring Step

That settles it — whose turn was it?

🔧 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 107 ms · ask 3889 ms · total 3998 ms
single-flight (PR-5)
queued 0 ms · generation 3998 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read
[{"page": 4, "score": 0.047643, "snippet": "To prepare to play a Mythos Tales investigation, follow the instructions in this section. Although players may select any investigation they wish to play in any order, it is recommended they play investigations in order, starting with A Grain of Evil. Choose an investigation to play and open the boo", "headingPath": "SETUP · GAMEPLAY · Investigation Phase · 1.\t Travel Step 2.\t Encounter Step", "sharpsignalDocId": 1261}, {"page": 5, "score": 0.046432, "snippet": "After the active player announces the location that the group will travel and advances the Time-Tracker, they then read aloud the encounter based on the location coordinate. The letter represents a district in Arkham. The number indicates a specific lot or building or room within a building. It is w", "headingPath": "Encounter Step · Encounter Step continued", "sharpsignalDocId": 1261}, {"page": 4, "score": 0.032787, "snippet": "In this step, all players first discuss what location they think should be visited next. However, it should be noted that a majority vote is not necessary. The active player can go to any location he or she desires.", "headingPath": "Travel Step", "sharpsignalDocId": 1261}, {"page": 6, "score": 0.032258, "snippet": "In the Scoring Step players determine their score by comparing their answers to the ones found in the Answers section. They also assess sanity penalties to their score as well as penalties for not being as efficient as Armitage, as revealed in the 'Path of Armitage.' Armitage's path will not always ", "headingPath": "Scoring Step", "sharpsignalDocId": 1261}, {"page": 5, "score": 0.031746, "snippet": "In order to find a location coordinate, which usually consists of a single letter followed by a number, the player can use the map of Arkham, the directory, or the ally list on the back of this game manual. There are some situations where there is no reference from a lead to look up in the directory", "headingPath": "Travel Step", "sharpsignalDocId": 1261}, {"page": 2, "score": 0.030769, "snippet": "After reading the introduction of an investigation aloud, players take turns choosing a lead player to continue the investigation. The lead player selects a letter and number combination of a location they hope is pertinent to the case. Players, as a group and in cooperative manner, then 'travel' to", "headingPath": "OVERVIEW", "sharpsignalDocId": 1261}, {"page": 7, "score": 0.030366, "snippet": "Sanity Penalties section. This section might assess a penalty to your score if you visited a particularly dangerous or haunting place. Many things you see cannot be unseen so be careful where you go! Excess Time : In the unlikely event an encounter forced players to advance the Progress marker beyon", "headingPath": "Scoring Step", "sharpsignalDocId": 1261}, {"page": 6, "score": 0.029851, "snippet": "No Location Coordinate in Book: It is important to note that if players travel to a location without an encounter, they do not count that location in the final count of locations when scoring penalties at the end of the investigation. This is important to remember. It is also important to note that ", "headingPath": "Encounter Step continued · SOLUTION PHASE · Question and Answer Step · Record-Keeping", "sharpsignalDocId": 1261}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show
[{"page": 4, "quote": null, "headingPath": "SETUP · GAMEPLAY · Investigation Phase · 1.\t Travel Step 2.\t Encounter Step", "sharpsignalDocId": 1261}, {"page": 4, "quote": null, "headingPath": "Travel Step", "sharpsignalDocId": 1261}, {"page": 5, "quote": null, "headingPath": "Travel Step", "sharpsignalDocId": 1261}, {"page": 2, "quote": null, "headingPath": "OVERVIEW", "sharpsignalDocId": 1261}, {"page": 5, "quote": null, "headingPath": "Encounter Step · Encounter Step continued", "sharpsignalDocId": 1261}, {"page": 6, "quote": null, "headingPath": "Encounter Step continued · SOLUTION PHASE · Question and Answer Step · Record-Keeping", "sharpsignalDocId": 1261}, {"page": 6, "quote": null, "headingPath": "Scoring Step", "sharpsignalDocId": 1261}, {"page": 7, "quote": null, "headingPath": "Scoring Step", "sharpsignalDocId": 1261}]
boost provenance — errata + base rulebook (E2/E3)
no registered errata card matched this query; base rulebook doc 1261 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 1261 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.92894 of 1914 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row recorded
Sep 5, 2026 15:38 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 rankdocumentheadingpage fused RRF scoresnippet chars
#1 RULEBOOK Mythos Tales — Rulebook (corpus doc 1261) SETUP · GAMEPLAY · Investigation Phase · 1. Travel Step 2. Encounter Step p.4 0.047643 (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 Mythos Tales — Rulebook (corpus doc 1261) Encounter Step · Encounter Step continued p.5 0.046432 (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 Mythos Tales — Rulebook (corpus doc 1261) Travel Step p.4 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)) 215
#4 RULEBOOK Mythos Tales — Rulebook (corpus doc 1261) Scoring Step p.6 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
#5 RULEBOOK Mythos Tales — Rulebook (corpus doc 1261) Travel Step p.5 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
#6 RULEBOOK Mythos Tales — Rulebook (corpus doc 1261) OVERVIEW 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
#7 RULEBOOK Mythos Tales — Rulebook (corpus doc 1261) Scoring Step p.7 0.030366 (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 Mythos Tales — Rulebook (corpus doc 1261) Encounter Step continued · SOLUTION PHASE · Question and Answer Step · Record-Keeping p.6 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

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 14 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 atdocumentheadingpage fused rankfused RRF scorecarried byhow it got its slot
#1 RULEBOOK Mythos Tales — Rulebook (corpus doc 1261) SETUP · GAMEPLAY · Investigation Phase · 1. Travel Step 2. Encounter Step p.4 #1 0.047643 (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
#2 RULEBOOK Mythos Tales — Rulebook (corpus doc 1261) Travel Step p.5 #5 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
#3 RULEBOOK Mythos Tales — Rulebook (corpus doc 1261) OVERVIEW p.2 #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
#4 RULEBOOK Mythos Tales — Rulebook (corpus doc 1261) Scoring Step p.6 #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)) vector + the doc-priority boost arm the re-ranker chose it
#5 RULEBOOK Mythos Tales — Rulebook (corpus doc 1261) Encounter Step continued · SOLUTION PHASE · Question and Answer Step · Record-Keeping p.6 #8 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
#6 RULEBOOK Mythos Tales — Rulebook (corpus doc 1261) Scoring Step p.7 #7 0.030366 (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 re-ranker chose it
#7 RULEBOOK Mythos Tales — Rulebook (corpus doc 1261) Travel Step p.4 #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)) vector + the doc-priority boost arm the re-ranker chose it
#8 RULEBOOK Mythos Tales — Rulebook (corpus doc 1261) Encounter Step · Encounter Step continued p.5 #2 0.046432 (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

chosen chunks — what the answer actually cited

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 Mythos Tales — Rulebook (corpus doc 1261) SETUP · GAMEPLAY · Investigation Phase · 1. Travel Step 2. Encounter Step p.4 no quote on the wire
[2] RULEBOOK Mythos Tales — Rulebook (corpus doc 1261) Travel Step p.4 no quote on the wire
[3] RULEBOOK Mythos Tales — Rulebook (corpus doc 1261) Travel Step p.5 no quote on the wire
[4] RULEBOOK Mythos Tales — Rulebook (corpus doc 1261) OVERVIEW p.2 no quote on the wire
[5] RULEBOOK Mythos Tales — Rulebook (corpus doc 1261) Encounter Step · Encounter Step continued p.5 no quote on the wire
[6] RULEBOOK Mythos Tales — Rulebook (corpus doc 1261) Encounter Step continued · SOLUTION PHASE · Question and Answer Step · Record-Keeping p.6 no quote on the wire
[7] RULEBOOK Mythos Tales — Rulebook (corpus doc 1261) Scoring Step p.6 no quote on the wire
[8] RULEBOOK Mythos Tales — Rulebook (corpus doc 1261) Scoring Step p.7 no quote on the wire

generation — timing and the path taken

timing split
retrieval 107 ms · first delta 1514 ms · total 3998 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 107 ms · ask 3889 ms · gateway work 3998 ms · total 3998 ms
tokens in (the prompt the answerer read)
3829
tokens out (what the answerer generated)
478
tok/sec
200.3 tok/sec — 478 output tokens in 2.386 s of generation
live seat (read from the running child)
answering — gemma4:26b think:false · num_ctx 32768 (live-verified 15s ago)
answerer host (measured by rulesage)
reachable (for 22h, 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 1191), 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.