Once Human First-Session Priority Checklist: Progress, Explore, or Build?

Your first priority should follow your next verified goal—not a universal route through progression, exploration, and base work.

Define one session result

Turn broad new-player uncertainty into a bounded decision that can be checked during the current session.

• Name one result you want before the session ends.
• Record the time available, platform, scenario, and displayed version.
• Separate the required result from optional exploration, collecting, or construction.
• Describe the current blocker without guessing its cause.

Verify what the goal currently requires

Use current in-game information instead of assuming a fixed progression or unlock path.

• Read the objective, scenario screen, and relevant item, recipe, or facility descriptions.
• Write down each displayed condition and preserve its qualifiers.
• Mark the requirement as confirmed, unclear, or unrelated to the chosen goal.
• Do not infer an unlock route that the supplied evidence does not document.

Choose the matching priority lane

Select progression, exploration, or base work according to the verified blocker rather than a universal order.

• Choose progression when the current interface connects the goal to an active objective or prerequisite.
• Choose exploration when the goal depends on locating information, a route, or an input identified in the current game.
• Choose base work when a displayed facility or setup requirement directly supports the chosen result.
• Choose an information-gathering step when no lane has a confirmed connection to the blocker.

Run a low-commitment test

Check whether the selected lane helps before committing substantial time or resources.

• Preserve the current setup when practical.
• Take the smallest reversible action connected to the confirmed requirement.
• Check whether the original blocker disappears, changes, or remains.
• Stop and reassess when the result does not match the displayed requirement.

Apply the scenario and patch gate

Keep the decision current when scenario availability or progression context changes.

• Confirm the scenario and entry options shown in the current interface.
• Treat the announced October 21, 2026 (PT) Isles of Abyss launch as pending until maintenance is complete and the scenario is visible.
• Keep entry details separate from unsupported assumptions about carryover, persistence, recipes, or other transition behavior.
• Recheck official or in-game information after an update affects a dependency in the plan.

Move to a specialized decision only when needed

Keep this page focused as an umbrella priority selector while directing narrower problems to existing guides.

• Use the first-base checklist after base placement or expansion becomes the verified decision.
• Use the resource-priority plan after a specific input is confirmed as the blocker.
• Use the beginner build chooser when the next decision concerns weapon feel or playstyle direction.
• Use the upgrade-commitment check before spending resources that are difficult to replace.

Decision checklist

• Write down one result for the current session.
• Record the platform, scenario, displayed version, and available time.
• Identify the first observable blocker to that result.
• Check the current objective and relevant in-game descriptions for a stated requirement.
• Classify the next action as progression, exploration, base work, or information gathering.
• Choose a reversible action connected to the verified requirement.
• Recheck the blocker after completing that action.
• Delay larger commitments when the requirement or result remains unclear.

Worked example

A new player has a short session and wants access to something shown in the current interface, but does not know whether to follow an objective, explore, or add to the base. They record their scenario and displayed version, read the connected objective and description, and look for an explicit prerequisite. If the interface links the goal to an active objective, they test that route without expanding the base. If it instead identifies a location or input, they make a bounded exploration trip. If it identifies a facility requirement, they address only that requirement. When no connection is shown, they preserve their resources and gather more current information rather than guessing at a large commitment.

Common mistakes

• Trying to progress, explore, and expand the base at the same time without one session goal.
• Treating another player's preferred order as a universal progression path.
• Building or upgrading before confirming that the expense addresses the current blocker.
• Using an old scenario answer without checking the current version and interface.
• Assuming announced scenario entry details also establish carryover or persistence rules.

Related guides