Session logs Built across the whole file Updated when a measurement moves
Co-Op Dispatch emblem Co-Op Dispatch
Logs

Patterns that only become visible after nineteen games

A single review can tell you whether a game is good. It cannot tell you that eleven of the nineteen games in this file blame the wrong player for friendly fire, or that most co-op designs quietly assume nobody will ever miss a week. These logs exist for the findings that need the whole file.

2open logs 19games drawn on No fixed schedule Every figure re-checkable

What is in the logs and what is not

Both logs are drawn from sessions that were played for the reviews rather than staged separately. Nothing here was set up to prove a point, which is why the samples are uneven — eleven games have friendly fire and nine were suitable for the absence test, and neither number was chosen.

Figures in the logs are re-checkable. Where a claim rests on a specific session it says so, and where it rests on an impression it is described as an impression rather than dressed up as a count.

Two logs closed as unusable

An attempt to measure voice-channel load — how much of a session is spent talking — was abandoned after four games. Transcribing our own conversations turned out to change how we spoke to each other, and the numbers described the experiment rather than the games.

A second attempt to grade matchmaking quality was closed before it opened. Every game in this file was played with someone we already know, which means we have nothing honest to say about playing with strangers, and a log built on four hours of curiosity would have been worse than no log at all.

LogGamesStatusWhy
L1 — Friendly fire and blame11OpenFinding held across every game with the mechanic
L2 — Drop-in and absence9OpenClear separation between three design approaches
L3 — Voice channel load4ClosedMeasurement changed the behaviour being measured
L4 — Matchmaking quality0Not openedNo honest sample; we always play with people we know

The finding we most expect to reverse

The friendly-fire log currently claims that blame allocation is a structural property of the system rather than of the players. That is drawn from eleven games and two people, and two people is a very small number of personalities to generalise from.

If it reverses, it will be because a third player joins the file for long enough to show that we were describing our own dynamic. That is noted at the top of the log itself rather than buried here.