What "no official support" means

EA has not provided a mod SDK, map editor, documented data format, Steam Workshop integration, or compatibility promise. A game update can therefore change files or behavior without preserving an unofficial modification. EA support may also ask a player to reproduce a problem on an unmodified installation.

Unofficial projects can still appear because PC users can inspect and replace local files. Their existence does not turn them into supported features. A download page, loader, or community patch remains the responsibility of its author and user.

Protect a campaign save before testing a mod

Finish any active mission, close the game, and copy the save folder before changing files. Keep a separate backup that the mod manager cannot overwrite. Record the mod version and the game build so you can reverse the exact change later.

Scan downloads, avoid installers that request unrelated permissions, and do not reuse account credentials in third-party tools. Remove the modification and verify the game files before reporting a crash or corrupted save to EA.

What to check after an update

Do not assume that a mod which launches is fully compatible. Load a disposable save first, check combat abilities and mission transitions, then confirm that an unmodified save still opens. Mods that alter campaign pacing, Operator data, or mission scripting carry more save risk than cosmetic replacements.

The performance guide covers supported troubleshooting. For the launch reviewers' comments about replayability and the absence of an official mod ecosystem, see the review roundup.