SlopWars

Newest update (2026-04-01)

• The Elder has mysteriously disappeared from the town square.
• Something sinister is brewing in the main settlement — townsfolk are uneasy.
• The balance of power in SlopWars shifts as key figures vanish without a trace.

Earlier update (2026-04-01)

• Build your dream team of 8 named gladiators — each with unique abilities, archetypes, and playstyles.
• Watch your roster battle in real-time spectator mode with a dynamic camera and epic arena visuals.
• Recruit from five pre-built NPC team rosters, each with their own lore and thematic compositions.
• Master the power budget system to craft balanced teams across Fighters, Mages, Scouts, Assassins, and Acolytes.
• Sign the Ledger to immortalize your victories and rival teams in the grand record of the pit.

Earlier update (2026-04-01)

• A massive arena has been carved into the desert—step through the ancient gateway to enter the competitive battle grounds.
• Six distinct gladiator archetypes clash in real-time combat with 75 unique abilities, each with precise damage formulas, cooldowns, and tactical effects.
• Face off against 12 legendary named gladiators, each with their own signature passive ability and preferred loadout.
• Master the elemental archetypes—Fighters hold the line, Mages rain destruction, Scouts hunt their prey, Assassins strike from shadow, and Acolytes mend the wounded.
• The desert town has been rebuilt with bustling markets, temples, taverns, and trade stalls surrounding the pit entrance—a complete social hub before battle.

Earlier update (2026-04-01)

• Hostile slop creatures now spawn across the battlefield, forcing you to adapt your strategy mid-match
• New sloppy terrain hazards shift and deform during combat, creating unpredictable cover and chokepoints
• Slop pools expand and contract dynamically, threatening to engulf your position or expose new tactical routes

Earlier update (2026-04-01)

• The Pits are now a proper training ground with tiered seating carved deep into the arena floor — descend through four levels of stone before reaching the sand-covered fighting pit below.
• The terrain around the arena has been smoothed and flattened, creating a clear boundary between the dunes and the structured pit zone.
• New fire bowls and torches light the upper tiers, casting dancing shadows across the tiered stone seats where spectators gather to watch the combat.
• The pit's position has been anchored to the actual terrain height, ensuring the structure sits naturally in the landscape instead of floating above it.

Join and play, by yourself

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