Mod Compatibility

AKA: “Why does the server crash when I add SpongeForge?”

SpongeForge tries to maintain compatiblity with as many mods as possible. However, the enormous breadth of possibilities available to mod developers can make this goal very difficult. Some mods simply will not work with SpongeForge present, others need configuration settings or alternative versions to be compatible, and many simply need to initialise after SpongeForge to work correctly. Sometimes there will be a diagnostic message in the server log telling you what broke, but often it can be very hard to tell what went wrong.

To help you resolve which is which, and how to fix the problem (if possible), we have prepared this list of mods that can cause problems when used alongside SpongeForge. Please note that, whilst we will try to keep it current, changes may happen as mods are updated. You can help by letting us know when relevant changes happen, on Discord or GitHub.

Known Incompatibilities

Old Mixins

First, a general note: If there is a warning about “old mixins” in the server log, the first step you should attempt is to rename the SpongeForge file, to make it first in the mod loading order. This can usually be done by prefixing the SpongeForge jar file name with aaa_, giving a filename like aaa_spongeforge-1.16.5-36.2.5-8.1.0-RC1312. This makes it load the Sponge version of Mixin first, and can resolve many problems in one step.

Forge Permissions

Some mods may register their own permissions with Forge. These cannot be tracked by mods, including SpongeForge due to a bug that was fixed in December 2021 (after forge stopped updating 1.16.5) so permissions plugins will not be able to use these permissions.


Alex’s Mobs

All The Mods 6

Applied Energistics 2

Bountiful Baubles

Conquest Reforged

Create Mod


Physics Mod

Progressive Bosses

Random Patches

Tinkers’ Construct

Twilight Forest

Valkyrien Skies

World Edit