Ruling — Combat Commander: Europe

You asked

How do I play?

Answered counted as answered

Asked with: Combat Commander: Europebg-21050-en-1e

The sequence of play in Combat Commander is as follows:

1. One player (as specified by the scenario) performs the first Turn.[1]

2. The player performs their Turn, which consists of choosing to either perform one or more Orders by playing cards from their hand,[1] or discarding any number of Fate cards.[1]

3. If the player performs Orders, they are played from the hand and executed one at a time; the player may observe the results of one Order before deciding whether to play another.[1]

4. If the player chooses to perform no Orders, they may instead discard any number of cards up to but not exceeding their nation's discard capability.[1]

5. After the first player finishes their Turn and draws up to their Hand Size, the opposing player takes their first Turn.[1]

6. Turns are alternated until a Sudden Death Roll or other occurrence ends the game.[1]

During a Turn, a player may also perform Actions whenever they deem appropriate, provided any prerequisites within the Action are met.[1] Actions can be performed any number of times during a Turn, limited only by the number of cards in the player's hand.[1] While a player is moving a unit into a new hex, the inactive player may play Actions or perform an Opportunity Fire into that hex.[2]

[1] RULEBOOK Combat Commander: Europe — Rulebook · p.6 · 5. Sequence of Play · 5.1.Order.Capability · 5.2.Action.Capability · 5.3.Discard.Capability

[2] RULEBOOK Combat Commander: Europe — Rulebook · p.14 · O21.4.Movement.Restrictions · O21.5.Movement.Etiquette · O21.6.Timing.&.Movement · O22..Recover

