Once Human Season Change Checklist: Learned vs Unused Items

An item you learned and an item still visible in inventory are not the same evidence. Check each state separately before making a transition decision.

Start with the evidence boundary

Prevent the announced Isles of Abyss schedule from being mistaken for a retention policy.

• The publisher announced Isles of Abyss for after maintenance on October 21, 2026 (PT).
• The announcement provides scenario-entry context but does not document retention for the asset categories in this guide.
• Use the schedule as a prompt to prepare, not as proof that a particular asset will remain or reset.
• Treat community discussion as evidence of player uncertainty rather than authority for a game rule.

Record the exact transition

Attach every rule check to the move the player actually intends to make.

• Write down the current scenario or server and the intended destination.
• Record the platform and the transition screen or notice being consulted.
• Note whether the decision occurs before or after the announced October 21 maintenance.
• Begin a new check if the destination, timing, or displayed wording changes.

Separate asset type from asset state

Avoid grouping learned access and inventory objects under one broad carryover label.

• Give each blueprint, recipe, cosmetic, unlock, and seasonal-progress dependency its own row.
• For every row, record whether it is learned, unused in inventory, equipped, claimed, or represented only by progress.
• Copy the relevant current wording without extending it to another state or asset category.
• Use confirmed, excluded, or unclear as the row status.

Apply a source-and-scope test

Decide whether a statement actually covers the player’s asset and transition.

• Prefer current publisher-controlled or in-game transition information for retention decisions.
• Match the wording to the same source, destination, platform, asset type, and asset state.
• Keep every condition or exception attached to the rule it qualifies.
• Leave the row unclear when the wording requires an inference.

Use an uncertainty gate before acting

Protect important state when the available rule does not answer the exact question.

• Capture screenshots of important inventory, learned entries, cosmetics, progress, and transition wording.
• Avoid consuming an unused recipe solely to test an unsupported retention assumption.
• Do not discard or reorganize important items merely to simplify the move.
• Proceed only with decisions whose required rules are confirmed; pause the dependent decisions.

Keep this checklist distinct from broader transition guides

Resolve overlap with existing RaidBench pages while giving this page a narrow job.

• Use this page for the learned-versus-unused state audit.
• Use the character carryover guide to classify account, character, server, and scenario dependencies.
• Use the scenario-choice checklist to compare schedule, group access, and play goals.
• Use the transfer-priority worksheet only after eligibility is confirmed and choices are ready to rank.

Decision checklist

• Name the current scenario or server.
• Name the intended destination.
• Record the platform and planned transition time.
• List each important asset or unlock on its own row.
• Label each row as learned, unused in inventory, equipped, claimed, or progress-based.
• Record the current official or in-game wording used for each decision.
• Mark every row confirmed, excluded, or unclear.
• Preserve screenshots and pause any decision that depends on an unclear row.

Worked example

A player lists four separate rows: a learned furniture formula, an unused recipe object visible in inventory, a cosmetic, and a seasonal unlock. The current transition wording is checked against each row without assuming that one category covers another. If the wording explicitly covers the learned state but says nothing about unused inventory objects, the first row can be marked confirmed while the second remains unclear. The cosmetic and seasonal unlock also remain separate until their exact categories and states are covered. The player saves screenshots and delays only the actions that depend on unresolved rows.

Common mistakes

• Treating every kind of progress as one carryover category.
• Assuming that a rule for learned access also covers an unused inventory object.
• Applying an answer from another season, scenario, server, or platform without checking its scope.
• Using the announced Isles of Abyss schedule as evidence for an undocumented retention rule.
• Taking an irreversible action while a required row is still unclear.

Related guides