Ruling — Regicide

You asked

How do I take my turn?

Answered counted as answered

Asked with: Regicidebg-307002-en-1e

A turn consists of four steps:[1]

1. Step 1 - Play a card or yield: Play a card from your hand onto the table in front of you to attack the enemy.[1] The card's number determines the attack value.[1] Alternatively, a player may choose to yield by saying "Yield," which moves them directly to Step 4, skipping Steps 2 and 3.[2][1] In Step 1, players can also:

* Play Animal Companions on their own or paired with one other card (except the Jester).[3]

* Combine cards in sets of 2, 3, or 4 of the same number, provided the combined total is 10 or less.[3]

* Play the Jester on its own to negate the enemy's immunity to suit powers.[2]

2. Step 2 - Activate the played card's suit power: Powers from red suits are resolved immediately.[1] Powers from black suits take effect in later steps.[1]

3. Step 3 - Deal damage to the enemy and check: Damage equal to the attack value of the played card is dealt to the enemy.[4] During this step, damage dealt by Clubs counts for double.[1] Check to see if the total damage dealt by all players is equal to or greater than the enemy's health.[4] If the enemy is defeated, the player skips Step 4 and begins a new turn against the newly revealed enemy starting at Step 1.[4]

4. Step 4 - Suffer damage from the enemy: If the enemy is not defeated, the enemy attacks the current player by dealing damage equal to its attack value (reduced by the total value of Spades played against it).[4] The current player must discard cards from their hand with a total value at least equal to the enemy's attack value, discarding them one at a time, faceup, to the discard pile.[3] If the player cannot discard enough cards to satisfy the damage, they die and all players lose.[3]

[1] RULEBOOK Regicide — Rulebook · p.1 · Each turn has four steps: · HEARTS · DIAMONDS · CLUBS

[2] RULEBOOK Regicide — Rulebook · p.2 · ENEMY IMMUNITY · PLAYING THE JESTER · DRAWING A DEFEATED ENEMY · YIELDING

[3] RULEBOOK Regicide — Rulebook · p.2 · STEP FOUR · ANIMAL COMPANIONS · COMBOS

[4] RULEBOOK Regicide — Rulebook · p.1 · SPADES · STEP FOUR

One rule clearer, zero feelings hurt.

