RuleSage cited table rulings
← BattleLore

You asked

How do I play?

Answered counted as answered

Asked with: BattleLorebg-25417-en-1e

To play, follow this sequence on your turn:
1. COMMAND phase: Play a Command card.[1] At the start of your turn, play a Command card from your hand, place it face up in front of you, and read it aloud.[2] The card dictates in which section(s) of the battlefield you may issue orders and how many units you may order.[2] If no unit Command cards back Section cards, Tactic cards can be ordered by the Command card just played; in this case, disregard steps 2 through 4 of the Game turn, draw a new Command card, and end your turn.[2]
2. ORDER phase: Announce all units you intend to order, within the limits of the Section or Tactic Command card just played.[1]
3. MOVEMENT phase: Move all ordered units you wish, one at a time.[1] You must respect unit and terrain movement limitations, as per the Terrain Summary cards.[1]
4. COMBAT phase: Battle one ordered unit at a time.[1] Select an enemy unit and:
* Verify that your target is within range and line of sight.[1]
* Announce the number of battle dice you are entitled to roll, per your unit's troop type and weapon type.[1]
* Adjust your number of battle dice, based on any terrain effects.[1]
* Roll the resulting number of battle dice, and apply their effect, per the attacking unit's weapon card, scoring hits first, then retreats.[1]
* If appropriate, conduct follow-on actions (gaining ground, pursuit action, Bonus Melee attack and/or enemy battle back).[1]
5. DRAW phase: Draw a new Command card.[1] In Lore Adventures, also draw new Lore cards and/or tokens.[1]
General Rules:
* Turn Order: The player listed in the adventure's battle notes starts first, and players then alternate turns.[1]
* Winning: The game continues until one player reaches the number of Victory Banners indicated by the adventure's victory conditions.[1]
* Lore Cards: To play a Lore card, place it in front of you during the appropriate phase of play (possibly in reaction to an opponent's action) and read it aloud.[3] You must spend the required number of Lore tokens from your goblet's reserve.[3] At the end of the game turn, tokens are dropped into the common Lore pool and the card is discarded.[3] You may play a maximum of one Lore card during your turn and a maximum of one during your opponent's turn.[3]
[1] RULEBOOK BattleLore — Rulebook · p.10 · There are no supplemental Terrain pieces in Agincourt. · ON YOUR TURN, follow the sequence below
[2] RULEBOOK BattleLore — Rulebook · p.11 · PHASE 1. PLAY A COMMAND CARD · There are two types of Command cards: · Conflicting Rules & Rules priorities and precedence:
[3] RULEBOOK BattleLore — Rulebook · p.51 · PLAYING A LORE CARD

The book has spoken.

🔧 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 189 ms · ask 6298 ms · total 6490 ms
single-flight (PR-5)
queued 0 ms · generation 6490 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read
[{"page": 51, "score": 0.048652, "snippet": "To play a Lore card, place it in front of you during the appropriate phase of play (possibly in reaction to one of your opponent's actions), and read it aloud. Spend the required number of Lore tokens out of your goblet's reserve, temporarily placing those tokens on the Lore card; at the end of the ", "headingPath": "PLAYING A LORE CARD", "sharpsignalDocId": 645}, {"page": 11, "score": 0.047938, "snippet": "At the start of your turn, play a Command card from your hand. Place it face up in front of you, and read it aloud. Command cards are normally used to order units to move and/or battle. The card you play dictates in which section(s) of the battlefield you may issue orders, and how many units you may", "headingPath": "PHASE 1. PLAY A COMMAND CARD · There are two types of Command cards: · Conflicting Rules & Rules priorities and precedence:", "sharpsignalDocId": 645}, {"page": 50, "score": 0.04598, "snippet": "This phase of play is not used in the base deck, but included for future use. Play during Orders: Play this Lore card at the start of your Orders phase, during your turn as the active player. These Lore cards usually order additional units, above and beyond those ordered by the Command card just pla", "headingPath": "Play alongside your Command card: · MOVEMENT PHASE", "sharpsignalDocId": 645}, {"page": 4, "score": 0.045956, "snippet": "T his Player's Guide introduces you to the BattleLore game system. It not only includes the rules you will need to play the game, but also lays the foundation for many forthcoming expansions. While the size of the book may seem daunting at first, learning the basics of the game is a straightforward,", "headingPath": "TABLEOF CONTENTS", "sharpsignalDocId": 645}, {"page": 50, "score": 0.045037, "snippet": "Play during battle: Play this Lore card during one of your unit's Battle phase. The battle can be a Melee attack on an adjacent enemy unit, or a Ranged attack against a more distant enemy. The effect of the Lore card applies for the unit's entire Battle, including any follow-on actions (gaining grou", "headingPath": "COMBAT PHASE · Play before your opponent's dice roll:", "sharpsignalDocId": 645}, {"page": 4, "score": 0.044192, "snippet": "Finally, you will be ready to form your own War Council and lead the charge, as explained in Chapter 9 - The War Council. If you are already familiar with the game's concepts, having played Memoir '44 or similar card-driven miniature game systems before, we invite you to jump right in. Set up the ga", "headingPath": "TABLEOF CONTENTS", "sharpsignalDocId": 645}, {"page": 7, "score": 0.042857, "snippet": "Part 1 of this book covers the game ' s basics. How to set up an adventure, how to play a Medieval Adventure if you ' ve never played one before, and the key Medieval tactical aspects of the game. 7 7", "headingPath": "OBJECT OF THE GAME", "sharpsignalDocId": 645}, {"page": 8, "score": 0.040385, "snippet": "For your first game, we recommend that you set up and play Agincourt - 1415, an adventure expressly designed to introduce you to the basics of Medieval warfare. Focused solely on the historical confrontation between the English and the French, two human Armies, it will give you and your opponent a c", "headingPath": "OBJECT OF THE GAME · Lay the 13 Wood hexes bordering Agincourt's battlefield. · There are no supplemental Terrain pieces in Agincourt.", "sharpsignalDocId": 645}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show
[{"page": 10, "quote": null, "headingPath": "There are no supplemental Terrain pieces in Agincourt. · ON YOUR TURN, follow the sequence below", "sharpsignalDocId": 645}, {"page": 11, "quote": null, "headingPath": "PHASE 1. PLAY A COMMAND CARD · There are two types of Command cards: · Conflicting Rules & Rules priorities and precedence:", "sharpsignalDocId": 645}, {"page": 51, "quote": null, "headingPath": "PLAYING A LORE CARD", "sharpsignalDocId": 645}]
boost provenance — errata + base rulebook (E2/E3)
no registered errata card matched this query; base rulebook doc 645 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 645 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.89884 of 1898 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row recorded
Aug 27, 2026 07:17 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 BattleLore — Rulebook (corpus doc 645) PLAYING A LORE CARD p.51 0.048652 (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 BattleLore — Rulebook (corpus doc 645) PHASE 1. PLAY A COMMAND CARD · There are two types of Command cards: · Conflicting Rules & Rules priorities and precedence: p.11 0.047938 (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 BattleLore — Rulebook (corpus doc 645) Play alongside your Command card: · MOVEMENT PHASE p.50 0.04598 (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 BattleLore — Rulebook (corpus doc 645) TABLEOF CONTENTS p.4 0.045956 (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 BattleLore — Rulebook (corpus doc 645) COMBAT PHASE · Play before your opponent's dice roll: p.50 0.045037 (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 BattleLore — Rulebook (corpus doc 645) TABLEOF CONTENTS p.4 0.044192 (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 BattleLore — Rulebook (corpus doc 645) OBJECT OF THE GAME p.7 0.042857 (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)) 200
#8 RULEBOOK BattleLore — Rulebook (corpus doc 645) OBJECT OF THE GAME · Lay the 13 Wood hexes bordering Agincourt's battlefield. · There are no supplemental Terrain pieces in Agincourt. p.8 0.040385 (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 atdocumentheadingpage fused rankfused RRF scorecarried byhow it got its slot
#1 RULEBOOK BattleLore — Rulebook (corpus doc 645) PHASE 1. PLAY A COMMAND CARD · There are two types of Command cards: · Conflicting Rules & Rules priorities and precedence: p.11 #2 0.047938 (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 BattleLore — Rulebook (corpus doc 645) Play alongside your Command card: · MOVEMENT PHASE p.50 #3 0.04598 (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
#3 RULEBOOK BattleLore — Rulebook (corpus doc 645) OBJECT OF THE GAME · Lay the 13 Wood hexes bordering Agincourt's battlefield. · There are no supplemental Terrain pieces in Agincourt. p.8 #8 0.040385 (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
#4 RULEBOOK BattleLore — Rulebook (corpus doc 645) PLAYING A LORE CARD OUT-OF-CHARACTER p.57 #10 0.028898 (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
#5 RULEBOOK BattleLore — Rulebook (corpus doc 645) There are no supplemental Terrain pieces in Agincourt. · ON YOUR TURN, follow the sequence below p.10 #17 0.024961 (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 BattleLore — Rulebook (corpus doc 645) Play after your opponent's dice roll: Play · IDENTIFYING THE TARGET p.51 #12 0.027598 (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 BattleLore — Rulebook (corpus doc 645) COMBAT PHASE · Play before your opponent's dice roll: p.50 #5 0.045037 (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
#8 RULEBOOK BattleLore — Rulebook (corpus doc 645) PLAYING A LORE CARD p.51 #1 0.048652 (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 BattleLore — Rulebook (corpus doc 645) There are no supplemental Terrain pieces in Agincourt. · ON YOUR TURN, follow the sequence below p.10 no quote on the wire
[2] RULEBOOK BattleLore — Rulebook (corpus doc 645) PHASE 1. PLAY A COMMAND CARD · There are two types of Command cards: · Conflicting Rules & Rules priorities and precedence: p.11 no quote on the wire
[3] RULEBOOK BattleLore — Rulebook (corpus doc 645) PLAYING A LORE CARD p.51 no quote on the wire

generation — timing and the path taken

timing split
retrieval 189 ms · first delta 3655 ms · total 6490 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 189 ms · ask 6298 ms · gateway work 6490 ms · total 6490 ms
tokens in (the prompt the answerer read)
3064
tokens out (what the answerer generated)
561
tok/sec
201.4 tok/sec — 561 output tokens in 2.785 s of generation
live seat (read from the running child)
answering — gemma4:26b think:false · num_ctx 32768 (live-verified 13s ago)
answerer host (measured by rulesage)
reachable (for 22h, checked 3s 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 578), 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.