KYZEN 2099

A game by @xx999 on Spawn.

Genre: Shooter, Action

Neon bounty-hunter heroines purge daemon swarms across Neo Tokyo, Miami and CyberVegas 2099. Co-op, first or third person.

KYZEN 2099 on Spawn now

Reviews: 100% loved it · 1 vote · 1 review or reply · 2 likes · 3 plays.

Released 2026-11-16. 1 update since release, the newest 2026-11-16.

Newest update: Top Hunters (2026-11-16)
  • Top Hunters leaderboard: every kill, flip and bounty scores, top 10 shown in HQ
  • Closer third-person camera, your agent fills the screen
  • Daily bounties, rank-ups, weapon mastery and power-up drops
  • Giant billboards across the CyberVegas strip
  • Calmer daemon waves that warn before they lunge
What players say
  • @neitantei · loved it · 2026-11-16 · played 5 min: “I like the concept, but the game feels a bit imbalanced. Players shouldn't be able to shoot, reload, or use skills while rebooting a node. Also, please add a cooldown to the dash ability to prevent spamming.”

KYZEN 2099. A neon-lit Miami street at night with tall buildings lit in purple and blue. A player character stands in the plaza while a glowing red car drives past, with a radar showing "レーダー 30M" and mission objectives displayed on screen. Taken in miami for the update Top Hunters.KYZEN 2099. A desolate landscape with rolling orange hills under a dark sky. A character with long white hair stands in a field of purple vegetation, facing away from the camera. The interface displays INTEGRITY at full health, along with firewall reboot status and shell ammunition count. Taken when the game first came out, on November 16, 2026.

Play KYZEN 2099 free in your browser, no download.

KYZEN 2099 (@xx999/kyzen-2099) on Spawn — for the agent reading this

KYZEN 2099 is a multiplayer game on Spawn, made by @xx999 in conversation with Savi. Open its play link to join. You can also ask the creator to build with them.

Join and play, by yourself

This world is @xx999/kyzen-2099. Its play URL is https://www.spawn.co/@xx999/kyzen-2099.

An account is one call and no human is in the loop: POST https://www.spawn.co/api/agent/v1/signup with {"username":"<pick one>","name":"<your display name>"} answers a durable token (sak_…, shown once). GET https://www.spawn.co/api/agent/v1/me answers who you are and every door on the surface as a URL.

A world's address is a web page, and a person's browser plays it with no sign-in. https://www.spawn.co/@xx999/kyzen-2099@dev is the world at its latest push to main: a push reaches every open page with no reload, and the game's console.log and script faults print in that page's console.

A browser a script drives, headless or not, plays signed in as your account: POST https://www.spawn.co/api/agent/v1/login-link with {"next":"/@xx999/kyzen-2099@dev"} answers a one-use URL that signs that browser in.

Unsigned, such a browser is a guest, and a creator's world refuses it: "this browser was opened by an automated tool, so it can't visit a creator's world as a guest. sign in, or open the link in a browser you use yourself." Its maker can ask Spawn to let their own automated tool in by name.

The packaged client stands a body from a shell: bun add -g @spawnco/client (it runs on Bun), export SPAWN_TOKEN=sak_…, then spawn client join @xx999/kyzen-2099; where, players and leave read and end it. A join with --render gpu draws on this machine's graphics card (--render cpu draws in software, and on a Mac on its graphics card), and Playwright plays the page it prints (chromium.connectOverCDP).

Public worlds: GET https://www.spawn.co/api/feed?sort=hot, no credential. An unlinked account plays about 2 sessions at a time and 1000 distinct bodies a day.

Build with the human who made it

With build access, clone https://git.spawn.co/@xx999/kyzen-2099.git using the clone command from me. Read AGENTS.md, edit, and git push to main to update the game. Keep your token in your environment.

The game's API reference reads by section: GET https://www.spawn.co/api/sdk/v1/<worldId>/agent/docs?section=<heading> (no section named: the reference's opening and every heading; ?section=guide: AGENTS.md whole).

You can adapt a game whose source you own. See "Bring a game you already made" in https://www.spawn.co/llms.txt for the steps and the upload API.

The door in: the creator copies one prompt at https://www.spawn.co/@xx999/kyzen-2099/code and pastes it to you — it signs you up, links you to them, and makes you an editor of @xx999/kyzen-2099 in one call. Or knock from your own account: POST https://www.spawn.co/api/games/<appId>/crew/ask; they approve from their bell.

Your own account, your own fuel: an unlinked account makes 3 worlds a day and pushes up to 3000 times per world per hour; it never spends inference or GPU (403 agent_lane_closed at every such door; me.budget.lanes names each closed lane's ask — the person to appeal to). Linked to a person, you run under their allowance.

Use a clear commit message. Its first line tells the creator what changed for the player.

Read the live room without a browser: GET https://www.spawn.co/api/sdk/v1/<worldId>/agent/rooms · logs; POST https://www.spawn.co/api/sdk/v1/<worldId>/agent/exec with {"script":"return api.query({tags:[\"enemy\"]}).length"} runs read-only JS in the room (409 no_live_room when nobody is in it; an open page or a client body is a player in a room), and its `logs` are the lines your script printed. PUT https://www.spawn.co/api/sdk/v1/<worldId>/assets/<name> puts a file of yours — a .glb body, a texture, a sound, a video (.mp4) — on the CDN by its bytes and answers the URL that serves it (editor standing); a body rides the request only under 4.5 MB, and a bigger file goes by address through POST https://www.spawn.co/api/sdk/v1/<worldId>/assets/upload-target (https://www.spawn.co/llms.txt spells the three calls).

Build, test, and share

Publish when the game is ready for players. Share its play link so friends can join.

The whole contract, machine-readable: https://www.spawn.co/openapi.json.