Into the Breach Codexery

Hornet

Fast, furious, and always three tiles ahead of the swarm.

Hornet is one of the player-piloted mechs in Into the Breach, a turn-based tactical strategy game developed by Subset Games. Designed as a fast, aggressive assault unit, Hornet is a compact, angular machine built for speed and precision strikes against the Vek, the insectoid alien species that have torn open breaches across the planet's surface. In the player's arsenal, Hornet fills the role of a skirmisher and disruptor—dashing across the battlefield grid to stun, shove, and finish off Vek before they can overwhelm allied units.

While the game's broader narrative is conveyed through sparse terminal text and environmental storytelling, Hornet's role is clear: it is one of the few human-made machines capable of matching the Vek's speed and adaptability within the breach zones. Fans often favor Hornet for its mobility and the satisfying chain of Sting-then-Bash combos that let a skilled pilot control the tempo of an entire engagement.

Role
Player-controlled fast assault mech
Affiliation
Human defense forces (breach-response unit)
First appears
Into the Breach (2018, Subset Games)
Movement
3 tiles per turn (among the fastest mechs)
Signature abilities
Sting (damage + stun), Bash (knockback)
Status
Active in all standard campaign and skirmish modes

Lore & Background

In the world of Into the Breach, the Vek arrived without warning, splitting the landscape into unstable breach zones where their organic, chitinous forms pour out in waves. Humanity's response was mechanical: a small cadre of purpose-built mechs, each with a distinct silhouette and combat doctrine, deployed into the breaches to hold the line. Hornet was engineered for the specific problem of Vek that are too quick to corner and too numerous to fight head-on. Its compact frame, low profile, and high top speed make it the unit of choice when a pilot needs to cross open ground, isolate a single Vek, and deliver a stinging blow that drops it into a stunned, vulnerable state before delivering a final shove into a hazard or off the grid.

The game's narrative fragments—terminal logs, mission briefings, and the quiet environmental details of the breach zones—paint a picture of a world under sustained, grinding pressure. There is no grand victory screen; the mechs simply keep rotating into the next breach, the next sector, the next wave. Hornet, like its sister mechs, is a tool of attrition in a war that, from the player's seat, never truly ends. The tone is one of weary competence: the pilot knows the grid, knows the Vek's patterns, and trusts the machine to do what it was built to do.

Among the mech roster, Hornet occupies a specific tactical niche. Where Beetle soaks hits and Scorpion delivers heavy area damage, Hornet is the unit that repositions, picks off stragglers, and uses the battlefield geometry—hazards, edges, and Vek-to-Vek spacing—as a weapon. Its Bash attack, in particular, turns the grid itself into a tool: a well-placed shove can send a Vek into a lava pool, off a cliff, or into the path of an allied mech's next strike. This makes Hornet a favorite for players who enjoy puzzle-like, multi-step kills over straightforward damage output.

In Their Own Story

The breach hummed. Not the deep, tectonic groan of a new one opening, but the thin, insectile buzz of Vek already inside, already spreading. Pilot Yara felt the grid resolve under Hornet's sensors—six tiles of cracked basalt, two hazard pools, a cluster of three Vek clustered around a thermal vent. Standard. Manageable.

She punched the throttle. Hornet slid two tiles east, the servos whining a half-octave sharp, and the lead Vek turned its many-eyed head toward her. Good. Attention was a resource, and she was going to spend it.

Sting. The needle-tip struck the Vek's thorax, and it shuddered, legs locking, eyes dimming to a dull amber. Stunned. One turn of helplessness.

Yara didn't waste it. She pivoted, lined up the Bash vector, and drove Hornet's chassis into the stunned Vek's flank. It slid—two tiles, three—its legs scrabbling uselessly against the basalt—and its rear end kissed the edge of the thermal vent. The Vek dropped into the superheated pool with a sound like a wet slap.

Two left. She had four tiles of movement remaining and a clean path to the second one. The breach would hold. It always held, for a turn or two, and that was enough.

Yara exhaled. The next breach was already on the manifest.

Reader's Guide

The game's narrative is delivered in fragments: short terminal logs, mission headers, and the quiet visual language of the breach zones themselves. Before the invasion, the world appears to have been a settled, industrialized planet—metal structures, maintained infrastructure, a civilization that had built a defense doctrine around small, specialized mechs. The Vek's arrival shattered that routine. Terminal entries reference "breach containment" and "sector rotation," implying a standing order to respond to every new opening rather than a single decisive battle.

During the invasion, the tone shifts to operational grind. Mission briefings are terse: identify Vek composition, note hazard placement, hold the line. There is no dialogue between pilots, no radio chatter, no character banter. The narrative lives in the repetition—the same grid logic, the same enemy patterns, the same quiet satisfaction of a well-executed combo. The world is not saved; it is held, breach by breach, turn by turn.

Developer commentary and patch notes reinforce this: the game is designed as a loop of escalating pressure, where the player's skill is the only variable that changes. Hornet, as a unit, embodies that philosophy—no passive buffs, no narrative power-ups. Just a fast machine, a sharp needle, a solid chassis, and a pilot who knows where the edges are.

Did You Know?

More in History & The Vek Invasion

Elsewhere in the Into the Breach universe

Spotted an error? Know more?

This is a living reference — every entry is fact-audited, and reader corrections feed straight into our audit queue. Suggest an edit · See this site's audit record

Comments

Loading…
Open in the interactive codex →