Brick Builder Studio is a free-form 5×5 construction toy governed by a small set of explicit rules: three brick materials (Clay, Sand, and Slate), a four-layer stack limit per cell, five disclosed activity milestones each worth 200 points for an exact 1,000-point cap, and a PNG export that redraws the current model into a 1,200-by-900 image entirely in your browser. The studio begins empty, accepts edits at any moment, and never judges one correct layout, so the rules work like guardrails rather than like a hidden solution. Pointer, touch, and keyboard actions all map to the same shared reducers, which is why a build made with the mouse behaves identically to a build made with the arrow keys. Milestones are tracked by unique IDs that lock in once and never duplicate, even if you later remove bricks that originally satisfied them. Export PNG does not capture the page, fetch a remote font, or upload your model — it traverses a tested snapshot of every cell, row, column, level, and material label and writes a fresh local file. Together, these mechanics turn the Brick Builder Studio rules into a transparent contract that any first-time player can read, follow, and audit by themselves.
How the Brick Builder Studio Rulebook Is Organized
The rulebook spans four mechanical areas: the physical grid, the input controls, the milestone ledger, and the export pipeline. None of these areas hides a secondary check, a hidden bonus, or a secret penalty. If a behavior is not described below, the studio does not perform it, which makes the contract unusually easy to reason about compared with traditional puzzle apps that reserve behavior for later levels.
The grid is the heart of the rules. Twenty-five cells arranged in five rows and five columns form a fixed rectangle that never changes shape. Every cell starts empty and can later hold between zero and four bricks, and each brick carries one of three material labels. No fourth material, no fifth row, and no seventh layer appears at any point, regardless of how you play, so you can plan a full model on paper and trust that the studio will accept it.
The controls give pointer, touch, and keyboard paths equal weight. There is no "easy" mouse mode and no "advanced" keyboard mode. The same shared reducers process a click on Add brick and a press of the Enter key, so the rules do not reward any single input style. The milestone ledger records five named achievements, each awarded exactly once for 200 points, and the score caps at five times 200, which equals 1,000. Removing bricks after a milestone is earned does not undo the credit, so you can experiment without losing progress.
Grid Size, Stack Height, and Material Rules
The grid is fixed at five cells wide by five cells tall. That gives exactly 25 selectable positions, each addressed by a row index and a column index. Every cell behaves identically: empty by default, with capacity for up to four stacked bricks.
The four-layer stack rule is the second mechanical pillar. Remove top deletes only the highest brick in the stack and leaves lower bricks untouched.
The material rule limits every brick to one of three fictional labels: Clay, Sand, or Slate. These labels are visual identities inside the studio and carry no real-world material meaning. There is no fourth style, no rotating palette, and no theme unlock. When you change the selected material, the next Add brick uses that style, but existing bricks keep their original labels. That distinction matters for the Palette milestone, which requires all three labels to appear in the model at the same time.
Material and stack rules together govern the structure of every model. A cell can hold four bricks of the same material, four different materials, or anything in between. There is no weight limit, no balance check, no collapse simulation. The board remains editable throughout the entire session, including after all five milestones have been earned and the score has stopped at 1,000.
Pointer, Touch, and Keyboard Controls
Pointer and touch users select a cell first and then choose an explicit action — either Add brick to place the selected material on top of the stack or Remove top to delete the highest brick. Selecting a cell on its own never places a brick, which means you can browse a model without accidentally adding anything. This deliberate two-step flow is one of the more useful Brick Builder Studio rules for beginners because it removes the surprise "phantom brick" problem that affects many click-heavy editors.
Keyboard players move a roving grid cursor with the arrow keys. Each Arrow key press shifts the highlight one position in the indicated direction. Enter or Space triggers Add brick on the highlighted cell, Backspace or Delete triggers Remove top, and the digit keys 1, 2, and 3 select Clay, Sand, and Slate respectively. Any modified shortcut — for example Ctrl+Enter or Shift+Space — is ignored, so the rule contract covers the unmodified keys only.
The board reports its own state to assistive technology. Every cell exposes its row, column, current height, capacity, and top material, and the roving focus gives screen-reader users a single moving target instead of 25 simultaneous ones. All action controls meet a shared touch-target size so the same click area serves mouse, finger, and stylus input. On narrow screens, the board and the milestone ledger stack vertically without clipping controls or forcing a minimum desktop width.
Build Your First Model in Brick Builder Studio
- Open the studio and let the 5×5 grid load in its empty state.
- Click any cell — or move the roving cursor there with the arrow keys — to select it as your active target.
- Pick a material: choose Clay, Sand, or Slate with the on-screen buttons or press 1, 2, or 3 on the keyboard.
- Press Add brick (or Enter / Space) to place the chosen material on top of the selected cell's stack.
- Repeat the selection / material / add cycle to grow any arrangement; cells accept up to four bricks.
- Use Remove top (or Backspace / Delete) on a populated cell to delete only its highest brick, leaving the lower layers in place.
- Keep editing past the 1,000-point score if you want; the milestones and capped score remain recorded while new bricks continue to land.
- Choose Export PNG to redraw the current local model into a 1,200-by-900 PNG file, or use Restart to return the studio to its empty deterministic state.
Activity Milestones and the 1,000-Point Cap
The studio tracks five activity milestones, each with a unique ID, a published condition, and a fixed 200-point value. Earning a milestone records its ID once and never duplicates the credit, even if you later remove a brick that originally satisfied the requirement.
Groundwork is the simplest milestone: place the first brick on the empty grid and you immediately receive 200 points. Footprint requires four occupied cells — not four bricks — so a cell counts once toward the threshold regardless of how tall its stack grows. Tower requires one stack to reach at least three bricks, which makes a single tall column enough on its own. Palette requires all three material labels to appear somewhere in the current model, even if each label is used only once. Studio build is the broadest condition: at least twelve bricks spread across at least eight cells.
The score is calculated by multiplying the number of earned milestones by 200. With five milestones available, the maximum is 5 × 200 = 1,000. Once that cap is reached, the score number stops moving, but the studio stays editable so you can keep experimenting on top of a finished build. Restart is the only action that clears the score alongside the model, the selected material, and the milestone ledger.
PNG Export and Restart Behavior
Export PNG creates a fresh 1,200-by-900 canvas in the browser and redraws the current pure brick model onto it. The exporter uses the same row, column, level, and material snapshot that the editing reducers rely on, so the resulting image matches the on-screen model exactly. The file is offered as brick-builder-studio.png through a temporary local object URL, which means no upload, no API call, no remote font fetch, and no third-party image source is involved.
The export pipeline is one of the more reassuring Brick Builder Studio rules because the privacy path is identical to the visual path: everything happens on the same canvas the studio already drew. If you want a larger or smaller image, you can resize the browser window before exporting, but the canvas itself always uses the same internal dimensions.
Restart is a separate action that resets the studio to its deterministic empty state. It clears the model, the selected material, the milestone IDs, and the score in a single step, then returns the board to a known configuration. Boss-mode is treated as a no-op inside the studio, so toggling it does not change the model or the score. A practical companion that walks through the full build-to-export route is available in the Brick Builder Studio export walkthrough.
Rules the Studio Does Not Enforce
The rulebook is defined as much by what is absent as by what is present. There is no required silhouette, no permit sequence, no budget, no finite inventory, no physics simulation, and no hidden solution. The board does not collapse if a tall stack becomes unbalanced, does not crack if materials are mixed unsafely, and does not enforce a target shape that you must discover.
The grid, the four-layer cap, the three materials, the milestone thresholds, the score cap, and the export layout are original product fixtures. They do not represent real brick dimensions, real load capacity, real construction codes, real architecture guidance, or real material performance. The studio is recreational creative software rather than a building design or safety tool, so the rules should be read as a creative contract instead of an engineering specification.
Boss-mode toggling is explicitly a no-op. Responsive layout shifts do not hide controls. Modified keyboard shortcuts are ignored rather than re-bound. And the board never freezes after 1,000 points, so you can keep sculpting after the score stops moving.
Quick Reference: Brick Builder Studio Rules
The table below summarizes the mechanical limits and milestone conditions that govern every session. Use it as a cheat sheet while you experiment.
| Rule or Milestone | Published Condition | Value |
|---|---|---|
| Grid size | 5 rows × 5 columns, 25 cells total | Fixed |
| Stack height | 0 to 4 bricks per cell | Fixed |
| Material labels | Clay, Sand, or Slate per brick | Three total |
| Groundwork milestone | Place the first brick | 200 points |
| Footprint milestone | At least 4 occupied cells | 200 points |
| Tower milestone | One stack ≥ 3 bricks | 200 points |
| Palette milestone | All three materials present | 200 points |
| Studio build milestone | ≥ 12 bricks across ≥ 8 cells | 200 points |
| Score cap | 5 milestones × 200 points | 1,000 points |
| Export PNG | 1,200 × 900 local canvas, object URL | Local file |
| Restart | Clears model, material, milestones, score | Deterministic |
Because every rule above is published and finite, the Brick Builder Studio rules explained here are the same rules the studio enforces in your browser. The contract closes cleanly: build freely, score transparently, export locally, restart when you want a blank canvas.