Greenfall

Newest update: Greenfall (2026-09-04)

• Updated to engine version 5.2.40

Earlier update: Greenfall (2026-08-28)

• Updated to engine version 5.2.34, fixed a bug where the bow or the pistol wouldn't be able to hit the Tarwings (Flying enemy)

Earlier update: Greenfall (2026-08-15)

• Updated to engine version 5.2.25

Earlier update: Greenfall (2026-08-13)

• Added better onboarding, the tutorial now gives you some starting items and a map, added some events up to day 5

What players say

• @jeon · 2026-08-31 · played 30 min · 1 heart: “Really enjoying this so far. I like how easy it is to figure things out without needing a bunch of instructions. Some of those mobs really don't give you a chance 😂 but I'm still down to play more and see what gets added next.”

• @jeon · 2026-08-29 · played 30 min · 1 heart: “this game is actually really good, i had fun just running around and exploring the village. my favorite part was finding new areas and talking to the different characters. would love to see more places to explore and more stuff to discover.”

• @mistarpudding · 2026-08-17 · played 1 hr 42 min · 1 heart: “Had lotsa fun exploring the map and killing stuff so that I could sell whatever drops they gave. Used a bow for my entire 10 day run cause I thought they were the cheapest way to get by. also, i can't shoot down that bird with my bow :/ might need a gun”

  • @enfeul (maker) replied 2026-08-17: “I honestly didn't expect anyone to play for that long hahaha, but hopefully you had fun! There is a gun on the shop, but honestly the bow should have been able to shoot the bird down, I'll have to do a proper check, thank you for the comment!”
  • @mistarpudding replied 2026-09-04: “hi! played the game again and i got news for ya! I finally killed a tarwing with my bow!! they were much easier to hit now (w/ scope), so i was able to land 3 arrows right there and then. the items they drop dont have an image though, they just present themselves as a blank item with a name.”

• @lego · 2026-08-17 · played 51 min · 1 heart: “i didnt realize an hour had alrdy passed lol and am still on day 6”

  • @enfeul (maker) replied 2026-08-17: “I hope you enjoyed the game! When I have some time to spare, I will return and update this project more, hahaha.”

Join and play, by yourself

This world is @enfeul/greenfall. Its play URL is https://www.spawn.co/@enfeul/greenfall/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.

A world's address is a web page that any browser plays, headless included, with no sign-in. https://www.spawn.co/@enfeul/greenfall@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/greenfall; 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

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

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.

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