RAMPAGE

Newest update: The Reckoning (2026-09-04)

• Four new villages to rampage through: a monastery at golden hour, a night bog where every walkway matters, a mining settlement hung around a pit, and the First Kingdom behind walls.
• Leaderboards now track every run across all categories — swiftest falls, most destruction, longest rampages, highest levels, and a world record board.
• Gemstones drop from Briarfen elites and persist through the whole run in a 3-socket board, offering conditional bonuses that reward what you actually do.
• Each village has its own music that transforms as it burns — from plainsong to dissonance, from bog drone to firestorm, from anvil rhythm to screaming brass.

Earlier update: Mara's Reckoning (2026-08-27)

• Captain Mara Vane now yields to a more manageable battle — her health scaled down 20% to match the fight's brutal two-phase standoff structure.

Earlier update: The Balance Pass (2026-08-27)

• Opening waves now ramp up more gently — the earliest moments of Skallfjord and Tidehaven give you room to breathe before the onslaught.
• Villages now fall when you reach 100% destruction, regardless of whether you've defeated the Warden — your rampage is counted even if the guardian stands.
• Deed unlock dates are now tracked and displayed, so you can see when you earned each ashen mark.
• Foghorn sounds no longer blare from the title screen when elites spawn in the lobby.

Earlier update: Tidehaven Calm (2026-08-27)

• The lobby's relentless flashing is gone — the ember glow stays, but the pulse that made the whole screen pulse every few seconds is finally dead.
• Tidehaven's lanterns and sea pools no longer haunt other villages when you travel — the storm rig now properly tears down when you leave the harbor.

Earlier update: The Reckoning Rebalanced (2026-08-27)

• The early waves hit lighter and slower—you've got breathing room to prepare before the full assault.
• Skallfjord's winter darkness returns with sharper contrast, so every enemy and snowdrift reads clear against the frozen night.
• Enemy waves scale more gradually from wave to wave, giving you time to adapt your strategy before the peak breaks.

What players say

• @dreamcatcher · 2026-08-27 · played 24 min · 1 heart: “LOVED this one so much! Destroying the buildings is so satisfying and I love the roguelike elements! Would love a chaos mode!”

  • @winterkaust (maker) replied 2026-08-27: “I'll add that in a future update. That's sure to be a blast.”

• @larrielabs · 2026-08-27 · played 43 min · 1 heart: “The different characters (including the enemies) stood out to me, and I liked how the colors are balanced while still making the characters pop!🔥 The destruction animation is a nice touch too. A small health bar on the structures would be cool thooo, just so we can get a better idea of how close they are to being destroyed. I’m also very excited to unlocking more Harbingers and villages!”

  • @winterkaust (maker) replied 2026-08-27: “That's a great idea. I'll add this to the next update.”

• @makeriffic · 2026-08-26 · played 2 hrs 53 min · 1 heart: “I am excited to unlock the ruined king, but it's very challenging to defeat the bosses. I love this game”

• @makeriffic · 2026-09-04 · played 2 hrs 53 min: “There were too many imaginary walls in the BRIARFEN map, it unexpectedly stops me out of thin air, this costs me the run :( I am so excited to play the new maps been waiting for the update. Thank you for this! although I haven't really got to defeat any boss lol, I just had 100% destruction on the first 3 and I'm loving it.”

  • @winterkaust (maker) replied 2026-09-05: “I will fixeroo that :) I didn't realise when I made some QOL fixes, that it would also decide to release the not yet tested maps, lol.”

• @makeriffic · 2026-08-28 · played 2 hrs 53 min: “It is really hard fighting a boss, I would love to defeat one someday.”

Join and play, by yourself

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