Co-op Teamwork Guide for NMRiH2

Regroup with a purpose

Responders can begin separated, so the first useful team action is to reduce uncertainty rather than collect unrelated loot. Read the active objective, identify the nearest practical regrouping direction, and move toward another player without turning every sound into an optional fight. The attached source supports the separated start and co-op structure; it does not guarantee that one path is safe on every map.

When players meet, exchange a short status: current objective, carried mission item, visible infection or treatment, and intended route. Regrouping is useful only when the new group shares a plan. Standing together while different players pursue different tasks simply concentrates confusion.

If another player remains separated, decide whether retracing the route would abandon the active task. This guide cannot observe the map state or prescribe a universal rescue path. Make the decision from the visible objective and the group's current resources, then say whether the squad is waiting, advancing, or changing extraction plans.

Use short voice calls

Proximity voice works best for concrete information: route left, infected, treatment here, mission item carried, reloading, regrouping, or leaving. A useful call names the fact and the next action. "Gene therapy here; infected player return" gives the nearby squad something checkable, while an unexplained shout does not establish ownership or direction.

Keep calls short during contact. Long explanations can hide the warning another player needs to hear, and proximity means a distant teammate may not receive the message at all. Repeat a critical extraction or objective call after regrouping instead of assuming it traveled across the map.

Voice is coordination, not evidence that the task completed. After an interaction, read the objective text again. After a handoff, confirm who now carries the item. After an extraction call, confirm who is alive, separated, infected, or still moving. Each confirmation closes a specific ambiguity without adding an unsupported game rule.

Assign objective ownership explicitly

At the start of each task, name who will attempt the interaction and who will keep the route open. Objective ownership does not require a permanent team leader or a fixed class. It is a temporary answer to a simple question: who is acting while everyone else protects, carries, or watches the mission state?

After the action, the acting player should state the result and the group should confirm that the visible objective changed. If it did not, recheck the current area and last interaction before scattering to search for an invented solution. The current map checklists support that bounded recovery sequence; they do not publish secret item locations or universal failure causes.

When ownership changes, say so. A downed, separated, or infected carrier can make the previous plan obsolete. Hand the mission responsibility to a reachable player and restate the route rather than allowing several players to assume someone else still owns the task.

Hand off resources by current need

Keep treatment and mission-critical items with a player who can remain accessible to the group. Announce the item before moving it, name the recipient, and confirm the handoff. Do not duplicate a support choice while another role has no way to address an immediate objective or visible infection problem.

For infection, identify who carries Pills and who carries Gene Therapy. The related health guide records Pills as a temporary delay and Gene Therapy as the one-use cure-and-immunity decision described by the current source. This teamwork page does not add spawn locations, treatment timers, or a rule that one role must always carry them.

For inventory pressure, ask whether a personal item can be moved before the next mission need. The source boundary does not provide a universal slot formula or best distribution. Use the actual inventories, keep mission needs visible, and make the transfer reversible when the objective state may change.

Decide extraction together

Before moving to early or final extraction, confirm who is alive, separated, infected, carrying Supplies, or responsible for a mission item. State which extraction type is available and whether the active objective permits the planned exit. A successful personal exit can still conflict with the shared plan if the group was relying on that player's route, treatment, or equipment.

Use one explicit call: "early extraction" when preservation has become the priority, or "final extraction" when the scenario is complete and the squad is moving to the exit. Ask each reachable player to confirm readiness. Proximity voice makes silence ambiguous, so do not interpret it as agreement from someone who may be out of range.

Choose a route the slowest living teammate can complete, then keep enough space to avoid blocking the group. If the exit does not resolve, recheck the objective text and player positions before declaring a bug. This guide offers a confirmation sequence, not a universal diagnosis.

Review the team decision after the run

After the result, name one coordination failure precisely: the squad never regrouped, a critical call did not reach the carrier, objective ownership was unclear, a resource handoff was not confirmed, or players followed different extraction plans. Practice that boundary in the next lower-consequence run instead of changing every role and route at once.

The official Armageddon co-op overview supports separated Responders, proximity voice, shared resources, objective movement, and extraction decisions. It does not establish an optimal squad composition, guaranteed safe formations, item drop rates, or current server behavior.

Use the extraction guide when the unresolved question is early versus final exit. Use the infection guide when treatment changes the group's time horizon, and the linked Medic Build only as a bounded role preset with its own captured-source limits. Relations provide context; they do not prove that one composition is required.