THE BATTLEBLOCKS AI DEVLOG

A game, taking shape.

Notes from the build. Real milestones, open questions and a few blocks along the way.

Subscribe by feed: RSS. No account or email needed.

Catch up

Every update we email is published here, newest first, so you can read what you missed. Posts marked "Newsletter issue" are the ones we email to people who have confirmed by the time they are published (the first issue also goes to anyone who joins in its first week); if you joined later, read the rest here. No account or sign-in is needed.

05 OCT 2026 / NISSAN DOOKERANNewsletter issue

Issue 1: the idea, and what exists so far.

What BattleBlocks AI is meant to be, what has been built and checked so far, and what you will hear from us next.

Read the devlog ↗

A phone-shaped screenshot from an Android emulator. Chrome shows localhost:8080 and a page titled Engine touch sandbox. A tall board holds a stack of blue blocks with a teal Z piece falling above a line marked row 8, and buttons for left, rotate, right, hard drop, resume and restart sit underneath. — Screenshot of the engine touch sandbox (source a85c6a0, WASM sha256 bf90a3a0) running in Chrome inside an Android emulator on a Mac, captured 3 October 2026. Made from sandbox-emulator-play.png (sha256 47025fc6): status bar and navigation bar cropped off, scaled to 800 px high, placed on a plain dark card and saved as WebP. It is an emulator, not a physical phone.

04 OCT 2026 / NISSAN DOOKERAN

Before the phone, we put a tiny slice in an emulator.

A first look at the smallest slice of BattleBlocks AI running in an Android emulator, and the problems we are trying to find while it is still small.

Read the devlog ↗

02 OCT 2026 / NISSAN DOOKERAN

Before the first duel, get the rules right.

The foundations of an asymmetric block battle.

Read the devlog ↗