Once Human Patch Notes: Support Channels, Bug Fixes, and What Players Need to Know
Once Human's latest update explains bug report and customer support steps while fixing combat, building, custom server, and PvE issues.
When Once Human players hit a bug in the middle of a base build, a boss run, or a cross-server team-up, the last thing they want is a scavenger hunt for the report button. That is why I paid close attention to the latest Once Human community update: it lays out exactly how to contact support and confirms a broad set of fixes across combat, building, custom servers, and PvE content. In 2026, with the game’s live-service cadence still pushing frequent updates, clear reporting channels matter as much as the patches themselves.
📣 How I Would Report a Bug Right Now
If I ran into an issue today, I would use the in-game tools first because they attach the right context for the development team. The process is slightly different on PC and mobile, so here is the short version I would share with any squadmate:
-
PC: Open the in-game ESC menu → Feedback & Customer Support → Select Bug Report to submit the issue.
-
Mobile: Tap the menu button in the upper right corner → Tap the headphone icon in the sidebar → Select Customer Support → Then choose Bug Report to submit feedback.
-
Offline: If the game or menu is unavailable, players can still report issues through the official email: [email protected]. The team says it will investigate as soon as messages arrive.
Why does this matter? Because a survival sandbox with base building, cross-server teams, custom servers, and seasonal events generates a huge number of edge cases. A vague report can slow down a fix; a clean report with the right menu path and context can help the team reproduce the problem faster. I appreciate that the update does not just list fixes, but also reminds players how to participate in the process.
🛠️ The Fix List: What Changed?
The development team says it has been gathering community feedback and actively addressing concerns. I grouped the main fixes by area so players can quickly see what affects their playstyle.
| 🎯 Area | ✅ Fix |
|---|---|
| Combat and weapons | Fixed an issue where switching weapons could occasionally trigger the incorrect No Other Weapon Equipped prompt. |
| Building and collision | Fixed collision detection errors for 1/2 Foundations, 1/4 Foundations, Fences, and Gates. |
| Custom servers | Fixed an issue where invitation codes could not be entered on the custom server invitation input screen. |
| Personalization | Fixed the incorrect limit for personalized badge displays. The current cap is now 70 badges to ensure a smooth display experience, with further optimizations planned. |
| Securement units | Fixed an issue where players could not use Claim All under certain conditions. |
| Facility interaction | Fixed a rare issue where interaction options would not disappear after using certain facilities. |
| Cross-server teams | Fixed a potential issue where cross-server teams could incorrectly enter dungeons in custom servers. |
| Character display | Fixed a rare issue where existing characters may not display properly in custom servers. |
| Gathering | Fixed an occasional issue with gathering in the wilderness. |
There are also three more targeted fixes that stand out for players chasing seasonal content and high-end PvE:
-
Fixed an issue in Lunar Revelry visional servers where players could not glide or swim after completing the Lord of Moonlight transformation trial.
-
Fixed missing Mystical Crates in PvE scenarios such as Fiskur Harbor and Avalanche Monolith strongholds.
-
Fixed an issue preventing multiplayer teams from entering the boss stage in Securement Silos (Nightmare) - ALPHA.
🔍 What Stands Out to Me
The custom-server cluster is the most interesting part of this update. Three separate fixes touch invitation codes, cross-server dungeon entry, and character display in custom servers. Anyone who has planned a community night on a custom server knows how fragile that experience can feel when one invite fails or one character does not load properly. I see these fixes as a signal that the team is paying attention to the social infrastructure around Once Human, not just headline combat changes.
Base builders should also cheer the collision fixes. Foundations, fences, and gates are the bones of so many creative builds, and small collision errors can turn a clean design into a frustrating mess. Is it glamorous? No. Is it important? Absolutely. The same goes for the Claim All fix in securement units and the interaction-option fix after using facilities. These are the quality-of-life details that shape daily play.
The badge cap change is another practical compromise. A limit of 70 badges may sound arbitrary, but display systems need guardrails to stay smooth. The team notes that further optimizations are planned, so I would treat this as a temporary tuning point rather than a final answer.
For endgame players, the Securement Silos (Nightmare) - ALPHA boss-stage fix and the missing Mystical Crates in Fiskur Harbor and Avalanche Monolith strongholds are the most valuable lines. Co-op progression bugs can waste an entire session, and missing crates can make a rewarding PvE route feel inconsistent.
🧭 What Should Players Do Next?
I would update the game, retest the issues that affected my squad, and submit fresh reports if anything still feels off. The email fallback is useful, but the in-game Bug Report path remains the cleanest option when the menus are working. The development team has clearly been listening; now the community’s job is to keep the feedback specific, reproducible, and constructive. I will be watching whether these fixes hold up in live play, especially around custom servers and cross-server teams, because those systems are where small bugs can become very big headaches.