Breach Cycle

Lore & Background

The Breach is not a door in any conventional sense. It is a wound in the local geometry of space, a shimmering tear through which the Vek cross from wherever they originate. The exact nature of the Vek homeworld—or whether they even have one—remains unexplained in the game's presentation. What is clear is that the breach is a one-way conduit for the Vek: they pour in, they attack, and when the cycle ends, the rift seals and they are gone, only to return when the next cycle begins. This repetition suggests the Vek are not conquering in a traditional sense but are drawn to something on this side of the breach, or are compelled by a biological or temporal imperative to strike, retreat, and strike again.

The mechs that defend against these incursions are the Goliath, the Wasp, the Hound, and the Titan—four distinct platforms with different armament, mobility, and support roles. They are not the only defenders; civilians populate the grid and are the primary objective. The Breach Cycle thus creates a moral and tactical tension: the mechs must position themselves to intercept Vek threats while simultaneously shielding fragile human lives from collateral damage, Vek attacks, and even the mechs' own heavy weapons. Every turn is a negotiation between aggression and protection.

The Vek themselves come in several types—small, fast ground units; larger, slower brutes; aerial raiders; and spitting or ranged variants—each exploiting a different tactical niche. Their emergence from the breach is not random; they appear in specific locations on the grid, and the player must read their positions, anticipate their movement, and commit mech resources accordingly. The Breach Cycle, then, is as much a puzzle of spatial reasoning as it is a narrative of survival.

In Their Own Story

The ground hummed before the sky split. Sable pressed her palm flat against the Goliath's viewport, feeling the low vibration travel up through the chassis, through the servos, through the bones of her fingers. Three civilians huddled in the alley behind the ruined market stall, their faces pressed to the glass, watching the air above the plaza wrinkle like heat-haze turned violent. A seam of violet light crawled across the grey sky, and the first Vek dropped through it with a sound like a car door slamming in an empty garage.

"Cycle's open," she said. Not a question. Not a warning. Just the fact of it, the way you'd say *rain's coming*.

The Wasp was already rotating its turret. The Hound had dropped into a low crouch on the far side of the plaza, its claws scraping concrete. And the civilians—she could see them counting the Vek the way you count teeth in a mouth you don't want to open. Sable exhaled. The breach was still widening. More shapes were folding through the light, chitin clicking, mandibles testing the air.

She keyed the comms. "All units, civilians are priority. I don't care what they're doing. I don't care if they're right on top of you. You do not put a shell within ten meters of those people. Understood?"

A pause. Then: "Understood, Sable."

The first Vek hit the ground and ran. Sable hit the throttle. The cycle was young. They had time. They always had time. That was the thing about the Breach Cycle that never got easier: the time was always just barely enough, and the next cycle was always already forming in the dark behind the last one.

Reader's Guide

The narrative of the Breach Cycle is assembled not from a single script but from the accumulated texture of the game's presentation: the briefing screens, the environmental storytelling of each map, the Vek emergence patterns, and the quiet moments between rounds.

Before the breach, the world is a place of ordinary life interrupted. Civilians populate the grid in clusters—near market stalls, behind barricades, in the lee of collapsed structures. They are not soldiers. They do not fight back. Their presence is the entire reason the mechs are there, and the game makes this abundantly clear through the damage feedback when a civilian is hit. The tone is one of a community that has learned to live in the shadow of the rift, to brace, to flatten, to wait for the sky to tear.

During the breach, the Vek emerge in waves. The first wave is usually small and fast—ground units that sprint toward the nearest civilian cluster. Subsequent waves introduce heavier or ranged threats. The player's mechs must intercept, reposition, and protect, all while managing their own positioning to avoid friendly fire and Vek area attacks. The breach location on the grid is a fixed point of danger; Vek can re-emerge from it in later turns, making it a persistent threat rather than a one-time event.

Between cycles, the game offers a brief respite. The mechs reset, the board reshuffles, and the civilians are either safe or gone. There is no persistent damage to the mechs across rounds, but the emotional weight of a lost civilian carries forward in the player's memory. The Breach Cycle, narratively, is a world that has stopped expecting the threat to end. It simply expects the next one. And the mechs, in turn, simply expect to be there when it does.

Did You Know?

• The Breach is not merely a narrative backdrop; it is a mechanical anchor. Vek can re-emerge from the breach location in later turns of a round, making it a persistent spatial hazard rather than a one-time spawn event.
• The four mechs available in Into the Breach—the Goliath, Wasp, Hound, and Titan—each represent a different tactical philosophy for engaging the Breach Cycle: heavy direct fire, rapid repositioning, area denial, and range
• Civilians in Into the Breach cannot be healed or revived within a round. If a civilian is destroyed, they are gone for that engagement, which makes positioning and threat-priority decisions during the Breach Cycle carry
• The Vek do not appear to communicate, strategize, or adapt in any visible way. Their behavior is driven by simple targeting rules—primarily the nearest civilian or the nearest mech—giving the Breach Cycle the feel of a n