Into the Breach Codexery

Block

Stand in the hole. Hold the line. Let nothing crawl out.

In Into the Breach, the Breach is a ragged wound in the ground from which waves of hostile bugs pour each turn. The single most important strategic act a player can perform is to place a mech directly on that tile—colloquially called 'blocking' the Breach. While a mech occupies the Breach, no bugs can emerge from it, effectively silencing the enemy's spawn point for as long as the mech holds position.

Block is not a flashy area-of-effect ability with a cooldown bar; it is a positional, ever-present mechanic available to every mech in the roster. Its simplicity is deceptive: deciding when to block, which mech should hold the tile, and how long you can afford to commit a unit to a static position is the central strategic tension of every single turn in the game.

Quick Facts

Type
Core positional mechanic
Target
The Breach tile
Effect
Prevents bug emergence while a mech occupies the tile
Range
0 (must be on the Breach tile)
Available to
All mechs (by positioning)
Cost
Movement; opportunity cost (no mana or charge required)

Lore & Background

The Breach is not a natural feature of the terrain. Each turn, the wound convulses and spits out chittering, multi-limbed bugs that scatter across the grid in search of prey. The mechs—clumsy, brightly colored, improbably sturdy machines built by a civilization that refuses to simply flee—are the only thing standing between the Breach and the settlements beyond. Blocking the Breach is, in the most literal sense, putting your body in the way of the apocalypse.

A mech pilot who drops their machine onto the Breach tile is making a quiet, enormous statement: you will not pass through me. The bugs pile against the hull, mandibles scraping metal, but the spawn is denied. It is not a kill. It is a refusal.

Over the course of a battle, the Breach may be blocked, unblocked, and re-blocked as the player juggles threats, protects civilians, and maneuvers for position. The rhythm of the game—the satisfying click of a mech settling onto the Breach tile, the brief silence where no new bugs appear—is the heartbeat of Into the Breach. It is the mechanic that turns a grid of squares into a story about holding the line.

Reader's Guide

Blocking the Breach is the single highest-priority action in most turns, but it is not always the only action. Because any mech can block simply by standing on the tile, the real decision is which mech to commit and when to release it.

Early in a turn, if the Breach is unblocked and bugs are about to spawn, prioritize moving a mech onto it before your opponent's (the AI's) bugs act. A mech with a longer movement range or a dash-type ability can often reach the Breach from further away, preserving your other units for offense or civilian rescue.

Terrain matters. If the Breach is adjacent to a cliff edge or a narrow corridor, a blocked Breach becomes a natural choke point—bugs that do spawn are funneled into predictable lanes where your other mechs can intercept. Conversely, if the Breach sits in open ground, unblocked bugs scatter in multiple directions, making them harder to catch.

Synergy between mechs is key. A tanky, high-armor mech (think Warden or Guardian-class) is ideal for holding the Breach because it can absorb the bugs that pile against it while your glass-cannon attackers (Magma, Volt) stay free to clear the field. If you must use an attacker to block, you lose a turn of damage output—so time your block for turns when the bug count is low or when civilians are safe.

Remember: the Breach is a single tile. You can only block it with one mech at a time. If you need to reposition, the Breach is open again for one turn. Plan your unblock carefully, or accept the cost of a new bug wave.

Did You Know?

What players say: Player verdict on Into the Breach — Rotten Tweets

More in Abilities & Mechanics

Elsewhere in Into the Breach

Spotted an error? Know more?

Reader corrections go straight into our review queue. Suggest an edit · How this site is sourced

Comments

Loading…
Open in the interactive codex →