EA Forums Thread Tracks Broken Sims 4 Mods After Patch 1.123

A console-first Sims 4 patch can still throw a wrench into a heavily modded PC game, and that is exactly why the new EA Forums broken-mods thread matters. The April 16, 2026 status post for patch 1.123 is already doing the job players need most after an update: it separates what is broken, what is now obsolete, and what creators have marked unsupported so you can act before a bad load order turns into a lost evening.

What patch 1.123 actually changed

EA’s official build numbers tell the story straight away: PC 1.123.66.1030, Mac 1.123.66.1230, and Console 2.31. The headline feature is The Sims 4 Marketplace coming to PlayStation and Xbox, but the patch notes also call out stability improvements and UI-related fixes on PC and Mac. That matters because UI trouble is one of the fastest ways a modded save can feel broken even when the underlying save file is still fine.

The console side of the update is larger than it looks from the outside. EA says PlayStation 4 and PlayStation 5 players get shared Marketplace storage of up to 16GB, while Xbox One, Xbox Series X|S, and Xbox Cloud players get up to 50GB. That is a big content shift for console users, but it also helps explain why the forum thread warns PC players not to assume this is a harmless, platform-only patch.

Why the EA Forums thread is the first stop

The new Broken and Updated Sims 4 Mods and CC thread exists for one simple reason: it tracks mods and CC that were broken, made obsolete, or declared unsupported after game update 1.123. It also keeps an eye on creator news and newly released bugfix mods, which is exactly what you want when the patch lands and everyone is trying to answer the same question at once: can I keep playing, or do I need to pull files right now?

The thread is useful because it is not just a giant dump of names. It tells players how to use it properly, including sorting by Oldest for compiled lists and by Newest for the freshest reports. That makes a difference when you are triaging a save fast. Oldest helps you find the broader, accumulated picture. Newest shows you what is still being reported after the initial wave of updates.

The forum’s Mod and CC Issues master post adds another layer of practical help. It points players to archived broken-and-updated lists, vanilla testing, and the 50-50 method for isolating trouble. If your game starts acting strangely after patch 1.123, that support stack is built to help you narrow the problem instead of guessing.

What to check first in a modded save

The first files worth checking are the ones that sit closest to the player experience: UI tools, custom tuning, and gameplay mods. EA’s own notes say patch 1.123 can still affect UI on PC even though the update is centered on console Marketplace content, so anything that touches menus, notifications, overlays, or interface behavior deserves immediate attention.

That is the kind of update where a save can look worse than it really is. Missing buttons, broken panels, or endless loading do not automatically mean the save is dead. More often, they mean one of your core mods is out of date, unsupported, or now conflicting with the patch’s own UI changes. The safest move is to remove or disable anything the thread marks as broken or obsolete before you keep testing.

Also watch for newly released bugfix mods. The thread explicitly tracks creator news, which matters because a quick fix can stabilize a save much faster than waiting for a full overhaul. In a modded game, a replacement file can be the difference between a working household and a weekend spent rebuilding your folder from scratch.

How to triage a broken save without making it worse

Start with the vanilla test. EA’s master post points players there for a reason: if the game behaves normally without mods and CC, you have already learned something important. The issue is almost certainly in the folder, not the save itself.

From there, use the 50-50 method. Cut your mods list in half, test the game, and keep narrowing until you find the file causing the problem. It is not glamorous, but it is the fastest way to identify the troublemaker when your game starts showing symptoms like missing UI, broken interactions, or a save that will not load cleanly.

A few practical habits make this process much less painful:

• Back up your saves before you test anything.

• Check the EA thread sorted by Newest for active reports, then by Oldest for compiled status.

• Pull anything the thread lists as broken, obsolete, or unsupported before you relaunch.

• Treat UI mods and custom tuning as high-priority checks after patch 1.123.

• If a creator has posted a bugfix, use that instead of forcing an outdated file to work.

That is the basic survival kit for any post-patch scramble. It keeps you from blaming the wrong file and helps you avoid the common trap of re-adding everything too quickly.

Why this patch still deserves attention

EA’s March 17, 2026 update set the pattern. That patch brought The Sims 4 Marketplace to PC and Mac, was described as a high-impact patch, and delivered more than 60 quality-of-life bug fixes and improvements, with console support following afterward. The fact that patch cycle already produced an old, archived broken-mods thread, plus March 18 and March 23 hotfix follow-ups, shows how quickly the community now has to move after each major change.

Patch 1.123 may look smaller because the main feature lands on console, but the forum response proves the real lesson of The Sims 4 mod scene: no update is too modest to skip the check. If you play with a built-out mod folder, the new EA thread is your fastest path to a stable save, a cleaner folder, and fewer surprise failures the next time you hit Load Game.