Quasimorph Progression Guide

Progression in Quasimorph is not a single level bar. It is the relationship between the flagship, contracts, crew, equipment, factions, technology, implants, pacts, and the resources that make another attempt possible. The safest long-term plan is to improve the part of the system that caused the last failure. If a run failed because the carrier could not leave, buy survivability or route control; if it failed because the ship could not support the next contract, invest in the relevant upgrade instead of chasing a shiny weapon.

Read progression as a loop

The loop is prepare, contract, extract, sort, upgrade, and prepare again. A ship upgrade matters only when it changes what contracts you can safely attempt. A rare item matters only when the crew can use, repair, and return it. A faction relationship matters when it opens a useful mission or trade path. Before buying or unlocking anything, write the next concrete problem it solves.

This approach also prevents over-investing in a single operative. A mercenary can carry an important build, but the campaign needs a replacement route. Keep basic equipment and a usable secondary role for a new clone. If a progression choice makes the whole ship depend on one character or one resource, treat that dependency as a risk to reduce.

Ship and technology decisions

Ship upgrades determine what the operation can do between missions: process information, improve production, support travel, make equipment available, or open a new interaction. The exact tree and order should be checked in the current game because 1.0 changed systems and 1.0.1 continued interface work. Do not follow an old “rush this upgrade” list without matching its branch, save, and objective.

Use a three-question filter. Does the upgrade help the next contract? Does it help recover from failure? Does it unlock a route that is currently blocked? An upgrade that answers none of these can wait. When several upgrades are useful, prefer the one that creates more future choices rather than the one that increases one narrow number.

Clones, classes, and implants

Clones let the campaign continue, but they do not remove the cost of poor preparation. Give a new operative a low-risk contract, observe how their class or equipment interacts with the map, then commit them to a specialist role. Keep the first mission focused on learning the controls and the risk signal rather than maximizing the haul.

Implants and augmentations are progression decisions with operational consequences. Confirm where they are equipped, what resource they consume, what action they change, and what downside they introduce. If the implant affects a meter, movement, body part, or weapon slot, test it in a contract where evacuation remains possible. A build is complete only when it remains useful after the effect’s cost appears.

Pacts, rites, and banes

The 1.0 patch notes describe a Pact Department, a total of 142 pacts, and a distinction between pacts obtained through different activities. Those are official version facts; the practical value of a specific pact still depends on the live screen, operative, mission, and current balance. Treat pact power as borrowed advantage, not a free upgrade.

Before absorbing or upgrading a pact, identify its immediate benefit and its long-term failure mode. If it raises a danger or bane pressure, decide how the crew will reduce or survive that pressure. Never spend the campaign’s last safe resource to test an effect in a critical descent. A pact that makes one room easy can still be the wrong progression choice if it makes the extraction route impossible.

Resource priorities

Sort resources into four groups: mission consumables, repair and crafting inputs, ship-upgrade requirements, and flexible trade value. Keep a small reserve in each group. Spend flexible value when it closes a specific gap, not when the inventory becomes visually full. If a material has an unclear use, hold it until the next recipe or trade screen explains its role.

The best resource is sometimes a completed return. A contract that brings back less but preserves treatment and a usable weapon may move progression farther than a larger haul that kills the carrier. Track why a run failed, then spend on that reason. This makes the campaign a sequence of learnable experiments instead of a race to copy a build from another patch.

Build a resilient campaign

Resilience means the ship can make another attempt after an unlucky room. Keep a spare operative, a repairable weapon, a route that does not require every optional fight, and enough basic material to prepare. Record the current version when evaluating advice. The Steam base game is a living product with official 1.0 and 1.0.1 changes, so progression pages must remain cautious about values and unlock order.

Open Ship Upgrades for the pre-purchase filter, then connect that plan to Factions and Equipment. The purpose of progression is not to own every system at once; it is to make the next sensible contract safer.