Valheim Co-op Sailing Embark Leave Threshold Worksheet

Why sailing embark needs a named owner

A ship is a shared vehicle with personal consequences. The player who "just unties" is not only moving a hull; they set the pace for everyone still on the pier, everyone already aboard, and everyone waiting at a return dock that may not exist as a shared label. Groups that rely on vibes usually discover the gap at the worst moment: mid-fjord with night falling, or at a beach with a half-loaded vessel and no agreed destination name.

An embark leave-threshold handoff is not a spreadsheet of every nail and plank. It is a role assignment for one voyage event: who decides when the ship may leave, who steers, who owns lookout and repair calls, who confirms cargo is aboard rather than "about to be," and who is allowed to call abort when the crew count or route is unsafe. Without that, the loudest player becomes captain, and quiet players with full inventories get left on the pier or blamed for a tip they did not cause.

Write the assignment once per voyage event, not once per forever. A Meadows-to-Black-Forest coast hop is not the same job as a Mountains silver barge to a distant hub. Reusing yesterday's "I always steer" is fine only if that person is present and accepting the role for this event ID.

The minimum fields before the ship leaves the dock

Fill each field or mark it UNKNOWN with the name of the person who will resolve it before embark:

• Event ID and goal — short label: ore barge Beach-A to Hub-Swamp-S, boss-prep sail to Island-East, recovery skim to Grave-Pin-3. One destination plan per sheet.
• Embark lead — the single person who owns go/no-go on leave readiness and cast-off timing. Not necessarily the best sailor; the clearest route and crew caller.
• Helm / steer owner — who controls the rudder and sail trim calls, and who may hand the helm mid-voyage with a spoken transfer.
• Lookout / clear owner — who watches for creatures, collisions, and night risk while the helm focuses on the line.
• Cargo / dock owner — who confirms what is aboard, what stays on the pier, and which return dock name is written on the sheet. Prefer shared labels over "the usual beach."
• Repair / spare owner — who carries the repair responsibility (hammer and wood/resin plan as your group already uses them) and calls when a stop is required. Mark counts UNKNOWN if you are not inventorying.
• Crew list — who is expected aboard at cast-off, who is optional, and who is explicitly staying ashore. A missing name is not a surprise mid-fjord.
• Leave threshold — one sentence the group agrees on. Example: "Leave when named crew are aboard, cargo for this trip is confirmed on the deck or in the named hold chest, and the return dock label is written—even if the mine still has loose ore on the pier."
• Route and staging names — departure pier, waypoints, and return dock or portal hub names that match your portal convention. Prefer written labels over gestures at the map.
• Go time and abort window — when embark starts, and until which landmark the group will still abort for a missing lookout, broken leave threshold, or storm/night call the group treats as a stop.
• Callouts — exact short phrases: "crew check," "cargo check," "dock hold," "embark go," "embark abort," "helm transfer," "dock confirmed."
• Post-event note owner — who writes one line if cargo was left behind, the wrong dock was used, or someone was left swimming without a recovery plan.

The leave threshold is the field that prevents the usual fight. If the group cannot state in one sentence when the ship is allowed to leave, the model of "vibes" will invent one under pressure—usually "we're already moving." Write the threshold before anyone boards for cast-off.

A worked example with a synthetic group

Three gaps still matter even in a "simple" barge: repair counts are unknown, loose ore remains on Beach-A by design of the leave threshold, and nobody should invent a ship capacity to argue for one more trip. The safe embark at this stage (1) names the event and destination, (2) confirms crew and cargo with spoken checks, (3) keeps the leave threshold as written, and (4) preserves abort until the first landmark. That plan makes no claim about wind, serpent behavior, or how much iron "fits."

Once the embark lead keeps the threshold and the cargo owner confirms the pier state, the sheet stays stable for cast-off. If someone dies mid-voyage or the hull is abandoned, stop treating this sheet as a sail plan and open the death recovery priority worksheet before the next embark.

Handoff sequence the group can run in under three minutes

Use this order at the pier. Do not reorder under pressure; the point is a shared checklist, not a race.

