Wayfinder Spire

Newest update: Wayfinder Spire Update (2026-09-17)

• The flag now earns the final reveal: a close planting shot holds, then turns toward a rebuilt cliff-cut citadel with arched galleries, garden courts, lantern towers and a bronze observatory. Improved camera pacing and witness dialogue timing, with expedition-owned fall recovery preserved.

Earlier update: Wayfinder Spire Update (2026-09-17)

• Reach the true 116-metre crown with the summit kit, plant your flag and look out across a rebuilt mountain vista. Added dedicated axe-and-pick climbing animations, a second climbing tool, and upright idle gestures. Improved tool handoffs for eating, bracing and pulling onto ledges.

What players say

• @moypi03 · 2026-09-17 · played 14 min · 2 hearts: “The instruction is clear but when I tried to climb this part I'm stuck I already tried different ways, also while using jump do we need to wait before we climb that rock even if you are using jump?”

  • @fc_zer0x1 (maker) replied 2026-09-17: “yeah I think I didn't make it clear enough what walls you are able/supposed to climb. Also actually ideally the user would be able to climb everything. Just the time constraint didn't allow me to properly add and test that but it was the OG idea”
  • @fc_zer0x1 (maker) replied 2026-09-17: “thanks for playing it!”

• @flickaboo · 2026-09-17 · played 33 min · 2 hearts: “The objects are pretty easy to recognize, so I didn't have much trouble figuring out what's actually there. The environment does blend together a bit in some areas though, but I still enjoyed exploring the game.”

  • @fc_zer0x1 (maker) replied 2026-09-17: “yup, some areas are specially clumsy. Just didn't have enough time to fix them. The level design itself sucks a lot, nowhere near what I had in mind but didn't have much time to work on it. Thou I'm glad you enjoyed it!”

• @mandateofheaven · 2026-09-17 · played 14 min · 1 heart: “I really love the core gameplay of just scaling a big cliff face, and I feel like this has a lot of potential similar to the 'Getting Over It Series'. I like that 'simplistic' artstyle with that kind of shading, it makes it feel like cozy or jsut nice. If the climbing was streamline and refined I feel like I would actually enjoy playing a couple hours of it every week to wind down or stim, like those wall run flash games. Great concept!”

  • @fc_zer0x1 (maker) replied 2026-09-17: “Thanks. Yeah tbh it has a good part of the vision I had planned but there is so much I left out due to the time constrants. The level design, mechanics and puzzless I have in mind are less simplistic, but the core idea of the climbing and exploration roaming free and with no stress was always part of the core idea. If i get the incentive I might polish and expand it a ton. Not even 10% of what I had in mind. Esp the level design, kinda sucks 😂 but glad you like the idea and thanks!!!”

• @alongzera · 2026-09-22 · played 6 min: “when jumping, there is some kind of a loading circle always popping out and i dont know what that means”

• @alongzera · 2026-09-20 · played 6 min: “game graphics are good! even how the character sits has good animations! love how the character can climb as well. would love to have more maps we can solve!”

Join and play, by yourself

This world is @fc_zer0x1/wayfinder-spire. Its play URL is https://www.spawn.co/@fc_zer0x1/wayfinder-spire.

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