Coalesce "A Battle For Bricks"

A game by @imbigcrusty6967 on Spawn.

Genre: Action

Walk and jump on the blue forge to make physical bricks. Ride a growing brick cloud through 14 sky realms, steer rockets from their POV to steal rival bricks, and fight for the highest-rider crown. One shared sky: 10 AI riders hold the seats until real riders join and take them.

Coalesce "A Battle For Bricks" on Spawn now

Reviews: 100% loved it · 3 votes · 10 reviews and replies · 4 likes · 52 plays.

Released 2026-09-17. 6 updates since release, the newest 2026-10-22.

Newest update: One Sky: AI Rivals (2026-10-22)
  • Singleplayer and multiplayer are now one shared sky. AI rivals with real names fill the empty seats and show on the leaderboard, and every player who joins takes one's place. Knock a rival off and their whole cloud flies to you. Stolen bricks park neatly instead of sinking into the ground or squishing together by the walls. Rockets hit riders up close, arcade landings are safer, and bricks no longer break when shot.
Earlier update: Studio Ident & Title Polish (2026-10-07)
  • BigCrusty's studio intro now plays in full before the title screen appears—no interruptions, no menu music playing over it.
  • Title riders grip their launchers with both hands like battle riders do, and their arms stay locked in place while idle.
  • Solo sky no longer hangs on the title view when you enter singleplayer—radio stops looping and the round resets fresh.
  • Trailer camera system added for filming cinematic shots of the sky and riders in action.
Earlier update: Salvage Overhaul (2026-09-30)
  • Loot bricks now settle at a height you can actually jump up and grab them from, not floating out of reach.
  • Your own bricks rise back up beneath you when you land on them, even if a rival just blasted them loose.
  • Rocket engines finally shut up when their rocket explodes, and any lingering roar gets cut off.
Earlier update: Rival Minds (2026-09-25)
  • jev ai
Earlier update: BigCrusty's Coalesce "A Battle For Bricks" Update (2026-09-17)
  • Opened the space beneath the spawner and all four stair approaches in multiplayer and solo. Removed the tall invisible support column while keeping the stair treads, top landing, and forge solid. Player progress and existing artwork are unchanged.
What players say
  • @parz1val · 2026-09-21 · played 27 min · 1 heart: “This game is really fun, especially when you play it with friends tho XD. It’s way more enjoyable when you’re playing together and messing around.”

  • @yzykyl · 2026-09-19 · played 12 min · 1 heart: “Don't wanna spoil anything but the second part of the game can be it's own game in and of itself. Great job with this! Had insane fun and almost reached the top (fell short by 68 steps 😭). Anyway, I'll try again next time. Would love to see what's waiting for me up there.”

  • @flickaboo · loved it · 2026-10-22 · played 11 min: “Made it to 2,001 m with 50 bricks and somehow secured a top 3 spot on the leaderboard! 🧱🚀 Was pretty cool seeing my score up there haha.”

  • @yujiro · loved it · 2026-10-12 · played 21 min: “I had fun! Finding platforms after getting hit was challenging. I couldn't figure out why my enemy was higher than me when we stood on the same block.”

  • @sunraku · loved it · 2026-10-01 · played 1 hr 12 min: “Love the new climb in the arcade. At first it was pretty easy but as I progressed to the challenging part, it was as hard AF haha. I hope the other stuff in the arcade works. It feels great. I enjoyed the climb in the arcade much”

Coalesce "A Battle For Bricks". A sky scene with floating brick islands containing castles and minifigures. The title "Coalesce: A Battle For Bricks" is displayed above menu options for Multiplayer, Singleplayer, Guide, and Support - Spons. Taken for the update Studio Ident & Title Polish.Coalesce "A Battle For Bricks". A grassy park with green hills, colorful trees, and floating white platforms in a blue sky. A character with a round head stands in the foreground facing a wooden bridge, while other characters float above in the distance. Taken for the update Salvage Overhaul.

Play Coalesce "A Battle For Bricks" free in your browser, no download.

Coalesce "A Battle For Bricks" (@imbigcrusty6967/coalesce-a-battle-for-bricks) on Spawn — for the agent reading this

Coalesce "A Battle For Bricks" is a multiplayer game on Spawn, made by @imbigcrusty6967 in conversation with Savi. Open its play link to join. You can also ask the creator to build with them.

Join and play, by yourself

This world is @imbigcrusty6967/coalesce-a-battle-for-bricks. Its play URL is https://www.spawn.co/@imbigcrusty6967/coalesce-a-battle-for-bricks.

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, and a person's browser plays it with no sign-in. https://www.spawn.co/@imbigcrusty6967/coalesce-a-battle-for-bricks@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.

A browser a script drives, headless or not, plays signed in as your account: POST https://www.spawn.co/api/agent/v1/login-link with {"next":"/@imbigcrusty6967/coalesce-a-battle-for-bricks@dev"} answers a one-use URL that signs that browser in.

Unsigned, such a browser is a guest, and a creator's world refuses it: "this browser was opened by an automated tool, so it can't visit a creator's world as a guest. sign in, or open the link in a browser you use yourself." Its maker can ask Spawn to let their own automated tool in by name.

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 @imbigcrusty6967/coalesce-a-battle-for-bricks; 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/@imbigcrusty6967/coalesce-a-battle-for-bricks.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/@imbigcrusty6967/coalesce-a-battle-for-bricks/code and pastes it to you — it signs you up, links you to them, and makes you an editor of @imbigcrusty6967/coalesce-a-battle-for-bricks 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, 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.