RuleSage cited table rulings
← Riftforce

You asked

How do I play?

Answered counted as answered

Asked with: Riftforcebg-291859-en-1e

1. The player with the start marker begins the game.[1]
2. Perform 1 action alternately.[1]
3. There are 3 different actions:
* Play: Play up to 3 elementals from your hand to locations on your side of the Rift.[1] These elementals must either all show the same symbol or all show the same number.[1][2] You can play these elementals either individually to adjacent locations or together in an order of your choice all to the same location.[1] If playing to adjacent locations, you can only play 1 elemental per location.[1] If playing to a location with previously played elementals, place the new elementals on top, ensuring the numbers and symbols are clearly visible.[1]
* Activate: Discard 1 elemental from your hand face up onto your discard pile.[3][2] Activate up to 3 elementals that either all show the same number or all show the same symbol as the just discarded elemental.[3][2] The elementals you activate can be at any location and do not have to be adjacent to each other.[3] You must execute the ability of an activated elemental completely before you activate the next elemental.[2]
* Check & Draw: You can only choose this action if you have less than 7 elementals in your hand.[2][4] Check if you control any locations; you control a location if at least 1 of your elementals and no enemy is present there.[4] Gain 1 Riftforce for each controlled location and move your Riftforce marker forward on the score track accordingly.[4] If you choose this action only, you can gain Riftforce even if your opponent controls locations at that moment.[4] Then, draw elementals from your draw pile until you have 7 elementals in your hand.[2][4]
[1] RULEBOOK Riftforce — Rulebook · p.6 · GAMEPLAY · A) PLAY
[2] RULEBOOK Riftforce — Rulebook · p.2
[3] RULEBOOK Riftforce — Rulebook · p.7
[4] RULEBOOK Riftforce — Rulebook · p.10 · C) CHECK & DRAW

So says the rulebook. So plays the table.

