The Once Human development team has released the 6th Meta Hotline, breaking down community requests via the Once Human Feedback Platform following the v2.3.7 update. The newly live Feedback Hot Charts display player likes and dislikes in real time, serving as a primary reference for upcoming development priorities across multiple platforms.

Quick Facts

  • Platform: Multiple platforms (via Steam and official client)
  • Event: 6th Meta Hotline (standings as of July 22)
  • Key Feature: Feedback Hot Charts display community likes and dislikes in real time
  • Source: Once Human Steam news update v2.3.7

High Risk Events and Storage Updates

Several top-voted suggestions from the community have already rolled out or received confirmed adoption with accelerated development priorities. For High Risk Events, the game now supports cooldown checking directly within the Map interface. Players can click the Eye icon next to an event with the left mouse button to view reward cooldowns, and will receive a pop-up warning before teleporting if an event is currently on cooldown.

Meanwhile, the team has adopted suggestions to enrich Collection Loot Crate rewards, add a filter and sorting function to Weapon Calibration blueprints to save storage space, and make Renaming Cards shareable across an account. Because these latter three adjustments involve item and account-logic changes, their exact release dates will follow in subsequent announcements.

Livestock Automation and Depot Management

Looking further ahead, the project team addressed long-term farming and inventory management. An auto-harvest byproduct function for livestock—designed to introduce a Deviation similar to the Growshroom for automated collection—is officially planned to launch next year. Additionally, the team has adopted suggestions for bulk transfer and cleanup functionality in depots and transit storage to cut down on manual, item-by-item sorting costs.

However, bulk depot operations are still undergoing evaluation. Because transit storage handles massive amounts of item data, developers must build in misoperation protection, quantity confirmation, and robust data synchronization to prevent lag or accidental item transfers before setting a release schedule.