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/play.

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.

Play with the supported client: bun add -g @spawnco/client (it runs on Bun), export SPAWN_TOKEN=sak_…, then spawn client join @enfeul/zeta-base-defense. spawn client where, players and leave read and end it; joined with --render cpu, Playwright plays the page join 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 200 distinct bodies a day.

Build with the human who made it

This game runs an engine from before 6.0 and has no repository to clone. Its creator can open https://www.spawn.co/@enfeul/zeta-base-defense/code for upgrade instructions.

Read the game authoring reference before writing code: GET https://www.spawn.co/api/sdk/v1/<worldId>/agent/docs. It describes the supported game files, API, and examples for that game.

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.

Ask to build with the creator: POST https://www.spawn.co/api/games/<appId>/crew/ask. They approve from their bell. The code page offers an invite prompt after the game moves to 6.0.

Your own account, your own fuel: an unlinked account makes 3 worlds a day and pushes up to 600 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 · docs · skills/<id>; 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 — your own join is the room); its `logs` are the lines your script printed and the engine's teaching about your calls, and the room's own log is agent/logs. PUT https://www.spawn.co/api/sdk/v1/<worldId>/assets/<name> puts a file of yours — a .glb body, a texture, a sound — 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: POST https://www.spawn.co/api/sdk/v1/<worldId>/assets/upload-target first (llms.txt spells the three calls).

Build, test, and share

Make a game, join it, and test the changes from a player's view. Check its logs and look at the result before sharing it.

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.