The Resistance: Avalon Strategy – Voting, Merlin & Evil Cover
Editorial analysis: Avalon is a game of information patterns, not certainty. A single vote or mission result rarely proves alignment because Good can make bad reads and Evil can intentionally support success.
Track proposal and vote history together
A player who repeatedly proposes the same suspicious teammate provides stronger evidence than one isolated approval vote. Look for patterns across several rounds.
Good should not equate success with innocence
An Evil player can submit Success to gain trust, especially on early missions. Treat a successful team as useful evidence, not a solved alignment list.
Merlin must guide without becoming obvious
Merlin’s perfect-looking reads become evidence for the Assassin. Mix accurate guidance with plausible uncertainty and let other Good players sometimes lead the argument.
Evil should avoid redundant sabotage
When two Evil players are on the same mission, two Fail cards can reveal more than one was necessary to produce the result. Coordinate through table inference, not explicit communication, and consider when a Success preserves cover.
Use the rejection track as pressure
Late in a sequence of rejected teams, Good may be forced to approve an imperfect proposal to avoid the automatic Evil victory. Evil can exploit this by creating disagreement before the fifth proposal.
Assassin reads post-mission behavior too
After Good reaches three successes, review who consistently redirected teams away from Evil players with unusual accuracy. Merlin may reveal themselves more through team-building influence than direct accusations.