The camera has an opinion

When you are not touching the camera, it cuts to the loudest thing in the valley: a fire, a drowning, a wedding on the move, a fight, a child at the pole. The first drag hands it back, and twelve seconds of stillness gives it to the camera again.

First cut
5 seconds
Hands back after
12 seconds
Alarms shown
4

The valley is seven hundred units across. A fire, a funeral, a child in the river, a mill jammed, a house going up: all of those already happen, and they used to land in a ticker you had to be reading. The director points the camera.

A shot is a state, not a line of text

The list is read off the frame the scene is already drawing. A roof alight, a procession walking, a party in the water, people fighting, a child on the way to the pole. A drowning that has just happened stays as long as it is still in the event window. Ranked, worst first, so the four buttons on the left and the idle cut are the same list.

Yield on the first drag

A camera that keeps taking the shot back is the most irritating thing a live simulation can do. Touch the canvas, the wheel, WASD, an alarm, or follow somebody, and it stops. After twelve seconds of stillness it takes the current top shot again. A fire beats a wedding the moment the roof catches; a walking procession keeps the camera because the shot is the row from this frame, not the one from when it started.

The buttons are still there

Pressing an alarm is the same circle the director would have done, except you chose it. WarAlert is the other half and deliberately different: a declaration is a moment and goes away, a fire is a state and stands while the roof is alight.

Read next

More on the village