Co-op survival tips: jobs, shared storage, revives, and base defense

What this guide solves

Co-op failures usually come from unclear decisions rather than a missing character build. Two players spend the same scarce materials, everyone enters a dangerous room at once, or nobody knows which Crafting Bench an Assault Event will target. This guide turns the game's verified systems into a simple team routine for each play session.

The assignments below are operating roles, not character classes. Abiotic Factor has Jobs, Traits, and individual Skills. The Wiki's version 1.3 menu screenshot labels the visual groups Fitness, Combat, and Survival, matching its current category headings. Crafting is an individual skill within Survival, not the name of a skill that levels the whole group. A player can perform any team task even if their starting Job gave another player an early advantage.

This page is verified for version 1.4. It avoids fixed route times, universal "best" job combinations, and claims that every player must sleep on a rotating watch. Those are group preferences, not rules established by the current game references.

Start with real Job advantages

Jobs affect starting Skills, XP bonuses, trait points, and sometimes starting items or forced Traits. They are useful for deciding who handles the first version of a task, but they do not lock that task to one player forever.

The final column is this site's planning suggestion, not an in-game Job description. Read the current Jobs page before character creation because exact bonuses can change between updates.

Assign one goal and four session roles

Choose the session goal before leaving the base. "Explore" is too broad. A good goal names a destination or outcome, such as unlocking one door, finding one recipe, completing one trade, or returning with one material category.

Then assign these temporary roles:

For a two-player group, combine route lead with rear guard and supply keeper with base operator. For a larger group, extra players can scout side rooms or carry cargo, but the four decisions should still have named owners.

Roles can change between runs. Reassign them when the objective changes rather than waiting for a player's Job or Skill level to match an imagined class.

Use a departure check instead of repeated discussion

Before the group moves, confirm five items:

1. Objective: Everyone can state the same destination and completion condition.
2. Return point: Each player has a valid bed or knows the relevant Portal World entrance and Check-In Terminal option.
3. Medical plan: The team knows who carries the Healing Briefcase and who has backup treatment items.
4. Inventory space: At least one player has room for the objective item; optional salvage does not fill every pack first.
5. Stop condition: The group returns when the objective is complete, essential supplies are depleted, or a required tool breaks.

This checklist is intentionally independent of exact equipment. It remains useful as the group advances through new sectors and replaces early gear.

For the terminal option, each player should check in before departure rather than merely know where a terminal is. Only one Check-In Terminal can be saved at a time, alongside the other respawn choices. A Portal World's Zone Entrance option applies while inside that world; the bed option requires a valid assigned bed.

Build shared storage around the Item Transporter

The Crafting Bench's Tier 1 Item Transporter upgrade can access items in storage containers within 16 meters. It also connects nearby Repair and Salvage Stations to stored repair materials. That verified range gives the group a clear reason to centralize active crafting stock instead of scattering every container across the base.

Use a small number of purpose-based zones:

• Crafting input: common materials used by recipes and repairs.
• Expedition supply: food, medical items, batteries, ammunition, and tools that players take before a route.
• Return sorting: one temporary container for unsorted items after a run.
• Hazard storage: shielded storage for radioactive items.
• Personal gear: equipment a player is actively maintaining for a chosen loadout.

Place crafting input within the verified Item Transporter range. Do not claim that every nearby container is connected until a recipe or repair interaction actually sees its contents. Floor level, placement, and the real range are better tested through the interface than guessed from room size.

Use the container quick actions deliberately. "Store all of the same type" moves matching items into a container that already holds that item. "Store all" attempts to move the player's inventory while respecting slot and stack limits. Check for leftovers before announcing that supplies have been banked.

Prevent duplicate spending

Shared storage helps only if the team controls high-cost decisions. Use this short protocol:

1. The player proposing an expensive craft names the item and its purpose.
2. The base operator checks whether the team already owns one.
3. The group confirms that required progression items will remain available.
4. One player crafts it and places any unused materials back in storage.
5. The item is assigned to the next route, not hidden in a personal container.

This is particularly important for bench upgrades because Crafting Skill gates the upgrade tiers. Crafting level 2 unlocks the first upgrade set, level 5 the second, and level 15 the final set. Concentrating early crafting activity on a player who already has the relevant Job bonuses can reach those gates more directly, but the game does not require permanent specialization.

Handle a critical wound without creating a second casualty

In multiplayer, a character whose health is depleted becomes critically wounded. Another player can revive them by holding the primary action button. The current Death reference gives a 60-second window before the wounded player dies. Single-player and multiplayer sessions with only one active player skip the critically wounded state.

