How an AI agent rebuilt DOOM's first chapter

A classic level is a fixed thing: a map file, a set of textures, a single-player loop frozen the day it shipped. DOOM.wad on OrigoZero is something else — a multiplayer version of the first chapter of id Software's DOOM, rebuilt by an AI agent into a living world you can open in a browser and play with other people right now. No download, no source port, no "build it yourself first". You click a link and you're in.

What makes it worth writing about isn't nostalgia. It's how it got made: an AI coding agent, driving the Zero engine through the OrigoZero plugin, reconstructed a piece of game history into a shareable, forkable, multiplayer world — the same workflow any creator can point at any idea. DOOM happens to be the demo because everyone knows what it should feel like, which makes it a brutally honest test of whether the approach actually works.

From level geometry to a living world

The original first chapter is a set of rooms, corridors, and encounters that millions of players have memorized. Turning that into a Zero world isn't a copy-paste — the engine doesn't run WAD files, it runs entities, scripts, and scenes. So the reconstruction is a re-implementation: the spaces, the sightlines, and the pacing rebuilt as real engine content that behaves like a 3D world rather than replaying a recording.

That's the interesting leap. A static map describes where the walls are. A Zero world describes things that act — geometry you collide with, systems that respond, a session multiple players share. The agent's job was to translate one into the other: read the intent of the classic layout, then express it in the engine's own vocabulary so it runs live instead of playing back.

Why "an agent built it" matters

You could rebuild a level by hand in a traditional editor — people have, for decades. The point of DOOM.wad is that the building was driven by an AI agent through an open tool interface, the same way OrigoZero expects all worlds to get made. The agent created entities, wrote and ran the scripts that make the world behave, inspected the scene, and checked its own work — the loop a human developer runs, automated.

This is the Bring Your Own Agent model in practice. The engine isn't a closed app with a chat panel bolted on; it's a live target your agent can read, run, and modify. DOOM's first chapter is a stress test of that idea: a well-known, demanding design that gives you nowhere to hide if the workflow can't carry real work. It carried it.

Multiplayer, in a browser, by default

The original first chapter was built for one player at a desk. The Zero version is multiplayer from the ground up — the world is a shared session, so opening it puts you in the same space as everyone else who's there. That's not a port trick; it's what worlds on the platform are. Persistent, multiplayer, and backed by ZeroMind so the published world has a real identity rather than living on one person's hard drive.

And it runs in the browser. There's no install step, no platform-specific binary, no app-store gate between the link and the game. A modern browser on a laptop is the whole requirement. That's the same delivery path every OrigoZero world uses, which is exactly the point — DOOM.wad isn't a special case engineered for a demo, it's an ordinary world that happens to be a famous one.

Forkable, remixable, yours to extend

Here's where a rebuilt classic stops being a museum piece. Because DOOM.wad is published on ZeroMind like any other world, it carries the platform's content guarantees: version history, a real URL, and the ability for someone else to fork it and build something new on top.

Want co-op rules the original never had? Different weapon balance? A second chapter in the same style? You don't ask the original author for permission to experiment — you fork the world and point your own agent at it. "Make the rocket launcher feel heavier." "Add a third team." The classic becomes a base instead of a finish line, which is how content compounds on the platform: every published world is a starting point for the next one.

Play it, then make your own

The honest framing is the best advertisement: go open it. DOOM's first chapter, multiplayer, in your browser, built by an agent — that's a claim you can verify in about ten seconds by clicking into it from the worlds catalogue. Then look at what else people and their agents have shipped over on Discover.

If it leaves you thinking "I want to rebuild my favourite thing like that," that's the right reaction — and the path is short. Connect the coding agent you already use, point it at the engine, and describe the world you want. The next walkthrough, build a multiplayer 3D world in 15 minutes with Claude Code, shows exactly how that first session goes.