Modding support: no version rollback, no API change notes, no test branch

I have been playing The Sims 4 with mods for years, and I use the game as a visual storytelling tool. Since the June 2026 patch (1.125) my setup has been unusable, and I want to raise three issues that are design decisions on EA's side, not user error.

1. No version rollback. The EA app offers no way to install or stay on a previous game version. When a patch breaks compatibility, players have no fallback at all. Steam users of other titles can select an earlier branch; Sims 4 players cannot. This single missing feature turns every patch into a forced gamble.

2. No advance notice of API or tuning changes. Mod creators discover breaking changes on patch day, at the same time as players. A published change log for tuning and script API changes, even a short one, would let creators prepare updates before release instead of after.

3. No public test branch. Other live-service games run an opt-in test build precisely so that the ecosystem can adapt. The Sims 4 has an unusually large modding community that is a major reason the game is still played a decade in, and it gets no lead time whatsoever.

Two smaller points: the "Script Mods Allowed" setting silently resets to off after updates, and script mods still load only one subfolder deep, which is barely documented anywhere official.

None of this asks EA to support third-party mods. It asks for the basic transparency and rollback options that would let players manage the consequences of patches themselves.

Thank you for passing this to the team.