You asked
how do i win?
Answered counted as answeredThe winner of a combat is determined by the total power revealed on their Power Dial plus any power from combat cards used [1][2]. If there is a tie in total power, the attacking player wins [3][2]. The winner of the combat gains control of the territory and all resource tokens on it [1]. Additionally, the winner may place one star token on the Triumph Track (unless they have already placed two) [1]. If the winner was the attacker, they lose 1 popularity for each worker forced to retreat [1][2]. If a mech transporting workers is attacked on a lake and the attacker wins, the attacking player loses 1 popularity for each of those workers [1][2]. The loser of a combat must retreat all units (mechs, characters, and workers) to their home base; any resources these units were carrying remain on the territory under the winner's control [1]. If the loser revealed at least one power through their dial or cards, they draw one combat card as they retreat [1][2].
🔧 debug — where this ruling came from
- outcome
- ANSWERED — Answered
- corpus profile
- live
- answerer pin (deploy-frozen, attribution only)
- gemma4:12b think:false 4eb23ef187e2
- timings
- search 89 ms · ask 5229 ms · total 5328 ms
- single-flight (PR-5)
- queued 0 ms · generation 5328 ms
- retrieval refs (raw)
- [{"page": 23, "score": 0.032266, "snippet": "Both players reveal their Power Dials and selected combat cards simultaneously. The value provided by any combat cards provides an additional bonus to the power you spend from the Power Track as indicated on your Power Dial. The player with the highest total power wins the combat (ties go to the att", "headingPath": "REVEAL", "sharpsignalDocId": 44}, {"page": 29, "score": 0.032018, "snippet": "Announce your coin total, and the player with the most coins wins! If multiple players have the same total, use the following as tiebreakers (in order): Number of workers, mechs, and structures Power Popularity Number of resource tokens controlled Number of territories controlled Number of star toke", "headingPath": "DECLARING THE WINNER", "sharpsignalDocId": 44}, {"page": 23, "score": 0.031054, "snippet": "If a mech transporting workers is attacked while on a lake and the attacker wins combat, the attacking player loses 1 popularity for each of those workers (they are forced to retreat with the mech to their home base). EXAMPLE: John takes a Move action, first moving his character onto an unoccupied f", "headingPath": "REVEAL", "sharpsignalDocId": 44}, {"page": 27, "score": 0.029644, "snippet": "When you reach a pinnacle of empire building, your faction rewards you with a star. Stars are worth coins at the end of the game. Here are the ways to place stars, as shown on the Triumph Track: Complete all 6 upgrades Deploy all 4 mechs Build all 4 structures Enlist all 4 recruits When you achieve ", "headingPath": "PLACING STARS", "sharpsignalDocId": 44}, {"page": 1, "score": 0.029274, "snippet": "The goal is to have the greatest fortune at the end of the game; a typical winning fortune is around $75. You can accumulate coins during the game, but you will earn most of them during end-game scoring in the following three categories: Every star token placed Every territory controlled Every 2 res", "headingPath": "GOAL", "sharpsignalDocId": 44}, {"page": 22, "score": 0.029083, "snippet": "Combat may happen at the end of a player's Move action (after all units have moved but before the player takes a bottom-row action). If that player's character and/or mechs share a territory with an opponent's character and/or mechs, combat occurs. It's possible for this to happen on multiple territ", "headingPath": "COMBAT", "sharpsignalDocId": 44}, {"page": 24, "score": 0.026779, "snippet": "As your character treks across Eastern Europa, they will encounter a number of local people and situations. Each encounter will present you with three options to determine how you want to interact with the people. The choice you make will often impact the peoples' view of you, represented in the gam", "headingPath": "ENCOUNTERS", "sharpsignalDocId": 44}, {"page": 1, "score": 0.02619, "snippet": "In Scythe, each player represents a character attempting to make their faction the richest and most powerful in Eastern Europa. Players explore and conquer territory, enlist new recruits, produce resources and workers, build structures, and deploy monstrous mechs. A game of Scythe typically begins w", "headingPath": "OBJECT OF THE GAME", "sharpsignalDocId": 44}]
- citations (raw)
- [{"page": 23, "quote": null, "headingPath": "REVEAL", "sharpsignalDocId": 44}, {"page": 23, "quote": null, "headingPath": "REVEAL", "sharpsignalDocId": 44}, {"page": 22, "quote": null, "headingPath": "COMBAT", "sharpsignalDocId": 44}]
- boost provenance — errata + base rulebook (E2/E3)
-
no registered errata card matched this query; base-rulebook boost: not recorded (this ruling predates it); rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base-rulebook boost: not recorded (this ruling predates it)
- 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
- Oct 14, 2026 11:49
retrieval — what the search arm returned
score = the fused retrieval score (reciprocal-rank fusion over the search arms) — NOT a cosine similarity. How many arms fused this ruling was NOT RECORDED (it predates the boost trail, ran on the path that stored none, or stored one that could not be read), and the ceiling depends on that count (ceiling = arms/(k+1) at k=60): 2 arms top out at 0.03279; 3 arms top out at 0.04918. So a score above 0.03279 here is not an anomaly: it is arithmetic proof a boost arm voted, and the measured band 0.016–0.033 (taken on two-arm asks) is what does not apply. 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 Scythe — Rulebook (corpus doc 44) | REVEAL | p.23 | 0.032266 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded)) | 300 |
| #2 | RULEBOOK Scythe — Rulebook (corpus doc 44) | DECLARING THE WINNER | p.29 | 0.032018 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded)) | 300 |
| #3 | RULEBOOK Scythe — Rulebook (corpus doc 44) | REVEAL | p.23 | 0.031054 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded)) | 300 |
| #4 | RULEBOOK Scythe — Rulebook (corpus doc 44) | PLACING STARS | p.27 | 0.029644 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded)) | 300 |
| #5 | RULEBOOK Scythe — Rulebook (corpus doc 44) | GOAL | p.1 | 0.029274 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded)) | 300 |
| #6 | RULEBOOK Scythe — Rulebook (corpus doc 44) | COMBAT | p.22 | 0.029083 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded)) | 300 |
| #7 | RULEBOOK Scythe — Rulebook (corpus doc 44) | ENCOUNTERS | p.24 | 0.026779 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded)) | 300 |
| #8 | RULEBOOK Scythe — Rulebook (corpus doc 44) | OBJECT OF THE GAME | p.1 | 0.02619 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded)) | 300 |
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.
| # | document | heading | page | quote chars |
|---|---|---|---|---|
| [1] | RULEBOOK Scythe — Rulebook (corpus doc 44) | REVEAL | p.23 | no quote on the wire |
| [2] | RULEBOOK Scythe — Rulebook (corpus doc 44) | REVEAL | p.23 | no quote on the wire |
| [3] | RULEBOOK Scythe — Rulebook (corpus doc 44) | COMBAT | p.22 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 89 ms · first delta n/a · total 5328 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 5229 ms · gateway work 5328 ms · total 5328 ms
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 35s ago)
- stream path
- not recorded — this ruling predates the stream-path column (V41)
- 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 2), 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.