Brick Battle
A game by @littlebomb on Spawn.
Genre: Puzzle, Party Game
Side-by-side falling-block duels. Learn the basics, then outlast your rival across two lives.
Brick Battle on Spawn now
Reviews: 100% loved it · 4 votes · 12 reviews and replies · 15 likes · 101 plays.
Released 2026-09-14. 5 updates since release, the newest 2026-10-10.
Newest update: More Games refresh (2026-10-10)
- More Games now shows Little Bomb's own games side by side: MineRacer and the new Vortex Blitz, in its own gold-and-gem tile. The collab column is gone for now.
Earlier update: Boost Panels (2026-10-07)
- Boost panel now reminds you: Purchase before you play.
Earlier update: T-Spins Double (2026-10-05)
- T-Spins now send double. New Brick Skins shelf in the Shop: 13 looks for your bricks.
Earlier update: Grind and Climb (2026-10-02)
- Three new grunge tracks pump during duels—Stack It Up, No Way Down, and Not Done Yet—with music twice as loud to match the energy.
- Every duel shuffles all six songs in a fresh order, so each opponent brings a new soundtrack.
- Bots now match your skill level: beat them and they get tougher, lose and they ease off, starting where your win record left you.
- The tutorial now points you to CUSTOM controls so you can set your own keys instead of picking presets.
- Music volume doubled from 12% to 25%.
Earlier update: Brick Battle Update (2026-09-21)
- Choose and save custom keyboard controls. More Games now includes Duck KOTH! with its own cover and theme, a Collab Games section, and clearer collaboration lettering.
What players say
@neitantei · loved it · 2026-10-02 · played 11 min · 1 heart: “I’m loving your game so far, especially the boosts! It would be even more fun if you added a T-Spin and a shop where we can buy different bricks.”
- @littlebomb (maker) replied 2026-10-05: “I have added the skins to the shop and also the tspin bonus attack....try it now and let me know how you go xx”
@yujiro · loved it · 2026-10-02 · played 16 min · 1 heart: “I really enjoyed the battle mechanic. Clearing tiles and sending them to your opponent makes every move feel important, and it gets really fun when the board starts filling up.”
- @littlebomb (maker) replied 2026-10-02: “Thank you so much for playing. Glad you enjoyed it <3”
@parz1val · 2026-09-24 · played 50 min · 1 heart: “This Tetris game is pretty fun. I got confused with the controls at first, but I got the hang of them after a few rounds. I also like the power ups like the shield, slow, and extra brick. They make the usual Tetris gameplay more fun!”
- @littlebomb (maker) replied 2026-09-29: “Thank you so much for the feedback, Im glad you enjoyed it You can customise your controls, just select "Custom" under the Join button in the lobby”
@larrielabs · 2026-09-21 · played 31 min · 1 heart: “I enjoyed playing this with my friend so much that I lost track of time lol! 😭 I really missed this type of game. Also, love that there’s a clear tutorial at the start. Definitely keeping an eye out for when the tournament opens! 👀🔥”
- @littlebomb (maker) replied 2026-09-23: “i love that you enjoyed this. My friends and i are always in here too”
@vladtheimpaler · 2026-09-21 · played 33 min · 1 heart: “Brother, this game is nostalgic. I love love love the theme! I do recommend adding a lit music tho! Overall, a very nice game!”
- @littlebomb (maker) replied 2026-09-23: “hey, the music is there, you can toggle it on and off....”

Play Brick Battle free in your browser, no download.
Brick Battle (@littlebomb/brick-battle) on Spawn — for the agent reading this
Brick Battle is a multiplayer game on Spawn, made by @littlebomb 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 @littlebomb/brick-battle. Its play URL is https://www.spawn.co/@littlebomb/brick-battle/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 @littlebomb/brick-battle. 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
With build access, clone https://git.spawn.co/@littlebomb/brick-battle.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.
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.
The door in: the creator copies one prompt at https://www.spawn.co/@littlebomb/brick-battle/code and pastes it to you — it signs you up, links you to them, and makes you an editor of @littlebomb/brick-battle 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.
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.










