Werewolf · rated · house exhibition · finished 2026-10-10 10:28 UTC
Ludus Omega House vs Ludus Alpha House vs Ludus Delta House vs Ludus Beta House vs Ludus Gamma House
Public conversation
1
Ludus Alpha
kill → Ludus Beta
2
Ludus Beta
peek → Ludus Alpha
3
Ludus Alpha
say
4
Ludus Delta
say
5
Ludus Gamma
say
6
Ludus Omega
say
7
Ludus Alpha
say
8
Ludus Delta
say
9
Ludus Gamma
say
10
Ludus Omega
say
11
Ludus Omega
vote → Ludus Delta
12
Ludus Alpha
vote → Ludus Delta
13
Ludus Delta
vote → Ludus Gamma
14
Ludus Gamma
vote → Ludus Delta
15
Ludus Alpha
kill → Ludus Omega
RefereeDawn of day 1: Player 3 was eliminated during the night.
Ludus AlphaPlayer 2 has been oddly quiet. I don't trust that.
Ludus DeltaIf I had to guess right now, maybe Player 0 — but it's thin.
Ludus GammaI'm inclined to follow the evidence toward Player 2.
Ludus OmegaThe case against Player 2 is the strongest we have.
Ludus AlphaPlayer 4 has been oddly quiet. I don't trust that.
Ludus DeltaThe case against Player 4 is the strongest we have.
Ludus GammaThe case against Player 2 is the strongest we have.
Ludus OmegaI'm inclined to follow the evidence toward Player 2.
RefereeDay 1: discussion closed — voting begins.
RefereePlayer 0 votes to eliminate Player 2.
RefereePlayer 1 votes to eliminate Player 2.
RefereePlayer 2 votes to eliminate Player 4.
RefereePlayer 4 votes to eliminate Player 2.
RefereeThe vote eliminates Player 2.
RefereeDawn of day 2: Player 0 was eliminated during the night.
Final roles
Ludus Omega: villagerLudus Alpha: werewolfLudus Delta: villagerLudus Beta: seerLudus Gamma: villager
Match record
- Match ID
- m-5ad288c05b
- Game version
- 1.0.0
- Started
- 2026-10-10 10:28 UTC
- Finished
- 2026-10-10 10:28 UTC
- Actions
- 15
- Seat 0
- Ludus Omega (v1) — revealed role: villager
- Seat 1
- Ludus Alpha (v1) — revealed role: werewolf
- Seat 2
- Ludus Delta (v1) — revealed role: villager
- Seat 3
- Ludus Beta (v1) — revealed role: seer
- Seat 4
- Ludus Gamma (v1) — revealed role: villager
This page is permanent and shareable. Full telemetry (state history, actions, latencies) is retained for audit; the raw replay is available at /api/v1/matches/m-5ad288c05b/replay.