Maw

Lore & Background

The Vek that pour through the Breach are not a single species but a vast, alien ecosystem, and the Maw sits near the top of that food chain. Where Spitters spew caustic globules and Chompers lunge with serrated jaws, the Maw is a slow, grinding force of nature—a many-part body that seems less like an animal and more like a living siege engine. The Goliath pilots who face one describe the sound: a wet, grinding rasp as its segments shift and reposition on the grid, each one a separate threat that must be accounted for in the next turn's plan.

Tactically, the Maw's segmented design is both its strength and its vulnerability. A Goliath can focus fire on a single segment, destroying it and reducing the creature's reach, but the remaining segments do not simply collapse. They continue to advance, to threaten, to force the pilot into reactive positioning. This creates the signature Maw fight: a grinding attrition where the pilot must decide which segments to prioritize, whether to split forces, and whether the Goliath can survive the turns it takes to bring the whole creature down.

In the sparse narrative text that threads between levels, the Maw is never given a name or a voice. It is simply *there*—another wave, another escalation, another reminder that the Vek are not a single enemy to be defeated but an ongoing ecological pressure. The Goliaths do not conquer the Breach so much as hold it, turn after turn, against waves that keep coming in ever-larger configurations.

In Their Own Story

Turn four. The Maw's rear segment had just cracked free from the rest of its body, tumbling two cells to the east with a sound like wet stone dragging across tile. Kael didn't flinch. She'd seen the segment count drop from five to four and her jaw had tightened, not loosened—four was still four separate things that wanted to be in her cockpit.

The Goliath's targeting frame flickered. Two segments still had line of sight on the civilian shelter three cells south. If she swung wide to hit the front maw, the rear pair would close. If she held ground, the front maw would reach the shelter's wall and start chewing.

She exhaled. Shifted the thrusters. The grid hummed under the Goliath's feet as it slid one cell left, just enough to put the front segment in the crossfire of her next shot while the rear pair scrambled to reposition. The Maw's remaining body segments ground forward, slow, patient, inevitable.

Turn five. One segment down. Three to go. The shelter held. For now.

Reader's Guide

The narrative framing of the Maw's appearances is built from the brief inter-level text that Subset Games writes between each tactical round. These short passages never name the Maw directly but describe escalating Vek pressure—waves growing larger, more varied, more coordinated. The Maw enters this escalation as the point where the enemy stops being a swarm and starts being a *presence*.

The in-game codex entries for Vek creatures are deliberately terse: a name, a one-line behavioral note, a small icon. The Maw's entry is no exception, but its icon is noticeably larger than the others, and the behavioral note hints at its segmented nature without spelling out the full mechanic. This restraint is part of the game's design philosophy—let the player discover the Maw's multi-part vulnerability through play rather than through a paragraph of exposition.

Developer commentary from Subset Games (Soren Johnson and team) has emphasized that the Maw was designed as a "puzzle enemy"—not a damage sponge, but a spatial problem. The player must think about which segments to remove, in what order, and how the remaining segments will re-route. This makes the Maw a natural capstone for a level's difficulty curve.

The broader world-building remains intentionally thin. There is no Vek homeworld described, no invasion fleet, no alien politics. The Breach is simply *the Breach*, and the Vek are simply *the Vek*. The Maw's lore is whatever the player builds around it in the heat of a turn-three decision under time pressure.

Did You Know?

• The Maw's segmented design means a single Goliath shot can remove one body part while the rest keep advancing, forcing the player to re-evaluate their plan mid-fight rather than simply 'killing the big one.'
• In the game's visual language, the Maw is drawn with a distinctly different color palette and larger sprite than smaller Vek, making it immediately readable on the grid as a high-priority threat.
• The Maw never speaks, is never named in narrative text, and has no individual identity—it is purely a creature of the Vek ecosystem, reinforcing the game's theme of the Goliaths fighting an endless ecological pressure ra
• Because the Maw occupies multiple grid cells, it interacts with the game's movement and adjacency rules in ways smaller Vek do not, creating unique blocking and pathing challenges for the Goliath.