The Architect

About The Architect

The Architect turns a sliding-tile puzzle inside out. You never swipe, and you never merge. A machine called the Engine does that, and it is good at it — it searches two moves ahead and assumes you will drop the cruellest possible tile next. Your job is the board itself: every turn you place one piece into an empty square, and the Engine immediately takes its best move in reply.

The tension comes from what merging does for it. Every merge the Engine lands frees a square, and a tile that reaches 32 escapes the board entirely and hands it another. Four escapes and it breaks out and wins. Deny it a merge and you slowly earn stones — permanent blocks that never move and never merge — but they arrive every second denial, not on demand, so you cannot simply wall it in. Trap the Engine with no legal move to win, and your score is how few moves it lasted.

How to play The Architect

Pick a tile from your tray at the bottom, then click any empty square on the board to drop it in. That is your whole turn. The Engine then slides the entire board in whichever direction its search likes best, and an arrow flashes to show you which way it went.

Merges are what keep the Engine alive, because each one frees a square. When it slides and merges nothing, you have denied it — and every second denial earns you a stone. Stones are placed like tiles but never move and never merge, so each one permanently shrinks the space the Engine has to work in.

A tile that reaches 32 escapes the board and frees its square, and the counter at the top tracks how close that is to costing you the game. Let it bank four escapes and the Engine breaks out and wins. Trap it so that no direction changes anything and you win — in as few placements as you can manage.

How to play The Architect, turn by turn

1. Look over the starting position: a five-by-five board with three small tiles already on it, a tray of three tiles beneath, and one stone in hand.
2. Choose your piece. Each tray tile is a 2, a 4 or an 8, and the stone slot shows how many stones you hold. The line under the tray counts down the denials needed for your next stone.
3. Click a highlighted empty square to drop the piece. "THE ENGINE IS THINKING" appears briefly, then the whole board slides and an arrow shows the direction.
4. Read its reply in the "Its moves" log on the right. Each line gives the direction and either the points it gained from merging, "denied" (with a ◆ when that denial earned you a stone), or "ESCAPED" with a count.
5. Keep an eye on the Escapes card. At three out of four it switches to a warning state, because one more escape ends the board.
6. The board ends as "TRAPPED" when no slide can change anything or every square is filled, or "IT BROKE OUT" after the fourth escape. The result panel gives a summary you can share, plus a button for a new board.

The Architect tips and strategy

• Use the 4s and 8s to surprise it. When the Engine looks ahead, it assumes your next piece will be a 2 dropped in the worst square. A 4 or 8 placed where it cannot pair up is a reply it did not plan for.
• Expect the biggest tile in a corner. Its judgement values free squares above everything, then neatly ordered rows and columns, then keeping its largest tile in a corner. A stone beside that corner disrupts all three at once.
• A stone splits a line in two. Tiles slide up to a stone as if it were a wall, and each side of the line collapses separately. A stone in the middle of a row turns one long lane into two short ones where pairs rarely meet.
• Stones cap at three. You only earn a new one while holding fewer than three, so denials you land while holding three mostly go to waste. Spend one before the hand fills.
• Your own placement can finish the game. If the piece you drop leaves no slide that changes anything, the board is trapped at once and the Engine never gets its reply.
• Most new tiles are 2s. Every piece you place is replaced at random, usually with a 2, sometimes a 4 and only occasionally an 8. An 8 is a scarce resource, so use it where its size matters.
• Undo goes a long way back. Z or the Undo button rewinds up to forty placements, stones and stone progress included, for testing a risky drop.

What a good score looks like

Your result is the number of placements the Engine survived, and stones count as placements. The developer's notes on balancing give a useful yardstick: in simulated play, dropping pieces at random always lost, careless play that still won took about 56 moves, casual play about 47, and strong play about 35. A board under 40 puts you closer to the strong end than the casual one.

The panel on the right helps you track that. "Pace vs your best" fills as the current board goes on, measured against your fewest-moves record (or against 45 until you have one). Below it, the run summary counts stones used, merges denied, merges the Engine made and its own points, and your record keeps boards trapped, boards lost, fewest moves and boards played across visits in the same browser.

Those numbers come from a rebalance: early testing showed stone-spamming could win on its own, so escapes became a loss, stones moved to every second denial and the tray gained mixed values. The choice of piece and square now decides most boards.