BRICKBOTS

01 The Game

Brickbots: Undeleted is three games that refuse to stay separate: a free-form brick builder, a souls-slow combat game with parries and poise, and a reading game where the rarest loot is literate source code you inject into your base to make it real.

No difficulty settings. The game's rival scales by copying you — your weapons, your shield, your upgrades. A stronger you is a stronger him. The mirror is the difficulty slider.

02 The Story (spoiler-safe)

You wake on Homestead Plains — a fresh render of the Manuscript, with a Spark, a toolbox, and no memory of why. You build. You survive the Rust. You grow strong.

Then you clear your second land, and a transmission arrives on a card that glitches like your own interface:

"Hello, Builder. Your Spark is a good teacher."

"Thank you for the lessons."

— UNKNOWN SENDER

Someone has taken your home. Someone with your frame, your mechanics, and your Spark — because he has been hacking everything you own and learning everything you learn. The campaign is the collision: five hand-authored lands, three duels against a rival who parries what you parry and shields what you shield, a manuscript scattered across a highland, a road set on fire to slow you down, and a truth at the end of the world that no wall can keep out.

The player never speaks. Your buildings are your dialogue — and late in the story, someone reads them back to you. The quest log is your inner voice, and near the end it stops being sure of itself. The last button in the game is a choice, and it is re-choosable only at the moment it was made.

03 Characters

04 Combat

Third-person, souls-like, forgiving. Every defensive verb is a timing question, and every timing question is telegraphed.

The three meters

Every land past the first tightens the air: more weapon heat, thinner stamina. The world itself is a difficulty curve you can see on the map.

05 The Manuscript the learning loop

Brickbots' rarest loot is readable source code — real, commented, honest excerpts of the code the game actually runs. Find a page, and you can read it like a book. Inject it at your Spark, and it becomes real.

/// How an enemy chooses which defense to hit. The rule fits
/// in a sentence: a threat is eligible if it stands inside
/// your attack range or inside its own taunt reach, and the
/// one that feels nearest — distance minus taunt — wins.
/// The subtraction is the whole trick: a bunker fourteen
/// studs away feels like it is standing on the enemy's foot,
/// which is exactly what a bunker is for.
let pull = distance - threat.tauntStuds * pitch
if best == nil || pull < best!.pull { best = (threat, pull) }

The comments teach the logic, not the syntax — why turrets overheat, why the sentry walks home, why enemies hit walls. Reading is never homework: injection only asks that the pages are in hand. But a player who read the turret's file already knows where to place it — and a kid who read all nine has quietly learned how game AI is written.

Later, a second library appears: the combat archive — annotated pages about your own systems, in someone else's handwriting. Collecting a discipline's fragments fits a permanent stat; completing it unlocks a build:

One build active at a time. "None" is a valid choice. No trees, no respec tax — just one passive, one stat, and a decision.

06 Defenses & Building

Your base fights back. Plant automated defenses anywhere there's open level ground — they hold their wounds between sessions, and destroyed means planting again at full price. Cover you hesitate to buy is cover you die without.

And under it all, the builder's game: an unbounded brick lattice, streamed in chunks, with collapse physics, blueprints, buildable vehicles, a programmable bot — and a world that saves every brick, per land. Waves mode turns your own base into the objective; camps and bosses never lock building, ever.

07 Arsenal

08 How to Play