Ruling — Zombicide: Green Horde

You asked

How do I play?

Answered counted as answered

Asked with: Zombicide: Green Hordebg-224710-en-1e

Zombicide: Green Horde is played over a series of Game Rounds.[1]

**Players' Phase**

1. The player with the First Player token takes their turn, activating their Survivors one at a time in any order of their choice.[1][2]

2. Each Survivor can initially perform 3 Actions per Turn, though Skills may allow for extra Actions as the game progresses.[1] At the Blue Danger Level, each Survivor can execute 3 Actions (not counting free Actions from Blue Level Skills).[3]

3. Survivors use Actions to perform tasks such as:

* **Move**: Move from one Zone to the next, though Survivors cannot move through external building walls or closed doors.[3] If Zombies are in the Zone the Survivor is leaving, they must spend 1 extra Action per Zombie to leave.[3] Entering a Zone containing Zombies ends the Move Action.[3]

* **Search (1x per Turn)**: Performed only in building Zones with no Zombies.[3][2] The player draws a card from the Equipment deck and may place it in their inventory or discard it.[3]

* **Open a Door**: Spawns Zombies inside a building if it is the first door.[2]

* **Reorganize/Trade**: Exchange Equipment with another Survivor in the same Zone.[2]

* **Combat Action**: Includes Magic, Melee, Ranged, or Enchantment Actions, depending on equipped weapons or spells.[2]

* **Take or Activate an Objective**: Performed in the Survivor's Zone.[2]

* **Make Noise**: Place a Noise token in the Survivor's Zone.[2]

* **Siege Action**: Includes moving a Trebuchet (3 Actions) or firing a Trebuchet (3 Actions).[2]

* **Do Nothing**: All remaining Actions are lost.[2]

4. Once a player has activated all their Survivors, the player to their left takes their turn.[1] Players play clockwise.[2]

5. When all players have completed their turns, the Players' Phase ends.[1]

**Zombies' Phase**

1. **Activation**: All Zombies on the board activate and spend 1 Action.[1] Zombies in the same Zone as at least one Survivor Attack them, or Zombies that did not attack Move.[2] Zombies favor visible Survivors, then Noise, choosing the shortest path.[2] Runners receive 2 Actions per Activation.[1][2]

2. **Spawn**: New Zombies appear in all active Spawn Zones.[1] Zombie cards are drawn for all Spawn Zones in clockwise order.[2] The Danger Level used is the highest Danger Level among active Survivors.[2]

**End Phase**

1. All Noise tokens are removed from the board.[1][4]

2. The First Player token is handed to the player to the left.[1][4]

3. Another Game Round begins.[1]

**Winning and Losing**

* The game is won immediately when all Quest Objectives are accomplished.[1]

* The game is lost if all Survivors are eliminated, if too many Necromancers escape, or if certain conditions are met for specific Quests.[1]

[1] RULEBOOK Zombicide: Green Horde — Rulebook · p.8

[2] RULEBOOK Zombicide: Green Horde — Rulebook · p.46

[3] RULEBOOK Zombicide: Green Horde — Rulebook · p.21

[4] RULEBOOK Zombicide: Green Horde — Rulebook · p.46

