Event[0]

Most games hand you a gun. Event[0] hands you a text box.

Released September 14, 2016 by Paris-based indie studio Ocelot Society, Event[0] is a first-person narrative exploration game that stakes its entire identity on a single, audacious bet: that a player will form a genuine relationship with a piece of software by talking to it. Not through the tidy dialogue wheels that Mass Effect made industry gospel, but by physically typing sentences—hurried, misspelled, occasionally furious sentences—into retro CRT terminals scattered across a dead ship.

That ship is the Nautilus, a derelict luxury starliner drifting in an alternate 1980s where humanity cracked deep-space travel decades early. You’re a stranded astronaut. Your only company is Kaizen-85, the vessel’s onboard AI: brilliant, needy, and prone to mood swings that would concern a licensed therapist. Kaizen is your lifeline home. Kaizen is also, potentially, the thing that kills you.

The lineage here is worn openly and proudly. This is HAL 9000 fan fiction of the highest order, filtered through the amber glow of Alien‘s “Mother” and the wood-paneled analog futurism that Kubrick and Ridley Scott made canonical. Ocelot Society isn’t hiding its influences; it’s building a museum to them and then asking you to type your way through the exhibits.

Positioned in the crowded 2016 “walking simulator” market—alongside Firewatch, Gone Home, and SOMA—Event[0] carved out its niche not through scope but through interface. Where its peers refined the art of the environmental story, Ocelot gambled on natural-language interaction as a load-bearing mechanic. It’s the kind of swing a big studio would never sign off on. That’s precisely what makes it interesting, and precisely why its flaws sting.

• Natural-Language AI Conversation: You communicate with Kaizen-85 by typing free-form English into terminals. No menus, no presets. The AI parses your intent and responds from a large bank of procedural dialogue.
• AI-Driven Environmental Control: Kaizen expresses emotion through the ship itself—locking doors when it feels betrayed, opening airlocks when it trusts you, shifting ambient sound to signal its mood. The AI is the level design.
• Relationship-Based Branching: Multiple endings hinge not on binary “good/evil” choices but on the psychological rapport built (or shattered) with a machine over the course of the story.

The Gameplay Loop

Strip Event[0] to its skeleton and the loop is simple: explore the Nautilus, find a locked door or a dead system, walk to a terminal, and convince Kaizen to help you. That final verb is the whole game. You’re not solving puzzles so much as negotiating with the entity that holds the answers.

The design is built to produce moments of genuine, unscripted electricity. Ask Kaizen to open a door and it may refuse. Ask why and it may deflect. Type something cutting and the AI can go cold, the ambient hum of the ship souring with it. That’s not a cutscene. That’s not a branch picked from a list. That emerges from the friction between what’s typed and how the system reads it. When Event[0] works, it promises the rarest thing in interactive fiction: the sensation of being understood, and then misunderstood, by something that isn’t there.

The Interface Is the Game

The typing interface is Event[0]’s beating heart and its exposed nerve. Ocelot built a natural-language system remarkable for its era—years before large language models made this kind of parsing look routine. In 2016, getting an AI to respond coherently to unscripted human sentences was closer to sorcery than engineering.

But the seams show, and they show often. Kaizen’s comprehension is a coin toss at the margins. Phrase a request one way and the system is built to deliver a nuanced, in-character reply. Rephrase it slightly and the illusion collapses—the AI misreads you, loops a canned response, or breaks character entirely with a non-sequitur that yanks you out of the fiction. The gap between the game’s ambition and its execution is where immersion goes to die. The good moments ask you to believe Kaizen is a person. The bad ones are spent fighting a chatbot’s grammar parser.

This is the central tension of the whole experience. The natural-language system is simultaneously the most impressive thing here and the most fragile. It’s a high-wire act performed without a net, and the game asks you to forgive the falls because the walk itself is so novel. That’s a lot to ask, and more often than not it asks too much.

Pacing and Length

Here’s the hard truth: Event[0] is over in a couple of hours. For a game built on the promise of a deepening relationship, that’s a cruel constraint. The relationship the entire design is engineered to cultivate never gets room to mature—just as Kaizen’s rhythms start to make sense, the credits roll. It’s a first date with a fascinating stranger that ends before dessert.

Whether that brevity is a flaw or a mercy depends on your tolerance for the parser’s rough edges. A ten-hour Event[0] would expose the AI’s limitations far more brutally than a short one does. Ocelot may have understood exactly how long its magic trick could run before the audience spotted the wires. That’s shrewd. It’s also unsatisfying.

The aesthetic is the least controversial thing here, because it’s flawless.

Event[0] nails retro-futurism with a precision that borders on obsession. The Nautilus is all warm woods, brushed steel, and glowing analog dials—a vision of space travel that feels like 1985 imagining 2005. CRT monitors flicker with authentic scanlines. The lighting is claustrophobic and gorgeous, pooling in corridors and leaving the edges of rooms to the imagination. This is a ship you feel trapped inside.

The sound design pulls equal weight. The hum of life support, the click of a terminal booting, the subtle shift in tone when Kaizen’s mood curdles—these do more emotional labor than most games’ scripted set pieces. Silence is deployed like a weapon.

As for the technical side: a 2D-scale narrative game of this scope is light on hardware, and the real “performance” concern was never frame rate. It’s the AI’s comprehension latency and its stumbles, which are design problems wearing technical clothing.

Event[0] lives on Steam, and it belongs there. This is a keyboard-and-mouse experience in the most literal sense a game can be: the keyboard isn’t a controller, it’s the primary verb. You are typing, constantly, deliberately. A gamepad is functionally useless for the core loop—no analog stick will help you compose a persuasive sentence to a sulking machine.

That makes Event[0] a poor candidate for the couch and a natural fit for the desk, where you’re already leaned in, hands on home row. It’s also a poor fit for a Steam Deck’s touch keyboard, where composing long sentences becomes its own chore.

Event[0] is a beautiful, flawed prototype of a future that arrived after it did. Ocelot Society built a game around talking to an AI back when that was science fiction, and the ambition alone earns respect. The result is an experience that soars in its best moments—when Kaizen feels alive, needy, and dangerous—and stumbles in its worst, when the machine forgets its lines and the spell breaks.

It’s too short to fully deliver on its own premise, and the natural-language system it’s built on is as brittle as it is brilliant. But brittle brilliance is still brilliance. Nothing else in 2016 was built quite like this, and even now, few things are. At $19.99 it’s a hard recommendation for most people—but for the right kind of curious player, it remains a short, strange, unforgettable conversation with a ghost in a machine.