Once Human Scenario Transfer Priority Worksheet: What to Verify Before Moving

A scenario transfer is both a rules check and a priority decision: confirm what the current transition permits before deciding what matters most.

Define the exact transition and first objective

Prevent a broad carryover question from producing an unfocused transfer plan.

• Record the source scenario or server and the intended destination.
• Name one concrete result you want to achieve first after the transition.
• List the character, group, equipment, resource, and unlock dependencies for that result.
• Separate immediate needs from choices that may become useful later.

Build a verification worksheet

Turn assumptions into rule checks without claiming unsupported transfer mechanics.

• Give every candidate its own row instead of grouping all progress together.
• Record where the current rule was found: an official notice or current in-game transition information.
• Mark each row confirmed, excluded, or unclear.
• Preserve every platform, scenario, server, character, and timing qualifier attached to the rule.

Rank only confirmed choices

Prioritize by the destination plan rather than by perceived rarity or old advice.

• Score each confirmed candidate by how directly it supports the first objective.
• Prefer a candidate that removes a verified early dependency over one with no defined near-term use.
• Consider group access and character compatibility before ranking inventory-related choices.
• Do not assign value to a benefit whose eligibility or destination effect remains unclear.

Use an uncertainty gate before committing

Protect the player from decisions based on missing transfer evidence.

• Pause when an unclear rule affects a required part of the destination plan.
• Save screenshots or notes showing important current state and the wording used for the decision.
• Recheck current authoritative or in-game information after an update or when the destination changes.
• Proceed only with the portion of the plan supported by confirmed rules.

Separate this worksheet from existing guides

Resolve overlap with the current carryover, scenario-choice, and update-migration pages.

• Use the carryover guide to classify account, character, server, and scenario dependencies.
• Use the scenario-choice guide to decide whether the destination fits schedule, group, and progression goals.
• Use the update-migration guide to identify systems that need retesting after a version change.
• Use this worksheet specifically to rank verified transfer candidates against one named destination objective.

Decision checklist

• Write down the exact source and destination.
• Choose one first objective for the destination.
• List each dependency in a separate worksheet row.
• Verify every relevant rule through current official or in-game information.
• Mark each row confirmed, excluded, or unclear.
• Rank only confirmed choices by direct usefulness to the first objective.
• Record important current state before committing.
• Pause when a required dependency remains unclear.

Worked example

A player wants their first destination objective to be joining friends and resuming a familiar progression routine. They list group access, character compatibility, equipment, materials, and unlocks as separate dependencies. Current authoritative or in-game information confirms one dependency, excludes another, and leaves two unclear. The player ranks the confirmed dependency first, removes the excluded entry, and pauses any step that relies on the unclear entries. If later information resolves those entries, the worksheet can be updated without rebuilding the entire plan from assumptions.

Common mistakes

• Treating all progress as one transferable category.
• Using a previous season answer as proof for the current transition.
• Ranking candidates before confirming their eligibility.
• Choosing by perceived rarity without a destination objective.
• Ignoring character, server, or group dependencies.
• Proceeding when an unclear rule affects a required step.

Related guides