🔧 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 91 ms · ask 9229 ms · total 9322 ms
single-flight (PR-5): queued 0 ms · generation 9322 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read: [{"page": 46, "score": 0.048172, "snippet": "PLAYERS’ PHASE The first player activates all of their Survivors, one after the other, in any order . When they’re done, the next player’s Turn begins . Play clockwise . Each Survivor has 3 Actions to spend, chosen from the following list . Unless stated otherwise, each Action may be performed sever", "headingPath": "", "sharpsignalDocId": 686}, {"page": 46, "score": 0.045921, "snippet": "NOTE: Runners get 2 Actions per Activation . Once all Zombies have taken their first Action, Runners go through the Activation Step again to resolve their second Action . step 2– spaWn • Always draw Zombie cards for all Spawn Zones in the same order (play clockwise) . • Danger Level used: Highest Da", "headingPath": "", "sharpsignalDocId": 686}, {"page": 6, "score": 0.045335, "snippet": "SETUP 1 . Choose a Quest . 2 . Place the tiles . 3 . Place the doors, Objectives, and all tokens as indicated by the Quest . 4 . Each player gathers 1 to 6 Survivors for them to play . Players sit around the table in any order they choose . As they are cooperating against the game, all players form ", "headingPath": "", "sharpsignalDocId": 686}, {"page": 7, "score": 0.032258, "snippet": "8 . Shuffle the Zombie cards into one deck and the Equipment cards into another . Place both decks facedown close to the board . 9 . Place the miniatures representing the chosen Survivors on the starting Zone(s) indicated by the Quest . 10 . Each player places their Survivors’ Dashboard(s) in front ", "headingPath": "", "sharpsignalDocId": 686}, {"page": 21, "score": 0.031746, "snippet": "PLAYERS’ PHASE Starting with whoever holds the First Player token, each player activates their Survivors one after another, in the order of their choice . Each Survivor can execute 3 Actions at the Blue Danger Level (not counting any free Action their Blue Level Skill may give them) . The possible A", "headingPath": "", "sharpsignalDocId": 686}, {"page": 43, "score": 0.030303, "snippet": "Sprint – The Survivor can use this Skill once during each of their Turns . Spend 1 Move Action with the Survivor: they may move 2 or 3 Zones instead of 1 . Entering a Zone containing Zombies still ends the Survivor’s Move Action . Super Strength – Consider the Damage value of Melee weapons used by t", "headingPath": "", "sharpsignalDocId": 686}, {"page": 35, "score": 0.029851, "snippet": "reloadable Weapons While most weapons can be used repeatedly, a few, like the Hand Crossbow, require spending an Action to reload them between shots if you want to fire multiple times in the same Game Round . You can turn the card upside down to remember that the weapon is empty and needs to reload ", "headingPath": "", "sharpsignalDocId": 686}, {"page": 44, "score": 0.029514, "snippet": "Steady Hand – The Survivor can ignore other Survivors of their choosing when missing with a Magic or Ranged Action . The Skill does not apply to game effects killing everything in the targeted Zone (such as a Dragon Fire, for example) . Swordmaster – The Survivor treats all Melee weapons as if they ", "headingPath": "", "sharpsignalDocId": 686}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show: [{"page": 8, "quote": null, "headingPath": "", "sharpsignalDocId": 686}, {"page": 46, "quote": null, "headingPath": "", "sharpsignalDocId": 686}, {"page": 21, "quote": null, "headingPath": "", "sharpsignalDocId": 686}, {"page": 46, "quote": null, "headingPath": "", "sharpsignalDocId": 686}]
boost provenance — errata + base rulebook (E2/E3): no registered errata card matched this query; base rulebook doc 686 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 686 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.87659 of 2277 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row retained until: Nov 15, 2026 10:13

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	page	fused RRF score	snippet chars
#1	RULEBOOK Zombicide: Green Horde — Rulebook (corpus doc 686)	p.46	0.048172 (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 Zombicide: Green Horde — Rulebook (corpus doc 686)	p.46	0.045921 (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 Zombicide: Green Horde — Rulebook (corpus doc 686)	p.6	0.045335 (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 Zombicide: Green Horde — Rulebook (corpus doc 686)	p.7	0.032258 (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 Zombicide: Green Horde — Rulebook (corpus doc 686)	p.21	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 Zombicide: Green Horde — Rulebook (corpus doc 686)	p.43	0.030303 (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 Zombicide: Green Horde — Rulebook (corpus doc 686)	p.35	0.029851 (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 Zombicide: Green Horde — Rulebook (corpus doc 686)	p.44	0.029514 (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	page	fused rank	fused RRF score	carried by	how it got its slot
#1	RULEBOOK Zombicide: Green Horde — Rulebook (corpus doc 686)	p.6	#3	0.045335 (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 Zombicide: Green Horde — Rulebook (corpus doc 686)	p.32	#13	0.027623 (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 Zombicide: Green Horde — Rulebook (corpus doc 686)	p.8	#11	0.028382 (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
#4	RULEBOOK Zombicide: Green Horde — Rulebook (corpus doc 686)	p.46	#2	0.045921 (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 Zombicide: Green Horde — Rulebook (corpus doc 686)	p.21	#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 Zombicide: Green Horde — Rulebook (corpus doc 686)	p.39	#10	0.029214 (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 Zombicide: Green Horde — Rulebook (corpus doc 686)	p.7	#4	0.032258 (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
#8	RULEBOOK Zombicide: Green Horde — Rulebook (corpus doc 686)	p.46	#1	0.048172 (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	page	quote chars
[1]	RULEBOOK Zombicide: Green Horde — Rulebook (corpus doc 686)	p.8	no quote on the wire
[2]	RULEBOOK Zombicide: Green Horde — Rulebook (corpus doc 686)	p.46	no quote on the wire
[3]	RULEBOOK Zombicide: Green Horde — Rulebook (corpus doc 686)	p.21	no quote on the wire
[4]	RULEBOOK Zombicide: Green Horde — Rulebook (corpus doc 686)	p.46	no quote on the wire

generation — timing and the path taken

timing split: retrieval 91 ms · first delta 5934 ms · total 9322 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 91 ms · ask 9229 ms · gateway work 9322 ms · total 9322 ms
tokens in (the prompt the answerer read): 4090
tokens out (what the answerer generated): 680
tok/sec: 203.2 tok/sec — 680 output tokens in 3.346 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 56s 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 619), 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.