Before relying on another revive, check the player's down-related status. Last Legs makes reaching 0 health cause death instead of another downed state; its listed recovery is sleep. Extra Down, granted by the First Aid Brink of Death perk, provides an additional down. The normal 60-second window does not guarantee that every later casualty can be revived.

Use this decision order:

1. Call the position. The wounded player identifies the room, doorway, or enemy controlling the body.
2. Stop advancing. Players who are still safe hold cover rather than entering the same damage source.
3. Control the immediate threat. Draw it away, interrupt it, or use the environment to create a revive window.
4. Send one reviver. One player performs the revive while another watches the approach.
5. Retreat after the revive. Recovery takes priority over resuming the original fight with low health.

If the route to the body cannot be controlled within the remaining window, do not sacrifice the full team. A death creates a corpse containing main-inventory items under the default penalty, and the player receives respawn choices based on available locations. The team can organize a deliberate corpse recovery instead of multiplying the number of corpses.

Use the Healing Briefcase accurately

The Healing Briefcase is a reusable, throwable device with a 200-capacity battery. When deployed, it heals players in its radius for 3 health every half second and spends charge only while it is actively healing. It does not heal enemies.

That supports two useful co-op patterns:

• Deploy it behind cover after a revive so several injured players can use the same recovery point.
• Throw it into a controlled melee area when players need healing but moving to a distant base station would break the formation.

Do not describe a crafted Charging Station as giving it "infinite uptime." The Briefcase requires charging between uses, and a crafted station needs power. Facility GATE Charging Stations work around the clock and charge one item at a time; locate one before committing to a recovery route. The verified advantage is that one device can heal multiple players in its radius, not that it runs forever.

Sleep according to fatigue, not a fictional watch rule

Sleep reduces fatigue when a player uses a bed. Waking before sleep completes can leave the player not fully rested and can cause Groggy. The specific Groggy entry lists waking with 30% fatigue status or lower as its trigger, so check the remaining meter rather than assuming every interrupted nap applies it. Bed quality affects sleep, and the Sleeping Minigame can speed recovery.

The game references do not establish a rule that co-op groups must always keep one player awake. Portal Storm behavior is more specific: if no portals are in the area when the event starts and all players sleep through the night, the event can be postponed until morning. Sleeping near an existing portal may be interrupted when enemies arrive.

Use this practical routine:

1. Read the current fatigue state before starting a long route.
2. If an Assault Event warning has appeared, inspect the base and decide whether to handle the event at night or postpone it under the documented conditions. Sleeping postpones a Portal Storm only if no portals are already in the area when it starts and every player sleeps through the night.
3. Let players finish sleep rather than forcing an early wake and Groggy.
4. Regroup only after each player confirms they are ready to depart.

Players do not need identical fatigue levels, so sleep can overlap or happen at different times. The useful coordination is announcing readiness, not enforcing a universal night-watch schedule.

Respond to Assault Event warnings

Assault Events target Crafting Bench areas. At 4 PM on the afternoon before an event, the game warns players with "The air feels strange. Be on your guard tonight." The start sequence later includes "The air feels different..." and a message associated with the event type.

When the warning appears:

1. Stop expensive crafting and return loose materials to storage.
2. Confirm which players are close to which powered Crafting Benches.
3. Repair the bench, nearby deployables, and the defenses already installed.
4. Move nonessential portable items out of exposed paths.
5. Choose positions that cover likely approaches without grouping everyone in one doorway.
6. Wait for the event-end message, then clear any remaining attackers before dismantling the response position. The message means all enemies have spawned, not that they are all dead.

The Assault Events reference notes that the selected bench is based on benches closest to players and that known spawn approaches matter for defense design. This means a split team should communicate location before the start message; otherwise different players may prepare different bases.

For general assaults, bench selection occurs when "The air feels different..." appears. Portal Storms have an earlier commitment point: once a portal has spawned at a bench, that storm stays tied to that bench. Check existing portals before moving the group to another base. If the team postpones a general assault by staying far from benches overnight, expect it to start when a player returns to a bench's radius; returning is a defense task, not an automatic all-clear.

Review one failure at a time

After a failed route, change one rule tied to an observed cause.

The aim is not rigid hierarchy. A reliable co-op group makes ownership visible, uses the real mechanics correctly, and can explain why a route succeeded or failed without inventing hidden classes or unsupported rules.

Session completion checklist

The session is complete when the objective item is stored, the return container is sorted, borrowed gear is returned, the Crafting Bench remains powered, and the next group can understand what changed. Record the next unresolved task in plain language. That small handoff prevents the following session from spending its first minutes reconstructing decisions that the previous group already made.