Once Human 3.1.1 October 23 Issue Status and Symptom Check

A symptom listed in the October 23 notice still needs its original status, context, and timing attached. Match those details before attempting a disruptive fix.

Read the October 23 status labels before troubleshooting

Keep the notice's three different status categories from being treated as equivalent.

• Treat the first group as issues the October 23 notice listed as fixed, while recognizing that a dated listing does not establish the cause of every later occurrence.
• Treat the second group as expected to be fixed by 08:30 PT; the notice explicitly says actual completion time may vary.
• Treat the Calamity Owl stronghold problem as still being addressed as of the notice.
• Treat the crocodile-pattern transfer problem as assigned to the November 5 version update, not as already corrected in the October 23 record.

Match symptoms in the listed-as-fixed group

Preserve each documented context before deciding that a current symptom is the same issue.

• Custom servers: duplicate character-name warnings could fail to appear and prevent server entry.
• Walkman: songs could play without sound.
• Moving ships: characters could experience lag or position rollback while the ship was in motion.
• Custom Server [Isles of Abyss: RaidZone]: memetics could be missing.
• Mobile in certain Isles of Abyss areas: trees could not be chopped.
• Custom Server [Isles of Abyss]: the "Head to a New Area" task could not be completed.
• Mr.Wishmonmon: the health bar could display incorrectly.

Check the expected-fix group without assuming completion

Identify symptoms covered by the variable-completion portion of the notice.

• Precision Load and Turret Enhancement mods could fail to take effect at certain levels.
• Environmental water resources could display inaccurately in certain areas of western Isles of Abyss.
• The Standing Action animation SFX for the Underworld Echo Set could fail to take effect, and the female mask could be missing its eye VFX.
• Halloween Wonder Night event task progress could fail to persist across seasons; the notice separately announced mail compensation for lost Blind Box attempts caused by that progress loss within 2 business days.
• A ship could occasionally become stuck while sailing and send players to the wrong location.
• Players could sometimes be unable to place items in their territory.
• A ship design layout could fail to place when "Building Filter" and "Ignore Facilities" were selected.
• The Team system unlock requirement in Isles of Abyss was adjusted from Tech Level 2 to Tech Level 1.

Separate the two unresolved warnings

Prevent a work-in-progress issue and a future-version correction from being described as completed.

• The Calamity Owl could clip underground while moving in strongholds, preventing normal attacks; the notice said the issue was being addressed.
• Crocodile patterns could be lost when transferring out of Eternaland; the notice said the cause had been identified and the fix required model changes planned for the November 5 version update.
• Preserve important state and avoid using either entry as a complete rule for other creatures, patterns, transfers, or scenarios.

Verify a live symptom with a small retest

Produce useful evidence without making an expensive or irreversible change first.

• Record the platform, displayed game version, server type, scenario, location, and relevant option or level.
• Describe the action immediately before the symptom and the result shown on screen.
• Compare every qualifier with the dated notice instead of matching on a shared keyword.
• Repeat only the smallest safe action needed to see whether the symptom persists.
• Keep screenshots or a short recording when the issue affects placement, movement, task progress, transfer state, visuals, or an interface message.

Report a persistent or unmatched issue

Give support a bounded observation while avoiding an unsupported root-cause claim.

• State whether the symptom fully matches, partly matches, or falls outside the October 23 list.
• On PC, use ESC, Support & Feedback, then Submit Suggestion.
• On mobile, open the map's left-side menu, select the headphones icon at the bottom right, then Suggestions and Submit Suggestion.
• Include the current version, platform, context, trigger sequence, observed result, and evidence captured during the smallest safe retest.
• Recheck a newer official notice before treating the October 23 classification as current.

Decision checklist

• Record the platform and displayed game version.
• Write down the server type, scenario, location, and relevant option or level.
• Classify the matching notice entry as listed fixed, expected by 08:30 PT with variable completion, still being addressed, or assigned to the November 5 version update.
• Confirm that every qualifier matches rather than relying on a similar symptom name.
• Run one small, reversible retest and capture the observed result.
• Submit a bounded report if the symptom persists or does not fully match the notice.

Worked example

A player cannot place a saved ship design after 3.1.1. Before rebuilding the ship, they record the displayed version, server context, and placement result. They note that the layout was applied with "Building Filter" and "Ignore Facilities" selected, which matches an entry in the group expected to be fixed by 08:30 PT with variable completion time. They preserve the original design, test one low-cost placement attempt with the same documented condition, and capture the error or failed result. If it persists, they report that exact sequence. The match shows that the behavior was documented; it does not establish that every ship-placement failure has the same cause.

Common mistakes

• Treating an expected completion time as proof that the change reached every player.
• Dropping a platform, Custom Server, Isles of Abyss, RaidZone, stronghold, level, or filter-option qualifier.
• Assuming any ship or territory placement failure has the documented cause.
• Describing the Calamity Owl or crocodile-pattern issue as resolved in the October 23 notice.
• Reinstalling, rebuilding, or transferring important state before recording a reproducible symptom.

Related guides