Mods: official support and compatibility risks

Safe evaluation order

• Read the mod’s exact supported game version
• Check recent user reports
• Back up saves and configuration
• Install one mod at a time
• Remove outdated loaders before troubleshooting

What changed enough to break mods

Version 1.0 added a new hub, missions, items, achievements, rank-five trees, synergies, maps, and UI changes. Mods that patch progression, inventory, or interface code are the most likely to need a new build.

High-risk compatibility areas

Progression, inventory, UI, save handling, and skill-tree patches touch systems that changed heavily in 1.0. Visual-only changes may be narrower, but every third-party package still needs a current compatibility report.

Build a reversible test

Record the clean game version, back up saves and configuration, and add only one mod or loader before launching. Test on a disposable run before opening an important save. If the game fails, remove the last addition first instead of stacking more fixes on an unknown base state.

Compatibility evidence to look for

• An exact supported game version
• A recent release date after version 1.0
• A clear list of modified systems and required loaders
• Current user reports that describe the same platform
• Removal instructions that restore original files

When to wait for an update

Do not load a progression, inventory, skill-tree, or interface mod after a game patch until its author confirms compatibility. Missing items, blank skill nodes, or a save that loads with reduced progress are stop signals. Restore the clean files and backup before testing a newer build.

Separate loader failures from mod failures

Start the clean game first, then test the required loader without optional mods. Add one mod only after the loader reaches the menu without errors. If the game stops launching, remove the last mod and repeat the same check. This order identifies whether the game update broke the loader, one content package, or the interaction between two packages.