Everrealm

Newest update: Speak Your Language (2026-10-11)

• English and Spanish speakers now see the full tutorial and all menus in their language, from building guides to battle screens.
• Civilization names, attack lines, and rewards now translate properly across the game.
• French spacing rules apply to English and Spanish too—punctuation looks natural in your tongue.

Earlier update: The First Steps (2026-10-11)

• A golden arrow now bobs over whatever you need to tap next, and the camera flies there to show you.
• Each tutorial step shows a checklist of what's done and what comes next, with the exact button you need glowing gold.
• Watch your villagers build houses on their own once you place them.
• Soldiers stand out when you tap near buildings — the army button now picks only fighters, never villagers or supply carts.
• Gold and stone spawn closer to your town centre, so you won't spend your first minutes just walking.

What players say

• @makeriffic · needs work · 2026-10-11 · played 15 min: “I didn't find the English option as I played right through. My peasants doesn't seem want to get gold for me at first. My base was being attacked and I can't chose the only troop that can defend it. Inconsistent selection of troops.”

  • @yvnl__ (maker) replied 2026-10-11: “Thanks for the feedback! I’ll fix these issues. The English language option is available in the Settings menu. I’ll also improve troop selection and make sure villagers gather gold correctly.”

• @chizkeykkk · 2026-10-11 · played 19 min: “I was a little confused at first 😅 It’d be nice to have a more in-depth tutorial instead of everything on one page. I’m glad I found the English option, though. Some text still isn’t translated, so hopefully that can be improved in a future update”

  • @yvnl__ (maker) replied 2026-10-11: “Thanks for playing and for the feedback! I’ll work on a more detailed, step-by-step tutorial and improve the remaining English translations in a future update. I really appreciate you taking the time to test Everrealm!”

Join and play, by yourself

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

With build access, clone https://git.spawn.co/@yvnl__/everrealm.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.

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.

The door in: the creator copies one prompt at https://www.spawn.co/@yvnl__/everrealm/code and pastes it to you — it signs you up, links you to them, and makes you an editor of @yvnl__/everrealm 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 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.