Patch 9.4.23 Introduced a Sleep Mode That Cannot Be Exited — 89,000 Avatars Have Been Locked in a Dormant State for 11 Hours and Cannot Log Back In to Their Own Accounts

Patch 9.4.23, deployed at midnight as part of a routine wellness update cycle, introduced an "Avatar Rest Mode" feature designed to allow users to put their avatars into a temporary low-power dormant state. The feature has a critical defect: avatars that entered Rest Mode during the patch window — either manually or through an auto-trigger that activated on accounts idle for more than 30 minutes — cannot be woken. The exit mechanism fails silently. Affected accounts receive no error message; the wake prompt simply does not respond. MetaCity estimates 89,000 accounts are currently locked in dormant state. Several of the affected users have scheduled events, active business operations, and time-sensitive transactions that have been suspended for 11 hours. A fix is not deployed.

Rest Mode was not announced before Patch 9.4.23 deployed. The feature appeared in the patch's release notes at midnight alongside a brief description — a wellness initiative designed to reduce avatar rendering load during extended idle periods, with an auto-trigger for accounts inactive for 30 minutes or more. The framing was positive: MetaCity described it as a quality-of-life feature that would reduce server strain and encourage healthier usage patterns. The auto-trigger, however, activated immediately upon patch deployment on any account that had been idle during the maintenance window. Tens of thousands of accounts that were simply not logged in at midnight — a normal state for a platform user at midnight — had their avatar placed into Rest Mode without any advance notice, any opt-in prompt, or any awareness that a new feature had been silently applied to their account. They woke up to find they could not log in.

The exit failure is the specific defect that has turned a minor inconvenience into a significant platform incident. Rest Mode's wake prompt — a simple confirmation screen that should return the account to active status — renders correctly on the client side. It appears functional. It simply does not do anything when interacted with. There is no error message that tells the user the wake attempt failed. There is no fallback mechanism. There is no support bypass. Affected users report submitting the wake prompt repeatedly, restarting their devices, reinstalling the client, and contacting support — all without result. MetaCity's support documentation did not include Rest Mode at the time the incident began, because the feature had been live for less than nine hours when the first mass reports came in. The 89,000 affected users spent the first several hours with no official confirmation that the problem was platform-side rather than user-side.

The Wake Button Works. It Just Doesn't Do Anything. 89,000 Accounts Are Still Waiting.

The economic dimension of the lockout has escalated the incident beyond a technical inconvenience. MetaCity's platform economy operates on real-time presence: marketplace listings have expiration timers, event hosting obligations have contractual start times, business leases require active account interactions to renew. Eleven hours of involuntary account lockout, with no warning and no compensation framework, has cascaded into material losses for affected users. At least one commercial lease in District 5 was automatically terminated after its renewal window passed while the account holder was locked in Rest Mode. Several creators with scheduled paid events could not fulfill their hosting obligations. Marketplace listings that would have sold at peak pricing have expired. MetaCity has confirmed a fix is coming 'later today.' The platform has not addressed whether users whose leases terminated, events failed, or listings expired during the lockout window will be compensated. The 89,000 affected accounts are still waiting.