Factions turn Quasimorph missions into a strategic map rather than a list of disconnected rooms. Contracts can change reputation, expose equipment, affect the balance of power, and lead the story toward different organizations. The community vocabulary commonly describes Power and Technology as meaningful faction values, while the official 1.0 notes add RealWare and AnCom storylines. Treat these as connected systems, but verify the current panel before relying on a specific reward or route.
Power
Read what the current faction strength changes about missions, enemies, rewards, and the wider map.
Technology
Inspect how faction technology affects available equipment, trading choices, and preparation decisions.
Reputation
Choose contracts for a clear relationship goal and accept that helping one side can change another route.
Read the faction screen
Before accepting a mission, identify the issuing group, the likely opposition, the reward, and what the contract changes. A faction that can sell or unlock the equipment you need may be more useful than a faction with a larger immediate payout. A story job may have value beyond the visible resource, but it should still be prepared like a dangerous contract.
Power and Technology are not interchangeable. A faction can be influential without offering the exact equipment your crew needs, and equipment availability does not automatically mean the mission is safe. Use the values as context for a decision, not as a permanent tier list. If the current screen changes after an update, record the new interpretation with a date.
Build reputation with a purpose
Choose one short-term relationship goal: obtain a type of equipment, open a contract route, support a story line, or stabilize a region. Then select missions that move toward that goal while still returning enough resources to keep the ship running. Avoid switching targets every contract because a different reward appears. Reputation is useful when it creates a path, not when it becomes a score you chase without a plan.
When a mission is offered by one side of a conflict, inspect the consequences visible in the preparation or result screens. If the effect is unclear, make a smaller test first. Keep a separate reserve for a route that depends on the current faction state. A successful faction plan leaves the crew able to work for another group later; it does not require burning every bridge for one item.
Factions and equipment
Technology can influence what a group uses, sells, or makes available. This is why an equipment page should not promise that one weapon is universally best. Compare the contract’s enemy equipment and the faction’s available trade or reward with the crew’s actual stock. The goal is to turn a relationship into a reliable loadout without sacrificing the carrier’s survival.
If a station or Trade Shuttle shows accepted item types, use that current interface. The 1.0.1 notes say the trading screen now shows what the selected station accepts, which reduces dependence on old tables. Keep a backup weapon and treatment before converting inventory into reputation or currency.
Faction planning is also a way to manage uncertainty. If a group offers a contract whose opposing side, reward, or consequence is not explained, do not fill the gap with a confident community rumor. Bring only equipment you can replace, set a clear extraction condition, and record what the result actually changed. A small, documented test is more useful than a dramatic story mission that leaves the ship unable to launch. Once the current screen is understood, the same method can be applied to another organization without copying an old route.
Story factions and version boundaries
The official 1.0 notes name RealWare and AnCom storylines, each with two endings. That confirms their presence in the base game’s 1.0 scope, not a guaranteed order, reward, or optimal ending. Story content also carries spoiler and branch risk. Place route advice behind a current version label and distinguish released content from future plans or community speculation.
The same rule applies to factions found in community wikis. A page may use a useful name or relationship map while still being a stub or awaiting a 1.0 update. Treat it as a vocabulary aid and research signal. Do not turn a partial table into a confident list of all factions, rewards, or equipment.
The most useful faction note is actionable and reversible. It names the contract, the loadout, the expected relationship change, and the point at which the crew leaves. It also records what was unknown. That format lets a player compare two organizations without treating a community opinion as a promise. When a later patch rebalances a mission or improves the trading screen, the note can be updated at the decision that changed rather than rewritten as a vague “best faction” ranking.
Good contract
It advances the chosen relationship, gives a useful reward, and leaves enough treatment and equipment for the return.
Bad contract
It offers a visible reward but forces a route the crew cannot prepare, repair, or evacuate from.
Unclear contract
Take a low-cost reconnaissance approach or delay until the current faction panel explains the consequence.
A faction planning worksheet
Write the target faction, desired outcome, required equipment, acceptable opposing relationship change, and the exit condition. After the mission, record the actual change and whether the reward arrived as expected. This keeps the guide tied to decisions and makes stale facts visible. If the screen disagrees with an older note, the current game wins and the note should be marked for update.
Continue with Reputation and Contracts for a short planning routine. Use Equipment to translate faction access into a loadout, and Updates when a patch changes trade, story, or difficulty presentation.
Recommended articles
Choose the guide that matches what you want to do next.
All Factions articles
1 focused articles with steps, checks, and current caveats.