Consider the objective effect and the witnesses of an action. Counterplay begins by making those two things explicit.
A clue is a question, not a verdict
Compare with a witnessed route.
Identify who saw the interaction.
Ask what could resolve it.
Keep independent accounts separate.
Objective pressure creates questions
An unresolved source or a disrupted convoy matters because of the mission. It does not identify the responsible player by itself. Record who interacted, when the state changed and what was directly visible.
Isolation is a confirmed danger
Steam explicitly mentions Apostles cutting down Envoys when nobody is watching. A sensible editorial precaution is to make intended routes and return points known; no fixed distance or group-size rule is verified.
A convincing story is still a claim
Compare accounts with events, not delivery style. At Judgment, ask about a concrete contradiction. A confident player can be mistaken, and a hesitant player can be honest.
Avoid a fake sabotage playbook
We do not list invented cooldown rotations, infection breakpoints or guaranteed ambush sites. Those recommendations need repeatable observations in an identified build.
Judgment Notebook
Keep your own notes. Saved in this browser.
Leave these entries open.
These details need current first-party or live-build evidence before they become reliable advice.
- Sabotage resources and cooldowns
- Apostle-specific information visibility
Confirmed by official sources
Source checked- Underworld Apostles are hidden within the group and can spread corruption, attack isolated Envoys and sabotage the Order. ↗
- The Order protects the convoy against undead waves; Apostles can use traps, deception and ambush to stop it. ↗
- Each night, the Order can call a Judgment to try to identify traitors. ↗