LOGFIRE: Signal Hunt
Production is burning. The logs are your only signal.
A terminal arcade game about being on call. Logs stream past faster than you can read them, most of it harmless noise, and the one line that matters is already three screens up.
Play
Play LOGFIRE: Signal Hunt
Keyboard captured — the game has focus
The embed didn't load — it may be blocked by your browser or an extension. You can still play it on Lexaloffle ↗.
Controls
- ↑↓
- Move through the log feed
- Z
- Respond to the selected log
You are the on-call engineer. A production system is streaming its logs at you and something in there is actually wrong.
Most of what scrolls past is noise — heartbeats, cache hits, a worker recycling on schedule. Buried in it are the lines that matter: a payment gateway timing out, replication falling behind, three warnings climbing in a row that add up to something none of them mean alone.
Miss enough of them and instability climbs to 100%, the system crashes, and the run is over. Runs last three to six minutes, and the log stream gets faster the longer you survive.
Signal versus noise
The whole game is one decision made repeatedly under worsening conditions: is this line worth acting on?
Acting on everything fails, because responding costs you time you don’t have as the feed accelerates. Acting on nothing fails faster. What the game is actually training is the thing that makes a good on-call engineer — recognising the shape of a real incident early, from partial information, while the information keeps arriving.
The dangerous patterns are deliberately not single lines:
- warnings that escalate rather than repeat
- errors that cluster around one service
- a CRIT that arrives quietly, between two INFO lines
Built small on purpose
There are no sprites and no scrolling backgrounds. Everything is text on black, in PICO-8’s palette, because the game is about reading under pressure and anything decorative competes with the thing you’re supposed to be reading.
That constraint set the whole design: if the only tool is a log line, then difficulty has to come from volume, speed, and how well the real signals hide in the fake ones.
Screenshots
Screenshots
Every run starts the same way.
Green is noise. Yellow might be. Red already cost you.
The escalating pattern is the tell. Three warnings climbing is an incident; one is a Tuesday.
100% instability ends the run.
Devlog
Writing about LOGFIRE: Signal Hunt
Building LOGFIRE in PICO-8
Why a game about reading production logs has no sprites, no scrolling background, and nothing on screen that isn't text you're supposed to read.