1. Event readback — Embark lead reads event ID, destination label, and leave threshold once. Anyone who disagrees speaks now.
2. Role confirm — Helm, lookout, cargo/dock, and repair owners say their names. Missing role = abort or rewrite, not "figure it out on the water."
3. Crew check — Call each expected name. Optional crew who are late are either marked ashore or the abort window is extended in writing.
4. Cargo check — Cargo owner states what is aboard and what is intentionally left. No invented stack counts required; qualitative lists are enough.
5. Dock names — Departure and return labels are spoken and match the sheet. If the return dock is UNKNOWN, do not cast off.
6. Embark go or abort — Embark lead says "embark go" or "embark abort." Only the embark lead closes the decision; helm does not cast off on private initiative.
7. Mid-voyage transfers — Helm changes only on "helm transfer" with a named receiver. Lookout calls that change the route go through the embark lead.
8. Dock confirmed — On arrival, cargo/dock owner says "dock confirmed" against the written label before anyone dumps cargo into a random chest.

If any step fails, the group either aborts or rewrites the sheet. Rewriting mid-boarding is allowed; pretending the old sheet still applies while people are already sailing is not.

Rules that prevent the usual failures

One leave threshold per event. If the group wants "one more load," that is a new event ID or an explicit rewrite before cast-off—not a shouted exception after the sail is up.

UNKNOWN is a stop, not a vibe. An unknown return dock, unknown crew list, or unknown embark lead means the ship stays tied. Filling gaps from memory after someone is already swimming is how reports become useless.

Qualitative cargo beats invented capacity. Say "iron-family ore for this trip plus support wood" rather than inventing how many stacks a hull "should" hold. Product numbers belong to Iron Gate's channels and your own observation sheets, not this process page.

Abort is a success condition. Calling "embark abort" when the lookout is missing or the leave threshold is broken is the sheet working. Shame around abort is how groups train themselves to leave people behind.

Separate observation from blame. If cargo was left on the pier, the post-event note records what was left and which field was incomplete. It does not need a villain. For reproducible product problems (disconnect mid-sail, join failures), use the multiplayer observation worksheets rather than rewriting this embark sheet into a bug report.

Do not change world modifiers or saves to "make embark easier" mid-event without recording that as a new case. The world modifier change log worksheet exists for intentional setting changes; embark night is not the time for silent edits.

How this sheet connects to portals, hauls, and recovery

Sailing often sits between a land haul and a hub unload. If the pier is the end of a cart run, complete or explicitly hand off the ore cart haul sheet before this embark sheet claims the cargo is "aboard." If the return plan depends on a portal rather than a reverse sail, write the portal hub label using the portal hub label convention so "dock confirmed" and "portal home" are not two different beaches with the same nickname.

Boss-prep sails should not inherit embark roles from a mining barge by default. Reassign roles for the event, and if the voyage is really a fight staging move, keep a separate debrief habit with the boss attempt debrief worksheet after the attempt—not during cast-off.

When someone dies on the water or on a landing beach, stop the next embark until recovery priority is named. The death recovery sheet exists so the group does not invent a second sail plan while graves and cargo are still unresolved.

For voyage technique and ocean risk framing beyond process roles, keep the sailing and ocean guide nearby. That guide is orientation; this worksheet is the three-minute pier checklist.

A one-page template to copy

Keep the filled sheet with the group's session notes. A one-line post-event note is enough when the voyage was clean; when it was not, the note should say which field was incomplete rather than which player was "bad at sailing."

Assumptions and limits

No game build was installed or tested for this article, and the source-check date is 2026-11-04. The installed build, ship type, wind, creature behavior, and any capacity figures are reader-supplied fields—or left UNKNOWN. This page invents none of them. It is a co-op process worksheet, not an in-game verified fix, not a claim about crossplay or dedicated-server behavior, and not a substitute for Iron Gate's bug and feedback channels. If a later official source contradicts a process habit here, the official source wins for product facts; your group's role names can stay as house rules.

Sources and method

• Iron Gate: Valheim FAQ — retrieved 2026-11-04
• Iron Gate: Valheim support — retrieved 2026-11-04

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.