Norse Field Manual
Field guides

Valheim Co-op Death Recovery Priority Worksheet

Norse Field Manual · 2026-10-25

A Valheim death is rarely a solo problem in co-op. One player is down, gear sits in a tombstone, the biome is still hostile, and three people talk at once about who should run back first. Without a short priority order, the group often sends the least prepared player, loses a second body on the same hill, and then argues while food timers expire. This worksheet is a group process for the minutes after a death or a small wipe: who recovers what first, how to label the tombstone run, and which risk rules the group agrees to before anyone leaves the bed.

Nothing here is an in-game verified combat guide, a claim about a specific Valheim build, or a promise that a tombstone always behaves a certain way on every platform. Iron Gate's official FAQ describes Valheim as singleplayer or co-op with servers capped at 10 players, and the support page is the place for product issues. This page only organizes how a small group decides recovery order so the next corpse run is deliberate. For neighboring co-op process sheets on this site, see the boss attempt debrief and the portal hub label convention.

Why recovery needs a written priority

Voice chat favors the loudest plan, not the safest one. After a death, the owner of the tombstone wants their gear back immediately, a second player wants to "just portal in," and a third is still cooking. A written priority answers four questions before anyone undocks from the base: whose body is the objective, who is the runner, who is the safety anchor, and what is the abort signal.

The worksheet is version-neutral on purpose. It does not list boss HP, weapon DPS, or food combinations. Those change with patches and with your world's modifiers. Process fields stay useful when the group only agrees on roles and risk limits. If a world modifier or difficulty preset changes death behavior for your save, record that modifier name in the header and treat combat details as UNKNOWN until someone confirms them in your build.

The minimum fields after every death

Fill each field or write UNKNOWN with the person who will resolve it before the run starts:

  • Death event ID — short label such as DEATH-26-14 so voice chat and a shared note point at the same event.
  • Who died — character name and player name if they differ.
  • Tombstone location pointer — biome, landmark, map pin text, or portal name nearest the body. If the pin text is missing, mark UNKNOWN and assign who will read the map aloud.
  • Gear criticality — what must come back first: main weapon, tool, armor set, inventory bulk, or "anything recoverable." Criticality is a group call, not a damage spreadsheet.
  • Runner — who moves to the tombstone first, preferably someone with spare gear and food already on them.
  • Anchor — who stays at a safe portal, ship, or base to reopen a door, restock, or take a second body if the runner falls.
  • Support limit — maximum number of living players who may enter the danger zone on this attempt.
  • Abort rule — the condition that ends the attempt (second death, nightfall, boss aggro, ship destroyed) without debate.
  • Recovery order — numbered list: for example (1) clear path, (2) open tombstone, (3) extract owner gear, (4) retreat to anchor.
  • Next spawn plan — where the dead player respawns and whether they wait naked at base or take a cheap backup kit.

The support-limit and abort-rule fields are the ones most often skipped. Without them, a "quick pickup" becomes a chain wipe because every helper walks in after the first scream.

A worked example with a synthetic group

In this example the owner does not run first. The owner is under-geared after death, and the group decided recovery success matters more than who touches the tombstone. Brick is the runner because spare gear is already equipped. Lark never leaves the hub on this attempt, which preserves a portal and a restock point if Brick dies. If Brick aborts under the written rule, Sam does not improvise a naked sprint; the event is closed and logged for a daylight retry.

If a second player dies during the same attempt, open a new death event ID instead of overwriting DEATH-26-14. Stacked bodies are easier to reason about when each has its own runner assignment and abort rule. The multiplayer bug-report observation worksheet is the place to park something that looks like a missing tombstone or a disconnect inventory problem rather than forcing it into a recovery priority sheet.

Priority rules the group can agree on once

Write a standing order the group reuses, then override it only in the death-event row:

  • Runner before owner when the owner lacks backup gear or food.
  • Tools before trophies when progression is blocked without a pickaxe, axe, or key item.
  • One body per attempt unless the support limit explicitly allows a two-person extract.
  • Daylight preference when the location pointer includes night-heavy biomes for your group's sense of risk.
  • Portal names stay untouched during the run unless the abort rule fires; renaming mid-rescue is how people portal into the wrong door. Use your hub label convention before the crisis, not during it.

These are process defaults, not moral laws. A hardcore world-modifier group may choose owner-first every time. The point is that the default is written before adrenaline rewrites it.

Risk rules and abort signals

Pick abort signals that are audible and unambiguous in your voice channel: a single word such as "abort," or a repeated ping on the map pin. Soft language like "maybe retreat" is how second deaths happen. The anchor repeats the abort, closes the attempt in the note, and restocks the runner only after everyone is accounted for.

Separate personal risk from group risk. A player may accept a dangerous self-rescue when alone; in co-op, their second death spends group time and sometimes a second set of gear. The support-limit field exists so volunteers do not silently turn a one-runner plan into a parade.

If the tombstone sits behind a boss altar, a sealed dungeon door, or a shipwreck route your group has not mapped, mark path status UNKNOWN and assign a scout step before the extract step. Skipping the scout step is the most common way a recovery becomes a new boss attempt without a debrief.

A one-page template to copy

Copy these lines into your shared note for each event:

  • Event / who / location pointer / map pin text
  • Critical gear list (three items max)
  • Runner / anchor / support limit
  • Abort rule (one sentence)
  • Recovery order (numbered)
  • Spawn plan for the dead player
  • Outcome: recovered / partial / aborted / second death (new event ID)
  • One change for next time (single sentence)

The last line feeds your next session. If the outcome was aborted because the path was unknown, the next change might be "scout in daylight with empty inventory." If the outcome was a second death because support limit was ignored, the next change is about discipline, not better weapons.

Assumptions and limits

All examples are hypothetical. Valheim patches, world modifiers, crossplay quirks, and server settings can change how deaths, tombstones, skills, and portals behave; this page does not claim hands-on testing of a specific build and does not replace Iron Gate's FAQ or support channels when something looks like a bug. Inventory risk on online servers is real; the FAQ reminds players that joining online play can put a character at risk. No DPS numbers, boss strategies, or exploit claims are made here. Check the stated assumptions before adopting the worksheet.

Sources and method

AI-assisted writing with automated source, calculation and editorial checks. No hands-on testing or professional certification is claimed. Check the stated assumptions before applying this guide.