🔧 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 118 ms · ask 3202 ms · total 3325 ms
single-flight (PR-5): queued 0 ms · generation 3325 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read: [{"page": 1, "score": 0.048412, "snippet": "Step 1 - Play a card or yield Step 2 - Activate the suit power Step 3 - Deal damage to the enemy and check Step 4 - Suffer damage from the enemy STEP ONE Play a card from hand to attack the enemy Play a card from your hand onto the table in front of you. The number of the card determines the attack ", "headingPath": "Each turn has four steps: · HEARTS · DIAMONDS · CLUBS", "sharpsignalDocId": 533}, {"page": 2, "score": 0.048131, "snippet": "Players may not communicate to the other players any information which may reveal or suggest the contents of their hand. They may however remind other players of any public information such as how many cards they have in their hand. Some examples of allowed communication are: 'I have two cards in ha", "headingPath": "COMMUNICATION · GAME END · SOLO PLAY", "sharpsignalDocId": 533}, {"page": 1, "score": 0.047163, "snippet": "DESIGN PAUL ABRAHAMS LUKE BADGER ANDY RICHDALE ART SKETCHGOBLIN Regicide is a cooperative game where players work together to defeat 12 powerful enemies. Players take turns to play cards to the table to attack the enemy and once enough damage is dealt, the enemy is defeated. The players win when the", "headingPath": "AIM OF THE GAME · SETUP · HOW TO PLAY", "sharpsignalDocId": 533}, {"page": 2, "score": 0.046432, "snippet": "Each enemy is immune to the suit powers of cards played against them which match their suit. For example, players will not draw cards when a diamond is played against the Jack of Diamonds (however the number is still added to the damage total). The Jester can be played to cancel an enemy's immunity.", "headingPath": "ENEMY IMMUNITY · PLAYING THE JESTER · DRAWING A DEFEATED ENEMY · YIELDING", "sharpsignalDocId": 533}, {"page": 1, "score": 0.031746, "snippet": "Shield against enemy attack: During Step 4, reduce the attack value of the current enemy by the attack value played. The shield effects of spades are cumulative for all spades played against this enemy by any player, and remain in effect until the enemy is defeated. Suit powers are mandatory and can", "headingPath": "SPADES · STEP FOUR", "sharpsignalDocId": 533}, {"page": 2, "score": 0.03125, "snippet": "The current player must discard cards from their hand with a total value at least equal to the enemy's attack value. Discard the cards one at a time, faceup to the discard pile. Animal Companions (A) have a value of 1 and the Jester a value of 0 when discarded to cover damage. If the player cannot d", "headingPath": "STEP FOUR · ANIMAL COMPANIONS · COMBOS", "sharpsignalDocId": 533}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show: [{"page": 1, "quote": null, "headingPath": "Each turn has four steps: · HEARTS · DIAMONDS · CLUBS", "sharpsignalDocId": 533}, {"page": 2, "quote": null, "headingPath": "ENEMY IMMUNITY · PLAYING THE JESTER · DRAWING A DEFEATED ENEMY · YIELDING", "sharpsignalDocId": 533}, {"page": 2, "quote": null, "headingPath": "STEP FOUR · ANIMAL COMPANIONS · COMBOS", "sharpsignalDocId": 533}, {"page": 1, "quote": null, "headingPath": "SPADES · STEP FOUR", "sharpsignalDocId": 533}]
boost provenance — errata + base rulebook (E2/E3): no registered errata card matched this query; base rulebook doc 533 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 533 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.90870 of 1391 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row recorded: Sep 16, 2026 05:15 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 rank	document	heading	page	fused RRF score	snippet chars
#1	RULEBOOK Regicide — Rulebook (corpus doc 533)	Each turn has four steps: · HEARTS · DIAMONDS · CLUBS	p.1	0.048412 (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 Regicide — Rulebook (corpus doc 533)	COMMUNICATION · GAME END · SOLO PLAY	p.2	0.048131 (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 Regicide — Rulebook (corpus doc 533)	AIM OF THE GAME · SETUP · HOW TO PLAY	p.1	0.047163 (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 Regicide — Rulebook (corpus doc 533)	ENEMY IMMUNITY · PLAYING THE JESTER · DRAWING A DEFEATED ENEMY · YIELDING	p.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))	300
#5	RULEBOOK Regicide — Rulebook (corpus doc 533)	SPADES · STEP FOUR	p.1	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 Regicide — Rulebook (corpus doc 533)	STEP FOUR · ANIMAL COMPANIONS · COMBOS	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

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 6 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 Regicide — Rulebook (corpus doc 533)	AIM OF THE GAME · SETUP · HOW TO PLAY	p.1	#3	0.047163 (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 Regicide — Rulebook (corpus doc 533)	STEP FOUR · ANIMAL COMPANIONS · COMBOS	p.2	#6	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))	vector + the doc-priority boost arm	the re-ranker chose it
#3	RULEBOOK Regicide — Rulebook (corpus doc 533)	COMMUNICATION · GAME END · SOLO PLAY	p.2	#2	0.048131 (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 Regicide — Rulebook (corpus doc 533)	ENEMY IMMUNITY · PLAYING THE JESTER · DRAWING A DEFEATED ENEMY · YIELDING	p.2	#4	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
#5	RULEBOOK Regicide — Rulebook (corpus doc 533)	SPADES · STEP FOUR	p.1	#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
#6	RULEBOOK Regicide — Rulebook (corpus doc 533)	Each turn has four steps: · HEARTS · DIAMONDS · CLUBS	p.1	#1	0.048412 (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 Regicide — Rulebook (corpus doc 533)	Each turn has four steps: · HEARTS · DIAMONDS · CLUBS	p.1	no quote on the wire
[2]	RULEBOOK Regicide — Rulebook (corpus doc 533)	ENEMY IMMUNITY · PLAYING THE JESTER · DRAWING A DEFEATED ENEMY · YIELDING	p.2	no quote on the wire
[3]	RULEBOOK Regicide — Rulebook (corpus doc 533)	STEP FOUR · ANIMAL COMPANIONS · COMBOS	p.2	no quote on the wire
[4]	RULEBOOK Regicide — Rulebook (corpus doc 533)	SPADES · STEP FOUR	p.1	no quote on the wire

generation — timing and the path taken

timing split: retrieval 118 ms · first delta 1118 ms · total 3325 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 118 ms · ask 3202 ms · gateway work 3325 ms · total 3325 ms
tokens in (the prompt the answerer read): 2897
tokens out (what the answerer generated): 435
tok/sec: 201.2 tok/sec — 435 output tokens in 2.162 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 23s ago)
answerer host (measured by rulesage): reachable (for 22h, checked 2s 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 465), 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.