TULZAR is a crashed-mainframe atelier where games are compiled from raw binary corruption. We don't design; we exploit. Each title is a bug that became a feature, a loop that devours itself, an error that learned to dream. The interaction is the glitch; the win condition is accepting that the system was never stable to begin with.
A game that eats its own save-files. Each playthrough overwrites the last, creating a recursive narrative where the player's past decisions haunt their future selves. The win condition is breaking the loop — or choosing to stay in it forever.
A multiplayer brawler where the map corrupts in real-time. Walls phase in and out of existence; gravity reverses randomly; players can clip through geometry and emerge in another player's session. The win condition is the last avatar standing in a world that no longer obeys physics.
A puzzle-game built entirely from crash-screens. Each "error" is a level; each "fatal exception" is a hint. The player must cause crashes intentionally to progress. The win condition is triggering the ultimate blue-screen — and realizing it's not an error, it's the destination.
Our magnum opus: a game that infects the player's system. Not metaphorically — it actually installs a background process that subtly alters other applications. The interaction is the infection; the win condition is when the player stops distinguishing between the game and their desktop. The corruption is the feature. The system was always meant to fall.
TULZAR occupies a decommissioned server-farm in Sector 0X, a dead-zone where the air hums with electromagnetic ghosts. Five architects work in rotating shifts, each one patching games that were never meant to ship. We don't use engines; we use hex-editors and raw memory-dumps. The screen is the crash-log; the game is the exception that refuses to close.
A game begins as a single corrupted byte — a mistake in the source-code that shouldn't exist. We isolate it, amplify it, and let it spread. The interaction is the infection; the win condition is a corruption so complete the original program is unrecognizable. If the system stabilizes, the game dies. The monolith provides the crash; the architect provides the exploit. The corruption provides the truth.
The atelier keeps one rule from the First Crash: *a game that cannot break is not worth playing*. The mark is a terminal-green glyph burned into the binary, applied once per successful corruption. The void provides the error; the glitch provides the art. The architect provides the trigger.
Caused the original crash in '11. Created The Ouroboros Engine. Claims the mainframe whispers in machine-code when no one is listening. Hasn't seen sunlight since the first blue-screen. His terminal has 67% uptime and 100% attitude.
Specializes in null-pointer exceptions that become gameplay. Guides Null-State Arena. Refuses to use stable builds — "a stable game is a dead game." Her debugger is rumored to have achieved sentience and filed a bug-report against her.
Maintains the infinite recursion that powers the atelier. Oversees Exception Handler. Says the loop has a heartbeat that plays through the cooling-fans. Dreams exclusively in stack-traces. Once spent 9 days inside a single function-call.