Patch 3.9.2 Fixed the Floating Districts but Compressed Time Inside Them by a Factor of 6 — Residents Aged Two In-World Years in Four Hours, All Subscriptions Renewed Early, One Wedding Got Auto-Completed

The emergency hotfix for Patch 3.9.1's floating district gravity failure has resolved the structural instability but introduced a temporal compression fault that caused time to pass at 6x speed inside any district that was airborne during the original glitch. Residents who stayed logged in during the fix experienced 48 in-world hours across 8 real-world hours. Platform subscription services recalculated billing using compressed in-world time, triggering early renewals. A scheduled wedding ceremony, using the platform's automated ceremony package, detected the time threshold and executed automatically with no guests present. The couple had no idea they were married until they received a congratulatory banner.

Patch 3.9.1 shipped at 11 PM on Tuesday and immediately caused eleven districts in MetaCity's elevated infrastructure zone to detach from their gravity anchors and begin drifting. The visual was remarkable — residents described watching their neighborhoods slowly rise through the cloud layer — but structurally catastrophic, as floating districts cannot connect to the platform's transit grid, utility pipelines, or neighbor rendering systems. The engineering team pushed Patch 3.9.2 at 4:18 AM as an emergency correction. It fixed the gravity. It also did something the patch notes did not mention: in the process of restoring the physics simulation to correct calibration, the engine applied a catchup multiplier to the time layer inside each affected district, running in-world time at six times normal speed until the simulation reached synchronization with the rest of the platform.

Three hundred and forty thousand residents were logged in when the fix deployed. For the next eight hours of real time, they experienced 48 in-world hours. Social events that were scheduled days out occurred the same morning. Inventory items with timed expiry conditions ran out faster than expected. Service contracts on automated building systems triggered renewal windows early. The platform's subscription billing system — which tracks renewal dates using in-world time stamps — processed 214,000 early subscription renewals during the compression window, each billed at standard real-currency rates. MetaCelebrityNews has confirmed that the charges processed and cleared. The billing system does not have a time-anomaly exception pathway.

The Wedding Nobody Attended

@celeste_and_varro had scheduled their wedding for the following weekend. They had used the platform's Premium Ceremony Package, an automated service that monitors account status, scheduled event time, and venue availability and executes a full ceremony sequence — vows, exchange, announcement post, guest notification — when all conditions are met. The wedding was scheduled for March 28th at 7 PM in-world time. During the time compression window, the in-world clock reached March 28th at 7 PM at approximately 9:30 AM real time on March 26th. The ceremony package detected the condition, checked that both accounts were logged in, noted the venue was available, and ran the full sequence. The venue was empty except for both users' avatars. No guests were present. No one was watching. The ceremony completed in four minutes. Both accounts received wedding bands. The platform's announcement system posted to both profiles: "It's official."

@celeste_and_varro did not know they were married until they saw the post. @celeste posted a screenshot of it with the caption "what." @varro's reply, three minutes later, was "okay so." The post has 1.8 million likes. MetaCelebrityNews spoke with @celeste, who said she and @varro had been planning the wedding for two months and are now "deciding how to feel about having already had it." She noted that the ceremony photos generated by the automated package are "actually very good." @varro said he is "mostly fine with it" and that his main concern is that "our families are going to ask why they weren't there and I don't know how to explain a time compression patch to my parents."

The platform has acknowledged the billing error and stated that all 214,000 early subscription renewals will be reviewed for refund eligibility. The time compression issue has been flagged as a "simulation synchronization artifact" and attributed to an undocumented interaction between the gravity restoration process and the temporal calibration layer. The wedding has not been addressed in any official communication. When MetaCelebrityNews asked a platform spokesperson whether the auto-completed ceremony is legally binding under MetaCity's digital partnership registry, they said they would "need to check on that." They have not followed up.