The Covenant

Lore & Background

In the world of Oxygen Not Included, the duplicants arrive on a cross-section of an alien planet with no memory of who sent them or why. The Covenant is the name that surfaces in their logs, in the mission briefings, and in the quiet, almost liturgical language the game uses to describe their duties. It is less a government with a capital city and more a compact: a set of conditions under which the duplicants were created, deployed, and expected to persist. The phrasing in the story text carries the weight of a founding document—obligations, resource quotas, survival imperatives—delivered not with malice but with the flat, bureaucratic calm of an institution that has done this many times before.

In Their Own Story

The log entry is timestamped, as all of them are, in the colonists' shared internal clock. No name is attached. Just the number, and the words: "Day 47. I watched Maren rebuild the water reclaimer for the third time. She hummed while she worked. Not the mission hymn. Something else. Something with a melody that didn't match any protocol. I asked her what it was. She said it was hers. I don't know what 'hers' means in this context. The Covenant does not have a category for a song that belongs to one person. I filed the observation. I did not file the feeling." The entry ends there. No follow-up. No corrective note from above. Just the quiet, terrifying silence of an institution that has not yet decided whether to notice.

Reader's Guide

The Covenant does not manifest as a buildable structure or a visitable settlement in the traditional sense. Its "architecture" is the story mode's chapter structure itself: each chapter is, narratively, a Covenant directive. The player's base is the locus where the Covenant's will meets the duplicants' reality.

In practice, the Covenant's influence shows up in three layers. First, the mission text: short, formal directives that frame each chapter's goals in the language of obligation rather than choice. Second, the duplicant dialogue: occasional lines that reference "the mission," "the protocol," or "what we were made to do," grounding the colony in a larger purpose the player never fully sees. Third, the structural pressure of the game systems themselves—oxygen, heat, food, water—functioning as the Covenant's invisible hand, ensuring that survival is never guaranteed and always conditional.

For players who want to lean into the Covenant's narrative weight, the design philosophy is one of restraint: let the player build, let the duplicants thrive, but keep the mission text in the corner of the screen like a letter from a parent you never met. The engineering choice that makes this work is that the Covenant never blocks, never punishes, never locks content. It simply *frames*. Remove the story mode and you lose the Covenant entirely; the game becomes a pure sandbox. Keep it, and every oxygen tank you place feels a little more like an act of quiet defiance.

Did You Know?

• The Covenant is never represented by a visible NPC, base, or physical structure in the game world; its presence is entirely textual and structural, embedded in mission briefings and duplicant dialogue.
• The duplicants' internal language in the story mode uses the phrasing of a compact or founding document—obligations and conditions—rather than the language of a government or military command, reinforcing the idea of a c
• Removing the story mode (playing in sandbox or free-play) effectively erases the Covenant from the experience, turning the game into a pure colony simulation with no narrative authority pressing on the player.
• The Covenant's most powerful 'tool' in the game is the resource-management loop itself: the relentless need to balance oxygen, heat, and food functions as the institutional pressure that keeps the duplicants (and the pla