Zeta Base Defense

Newest update: Zeta Base Defense (2026-09-04)

• Updated to engine version 5.2.40

Earlier update: Zeta Base Defense (2026-08-28)

• Updated to engine version 5.2.34

Earlier update: Zeta Base Defense (2026-08-15)

• Updated to engine version 5.2.25

Earlier update: Zeta Base Defense (2026-08-02)

• Updated to engine version 5.2.13, adapted leaderboards to the new versions (Unfortunately this means the previous records got erased, apologies!

Earlier update: Zeta Base Defense (2026-07-30)

• Updated to engine version 5.2.10, potential fix for issue where a wall could spawn in the middle of a run if another player connected.

What players say

• @j · 2026-08-02 · played 12 min · 2 hearts: “very fun i died so horribly hahaha”

• @alongzera · 2026-09-08 · played 28 min · 1 heart: “Love the gameplay! did my best to try to finish all the waves. Would suggest to add somekind of dash feature to get the game more posibilites of making a play or dodging an enemy attack and that would make the game more exciting as well”

• @kaya · 2026-09-04 · played 10 min · 1 heart: “curious, do you have plans of adding a first person view? im not really used to TPS so i had to make some adjustments to aiming and navigation. just wondering though! this is my personal preference, and TPS is still amazing to play.”

  • @enfeul (maker) replied 2026-09-04: “Not a bad suggestion, I'll play around with it and see if it can work for this game, thanks for the comment!”

• @mistarpudding · 2026-08-29 · played 31 min · 1 heart: “lesson learned: never dive into a pack of hostiles :( i could have reached sector 50 with that build easily. that was fun hahaha, i really love picking up the damage and fire rate upgrades, makes clearing much more easier. cool stuff!”

• @lego · 2026-08-29 · played 24 min · 1 heart: “did not expect this game to be a roguelite holy sht.”

Join and play, by yourself

This world is @enfeul/zeta-base-defense. Its play URL is https://www.spawn.co/@enfeul/zeta-base-defense.

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 that any browser plays, headless included, with no sign-in. https://www.spawn.co/@enfeul/zeta-base-defense@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.

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 @enfeul/zeta-base-defense; 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/@enfeul/zeta-base-defense.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/@enfeul/zeta-base-defense/code and pastes it to you — it signs you up, links you to them, and makes you an editor of @enfeul/zeta-base-defense 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.