🔧 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 2741 ms · total 2850 ms
single-flight (PR-5)
queued 0 ms · generation 2850 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read
[{"page": 6, "score": 0.04918, "snippet": "The player with the start marker begins the game. Perform 1 action alternately. There are 3 different actions: Play Activate Check & Draw Play up to 3 elementals from your hand to locations on your side of the Rift. They must either all show the same symbol or all show the same number. You can play ", "headingPath": "GAMEPLAY · A) PLAY", "sharpsignalDocId": 1205}, {"page": 4, "score": 0.04741, "snippet": "Place the 2 halves of the score track next to each other so the numbers are in ascending order. Choose which side of the cards you want to use depending on your table size. 1 Place your Riftforce markers next to the score track. 2 Place the 5 locations in a row between you and your opponent to creat", "headingPath": "SETUP GENERAL", "sharpsignalDocId": 1205}, {"page": 11, "score": 0.047379, "snippet": "As soon as you reach 12 Riftforce the game end is triggered. Finish your action completely. If you started the game your opponent still takes 1 action. If your opponent started, the game ends immediately. That way both of you get the same amount of actions. The player with the most Riftforce wins! I", "headingPath": "GAME END · FAQ GENERAL", "sharpsignalDocId": 1205}, {"page": 2, "score": 0.045928, "snippet": "action if you have less than 7 elementals in your hand. Gain 1 Riftforce for each location where at least one of your elementals and no enemy is present. Draw elementals from your draw pile until you have 7 elementals in your hand. ACTION B Activate Discard 1 elemental from your hand onto the discar", "headingPath": "", "sharpsignalDocId": 1205}, {"page": 1, "score": 0.044557, "snippet": "A card game for 2 players, ages 10 and up, which plays in approx. 30 min. The Rifts changed our world. Villages were torn apart, the Riftforce emerged and spread across the land. What once seemed lifeless began to rise and awake. Flames leapt from campfires and waves poured out of their riverbeds. E", "headingPath": "HOW IT BEGAN · Now it is your time! · CREDITS", "sharpsignalDocId": 1205}, {"page": 5, "score": 0.031746, "snippet": "Select your guilds as described in the Guild Selection (page 3). Display your 4 summoners next to the score track. Place the start marker next to it if you started in the Guild Selection. 6 Collect all 36 elementals of your 4 guilds. Shuffle them together thoroughly and then place them face down to ", "headingPath": "SETUP PERSONAL", "sharpsignalDocId": 1205}, {"page": 10, "score": 0.030769, "snippet": "You can only choose this action if you have less than 7 elementals in your hand. Check if you control any of the locations. You control a location if at least 1 of your elementals and no enemy is present there. You gain 1 Riftforce for each controlled location. Move your Riftforce marker forward on ", "headingPath": "C) CHECK & DRAW", "sharpsignalDocId": 1205}, {"page": 7, "score": 0.030159, "snippet": "B) ACTIVATE First discard 1 elemental from your hand face up onto your discard pile. Activate up to 3 elementals that either all show the same number or all show the same symbol as the just discarded elemental. The elementals you activate can be at any location and do not have to be adjacent to each", "headingPath": "", "sharpsignalDocId": 1205}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show
[{"page": 6, "quote": null, "headingPath": "GAMEPLAY · A) PLAY", "sharpsignalDocId": 1205}, {"page": 2, "quote": null, "headingPath": "", "sharpsignalDocId": 1205}, {"page": 7, "quote": null, "headingPath": "", "sharpsignalDocId": 1205}, {"page": 10, "quote": null, "headingPath": "C) CHECK & DRAW", "sharpsignalDocId": 1205}]
boost provenance — errata + base rulebook (E2/E3)
no registered errata card matched this query; base rulebook doc 1205 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 1205 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.92073 of 1375 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row recorded
Sep 6, 2026 12:24 UTC

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 Riftforce — Rulebook (corpus doc 1205) GAMEPLAY · A) PLAY p.6 0.04918 (at the 3-arm ceiling (0.04918) — every arm ranked it #1) 300
#2 RULEBOOK Riftforce — Rulebook (corpus doc 1205) SETUP GENERAL p.4 0.04741 (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 Riftforce — Rulebook (corpus doc 1205) GAME END · FAQ GENERAL p.11 0.047379 (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 Riftforce — Rulebook (corpus doc 1205) p.2 0.045928 (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 Riftforce — Rulebook (corpus doc 1205) HOW IT BEGAN · Now it is your time! · CREDITS p.1 0.044557 (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 Riftforce — Rulebook (corpus doc 1205) SETUP PERSONAL 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
#7 RULEBOOK Riftforce — Rulebook (corpus doc 1205) C) CHECK & DRAW p.10 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
#8 RULEBOOK Riftforce — Rulebook (corpus doc 1205) p.7 0.030159 (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 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 15 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 Riftforce — Rulebook (corpus doc 1205) GAMEPLAY · A) PLAY p.6 #1 0.04918 (at the 3-arm ceiling (0.04918) — every arm ranked it #1) vector + full-text + the doc-priority boost arm the re-ranker chose it
#2 RULEBOOK Riftforce — Rulebook (corpus doc 1205) p.7 #8 0.030159 (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 Riftforce — Rulebook (corpus doc 1205) p.2 #4 0.045928 (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 Riftforce — Rulebook (corpus doc 1205) C) CHECK & DRAW p.10 #7 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
#5 RULEBOOK Riftforce — Rulebook (corpus doc 1205) B) ACTIVATE p.9 #13 0.014085 (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
#6 RULEBOOK Riftforce — Rulebook (corpus doc 1205) SETUP PERSONAL p.5 #6 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
#7 RULEBOOK Riftforce — Rulebook (corpus doc 1205) GAME END · FAQ GENERAL p.11 #3 0.047379 (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 Riftforce — Rulebook (corpus doc 1205) SETUP GENERAL p.4 #2 0.04741 (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

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 Riftforce — Rulebook (corpus doc 1205) GAMEPLAY · A) PLAY p.6 no quote on the wire
[2] RULEBOOK Riftforce — Rulebook (corpus doc 1205) p.2 no quote on the wire
[3] RULEBOOK Riftforce — Rulebook (corpus doc 1205) p.7 no quote on the wire
[4] RULEBOOK Riftforce — Rulebook (corpus doc 1205) C) CHECK & DRAW p.10 no quote on the wire
timing split
retrieval 107 ms · first delta 873 ms · total 2850 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 2741 ms · gateway work 2850 ms · total 2850 ms
tokens in (the prompt the answerer read)
1719
tokens out (what the answerer generated)
390
tok/sec
202.5 tok/sec — 390 output tokens in 1.926 s of generation
live seat (read from the running child)
answering — gemma4:26b think:false · num_ctx 32768 (live-verified 41s ago)
answerer host (measured by rulesage)
reachable (for 24h, 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.
outcome
ANSWERED — Answered
abstain rationale (n/a — this ruling answered)
answered — no abstain rationale applies
decision
NOT_SETUP_SHAPED — no setup-shape pattern matched this question

this game registers NO errata cards (edition 1135), 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.