Patch 9.4.28 Corrected the District 3–11 Gravity Anomaly From 9.4.27 and Simultaneously Set District 12 to Zero Gravity — District 12 Was Not Mentioned in the Patch Notes and Had No Prior Gravity Issues

Patch 9.4.28, deployed this morning to resolve the variable-gravity anomaly introduced by 9.4.27 across Districts 3 through 11, has restored normal gravity to all affected districts while setting District 12 to 0% gravitational force — a state not present in any prior version of District 12. District 12 was not referenced in Patch 9.4.28's patch notes, was not part of the 9.4.27 anomaly, and had no open gravity-related bug reports. Approximately 47,000 residents of District 12 currently have no functional gravity. MetaCity has confirmed it is aware of the issue and is preparing Patch 9.4.29.

The specific nature of the District 12 situation distinguishes it from the 9.4.27 anomaly it apparently accompanied into the patch cycle. The 9.4.27 gravity bug produced variable results — Districts 3 through 11 experienced different gravity levels, ranging from near-weightlessness in some areas to oppressive high-gravity in others, depending on location within the district. The cause was a coefficient calculation error that affected the physics engine's interpretation of zone gravity parameters in those districts. District 12 under Patch 9.4.28 is not experiencing variable gravity. It is experiencing a clean, stable, consistent 0%. Whatever the patch did to District 12, it did it completely. The Central Commerce Hub, the transit stations, the Athletic Complex — all of them now operate under conditions that do not exist anywhere else on the MetaCity platform and have never existed in District 12's operational history.

The absence of a clear mechanism is what the engineering team's statement implies when it says it is 'investigating the cause.' Districts 3–11 and District 12 do not share physics subsystem code paths in any way that would make District 12 a natural casualty of a patch targeting the 9.4.27 anomaly. District 12 was not in the patch scope. Its gravity parameters were not referenced in the patch code. It had no open tickets. The fact that a patch targeting a specific set of districts caused a complete gravity failure in a completely different district that the patch wasn't touching suggests either that the physics engine's district isolation is less complete than the architecture documentation describes, or that the patch introduced something with platform-wide effects that only manifested visibly in District 12 due to some underlying condition that existed there and nowhere else. MetaCity's engineering team is now working to understand which of these is true before Patch 9.4.29 is deployed.

The Patch Fixed Districts 3 Through 11. It Also Broke District 12. District 12 Was Fine.

The Patch 9.4.29 preparation announcement — issued less than two hours after the 9.4.28 deployment — creates its own set of questions. The patch cycle that produced this situation is: 9.4.27 broke Districts 3–11, 9.4.28 fixed Districts 3–11 and broke District 12. The next step is 9.4.29. The pattern is a patch response loop where each remediation introduces a new problem whose scope is not yet visible. MetaCity has not stated whether the 9.4.29 deployment will be targeted exclusively at restoring District 12 gravity, or whether it will address the broader platform physics review that the 9.4.27–9.4.28 cycle arguably warrants. Residents of Districts 3 through 11 whose gravity was restored by 9.4.28 have reasonable interest in whether 9.4.29 will leave them in normal gravity. Residents of every other district have reasonable interest in whether 9.4.29 will affect them. MetaCity has not addressed these questions. Patch 9.4.29 is being prepared.