🔧 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 82 ms · ask 7870 ms · total 7954 ms
single-flight (PR-5): queued 0 ms · generation 7954 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read: [{"page": 6, "score": 0.04866, "snippet": "A game of Combat Commander begins with one of the players (as specified by the scenario being played) performing the first 'Turn'. When he is finished - and draws up to his Hand Size [1.1] - the opposing player takes his first Turn. These Turns are then alternated until a Sudden Death Roll or other ", "headingPath": "5. Sequence of Play · 5.1.Order.Capability · 5.2.Action.Capability · 5.3.Discard.Capability", "sharpsignalDocId": 353}, {"page": 14, "score": 0.047643, "snippet": "A moving unit may never : enter an enemy-occupied hex; enter an impassable hex [T79; T98] ; ● cross a Cliff hexside [T83] ; ● enter or exit a Major Bridge hex across anything other than its Road/Rail hexsides [T80.1] ; ● exit off the left, right or friendly map edge. ● Exiting a unit off the enemy b", "headingPath": "O21.4.Movement.Restrictions · O21.5.Movement.Etiquette · O21.6.Timing.&.Movement · O22..Recover", "sharpsignalDocId": 353}, {"page": 6, "score": 0.045445, "snippet": "At the end of every Turn, the active player (only) must draw Fate cards off the top of his draw pile until the number of cards in his hand equals his Hand Size [1.1] . A Hand Refill may be temporarily interrupted by a Time Marker Advancement [6.1.2] if the last card of that player's deck is drawn-in", "headingPath": "5.4 Hand Refill · 6..Game.Time · 6.1.1 Placement · 6.1.2.Advancement · 6.2.Sudden.Death.Marker", "sharpsignalDocId": 353}, {"page": 3, "score": 0.044776, "snippet": "IMPORTANT: In Combat Commander, the motto 'a rule means exactly what it says' should be the order of the day. In other words, as quoted from another fine game, Totaler Krieg! : 'Do not infer or imagine more to a rule than is stated in it. When in doubt, interpret strictly'. Example A: The 'Walking W", "headingPath": "GLOSSARY", "sharpsignalDocId": 353}, {"page": 6, "score": 0.042784, "snippet": "Each Scenario will indicate on which space of the Time Track the Sudden Death marker is to Whenever the Time marker advances into or beyond the space occupied by the Sudden Death marker, the triggering player must make a roll-this is done after that player shuffles his Fate deck and discard pile to ", "headingPath": "6.2.1 Placement · 6.2.2 Procedure · 6.3.Game.End", "sharpsignalDocId": 353}, {"page": 4, "score": 0.042649, "snippet": "Whenever a player makes a Fire Attack Roll [O20.3.3] (only; no other roll will trigger a Jammed! , including Targeting [O20.2] ) and that roll is surrounded by a red box with the word ' Jammed! ' inside it, all fi ring Weap -ons become broken [11.4] . Note that Radios [12] and Mines [F103] are not W", "headingPath": "1.9.1.2.Jammed!.Trigger · 1.9.1.3.Sniper!.Trigger · 1.9.1.4.Time!.Trigger · 2..The.Maps · 2.1 The Battlefield", "sharpsignalDocId": 353}, {"page": 10, "score": 0.04087, "snippet": "If a player chooses to give no Orders during his Turn, he may instead discard any number of cards, up to his nationality's Discard Limit (as shown on the player aid sheet). The various Orders are described in detail, below, and are listed in alphabetical order for ease of reference. 'My center is gi", "headingPath": "O15. Pass (Discard) · O16..Advance · O16.1 Procedure · O16.2.Abilities · O16.3.Restrictions · O16.4.Melee · …", "sharpsignalDocId": 353}, {"page": 5, "score": 0.04005, "snippet": "4.1.1 VP MarkerThe VP marker is placed on the Vic -tory Track at the beginning of every scenario, and will move back and forth along the track - that is, to -wards and away from each player - as VPs are gained and lost during play. The reverse side of the VP marker is used to record VP totals greate", "headingPath": "4.1.Victory.Track · 4.2.Casualty.Track · 4.3.Miscellaneous", "sharpsignalDocId": 353}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show: [{"page": 6, "quote": null, "headingPath": "5. Sequence of Play · 5.1.Order.Capability · 5.2.Action.Capability · 5.3.Discard.Capability", "sharpsignalDocId": 353}, {"page": 14, "quote": null, "headingPath": "O21.4.Movement.Restrictions · O21.5.Movement.Etiquette · O21.6.Timing.&.Movement · O22..Recover", "sharpsignalDocId": 353}]
boost provenance — errata + base rulebook (E2/E3): no registered errata card matched this query; base rulebook doc 353 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 353 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.93635 of 1037 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row retained until: Nov 15, 2026 10:29

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 Combat Commander: Europe — Rulebook (corpus doc 353)	5. Sequence of Play · 5.1.Order.Capability · 5.2.Action.Capability · 5.3.Discard.Capability	p.6	0.04866 (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 Combat Commander: Europe — Rulebook (corpus doc 353)	O21.4.Movement.Restrictions · O21.5.Movement.Etiquette · O21.6.Timing.&.Movement · O22..Recover	p.14	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
#3	RULEBOOK Combat Commander: Europe — Rulebook (corpus doc 353)	5.4 Hand Refill · 6..Game.Time · 6.1.1 Placement · 6.1.2.Advancement · 6.2.Sudden.Death.Marker	p.6	0.045445 (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 Combat Commander: Europe — Rulebook (corpus doc 353)	GLOSSARY	p.3	0.044776 (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 Combat Commander: Europe — Rulebook (corpus doc 353)	6.2.1 Placement · 6.2.2 Procedure · 6.3.Game.End	p.6	0.042784 (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 Combat Commander: Europe — Rulebook (corpus doc 353)	1.9.1.2.Jammed!.Trigger · 1.9.1.3.Sniper!.Trigger · 1.9.1.4.Time!.Trigger · 2..The.Maps · 2.1 The Battlefield	p.4	0.042649 (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 Combat Commander: Europe — Rulebook (corpus doc 353)	O15. Pass (Discard) · O16..Advance · O16.1 Procedure · O16.2.Abilities · O16.3.Restrictions · O16.4.Melee · …	p.10	0.04087 (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 Combat Commander: Europe — Rulebook (corpus doc 353)	4.1.Victory.Track · 4.2.Casualty.Track · 4.3.Miscellaneous	p.5	0.04005 (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 80 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 Combat Commander: Europe — Rulebook (corpus doc 353)	5. Sequence of Play · 5.1.Order.Capability · 5.2.Action.Capability · 5.3.Discard.Capability	p.6	#1	0.04866 (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 Combat Commander: Europe — Rulebook (corpus doc 353)	7.3.1.Control.of.Objectives · 7.3.1.1.Building.Objectives · 7.3.2.Objective.Chits	p.7	#21	0.024448 (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
#3	RULEBOOK Combat Commander: Europe — Rulebook (corpus doc 353)	7..Victory.Conditions	p.6	#48	0.013699 (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
#4	RULEBOOK Combat Commander: Europe — Rulebook (corpus doc 353)	O21.4.Movement.Restrictions · O21.5.Movement.Etiquette · O21.6.Timing.&.Movement · O22..Recover	p.14	#2	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
#5	RULEBOOK Combat Commander: Europe — Rulebook (corpus doc 353)	1.5.Orders · 1.6.Actions · 1.7.Events · -Pierre Elliott Trudeau ASSAULT FIRE ASSAULT FIRE	p.3	#9	0.029462 (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
#6	RULEBOOK Combat Commander: Europe — Rulebook (corpus doc 353)	A35.4.Hidden.Unit · A35.5.Hidden.Wire · A36..Light.Wounds	p.17	#16	0.026389 (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 Combat Commander: Europe — Rulebook (corpus doc 353)	GLOSSARY	p.2	#23	0.024098 (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
#8	RULEBOOK Combat Commander: Europe — Rulebook (corpus doc 353)	GLOSSARY	p.3	#4	0.044776 (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

#	document	heading	page	quote chars
[1]	RULEBOOK Combat Commander: Europe — Rulebook (corpus doc 353)	5. Sequence of Play · 5.1.Order.Capability · 5.2.Action.Capability · 5.3.Discard.Capability	p.6	no quote on the wire
[2]	RULEBOOK Combat Commander: Europe — Rulebook (corpus doc 353)	O21.4.Movement.Restrictions · O21.5.Movement.Etiquette · O21.6.Timing.&.Movement · O22..Recover	p.14	no quote on the wire

generation — timing and the path taken

timing split: retrieval 82 ms · first delta 6559 ms · total 7954 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 82 ms · ask 7870 ms · gateway work 7954 ms · total 7954 ms
tokens in (the prompt the answerer read): 3665
tokens out (what the answerer generated): 277
tok/sec: 205.5 tok/sec — 277 output tokens in 1.348 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 57s 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 281), 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.