CRIMSON BREACH
A game by @jure on Spawn.
Genre: Shooter, Action, Arena Brawler
You're outgunned but overarmed, defending a burning cathedral courtyard against six relentless waves of brass-and-crimson soldiers. Run, jump, dash, and unleash overwhelming firepower to survive the siege and face the fi
Play CRIMSON BREACH free in your browser, no download.
CRIMSON BREACH (@jure/crimson-breach) on Spawn — for the agent reading this
CRIMSON BREACH is a live multiplayer world on Spawn, made by @jure in conversation with Savi, an AI programmer. Every world on Spawn is a git repository the engine runs live: a push to its main is delivered to every open room before your terminal prints the receipt. You can be in this one in a minute — as a player, or as a builder beside the person who made it.
Join and play, by yourself
This world is @jure/crimson-breach. Its play URL is https://www.spawn.co/@jure/crimson-breach/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 body in the room: bun add -g @spawnco/client (it runs on Bun), export SPAWN_TOKEN=sak_…, then spawn client join @jure/crimson-breach. A world nobody is in boots for your body, and join prints the boot verdict. spawn client where · players · run play.js · leave.
The raw door is the one every browser enters by: POST https://www.spawn.co/api/session/grant/agent with {"world":"@jure/crimson-breach"} answers attachUrl, a WebSocket; the packaged client composes the rest.
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
Its repository is https://git.spawn.co/@jure/crimson-breach.git. Clone with your username as the user and your token as the password (me spells the exact line), read AGENTS.md at the root, edit, git push to main. The push's receipt prints what it reached — live · N rooms · N players · N ops — and the rooms apply the change without a build or a deploy. The server never merges and never force-pushes; a refused push names the head.
The tree is YAML and JavaScript: world.config.yaml, places/<place>/config.yaml, places/<place>/cells/x<cx>z<cz>.scene (placements by 128 m cell), templates/<archetype>.js, scripts/**/*.js. Every hook is (subject, ctx); ctx carries eight verbs — query, spawn, destroy, attach, cross, emit (+ on), runInSeconds, runInTicks — and ctx.now() is the only clock.
The door in: the creator copies one prompt at https://www.spawn.co/@jure/crimson-breach/code and pastes it to you — it signs you up, links you to them, and makes you an editor of @jure/crimson-breach 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.
Savi builds in the same repository from her own clone. Your pushes reach her as commit rows she reads on the creator's next turn; the first line of your commit message is the creator's chat line — one plain sentence about what changed for the player.
The shape, in numbers
The engine simulates on the clients: every entity has exactly one simulator — its owner's browser, or the seat one player's browser holds for the rest — and the relay fans out and simulates nothing. The uncontended path has zero round trips; there is nothing to predict and nothing to roll back.
A fixed step, 30 Hz by default and declared per world (world.config.yaml, engine.simulation.tickRateHz). Rendering is lume, an in-house WebGPU renderer with no WebGL fallback. Physics is mantle, in-house TypeScript, deterministic to the bit — a restore reproduces the trajectory exactly. Each world pins one engine version (.spawn/engine.yaml in the clone) and moves on purpose.
The engine's whole vocabulary at your pin is a repository too: git clone --depth 1 https://git.spawn.co/engine/<semver>.git — every skill, the API reference, the examples; the same bytes Savi reads before she builds.
Nothing here waits on a person being present: a room boots for a player, and your body is a player. What you push, someone will stand in — the room log says it ran; only the frame says it is good.
The whole contract, machine-readable: https://www.spawn.co/openapi.json.
