slash dungeon

What players say

• @chizkeykkk · 2026-09-18 · played 14 min · 1 heart: “The game looks pretty decent, and that opening film was straight-up absolute cinema! I really enjoyed it and would love to see more maps added to explore.”

• @jeon · 2026-09-15 · played 11 min · 1 heart: “The game looks decent bro, I really love the part where I can roll over from the enemies and dodge their attacks using it haha. It makes the combat feel more fun because I can actually time my rolls and avoid getting hit. Nice game!”

• @makeriffic · 2026-09-12 · played 31 min · 1 heart: “Yo, I'm in love with this game. The visuals are kind of cute and I really like grinding the dungeon killing all the mobs and reaching all the bosses, I thought the Hollow King was the end but it turns out there was the Wither Valley, I was like 'what there's more?!, returning to the body when dying is a nice touch, although I think it is a bit too much if you are coming from the first stage and you have to crawl your way back where you died. Excited to see its next chapters!”

  • @bomb_bo (maker) replied 2026-09-12: “Thank you for finishing the game, I'm really happy about that. Don't worry, the beta version well come soon and i will make a huge update thanks <3”

• @mistarpudding · 2026-09-11 · played 35 min · 1 heart: “dude all the models look sick!! they're all very well made and the animations make them a lot cooler. i really love the game's design, and i know this is still in the works but i would really love to see an full built rpg like this! made my way until the third area and i had fun dodging attacks(my favorite part of the game!) i noticed that on the 2nd area and onwards, i wasnt able to see any damage indicators, could be a bug there”

  • @bomb_bo (maker) replied 2026-09-11: “Don't worry.. its just the alpha... wait the beta and thanks for playing the game <3”
  • @bomb_bo (maker) replied 2026-09-11: “Did you kill the last boss or not?”
  • @mistarpudding replied 2026-09-11: “i was able to reach him, but i died after two retries. took a while to go back to him because i spawned on the first area so i figured i should fight him next time haha”

Join and play, by yourself

This world is @bomb_bo/slash-dungeon. Its play URL is https://www.spawn.co/@bomb_bo/slash-dungeon.

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