You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current plan of record is to use Architectury to achieve mod loader independence for Sodium. The platform-specific code for Fabric and NeoForge will be located in separate modules, and they will both share a "common" module that is platform-agnostic.
Eventually, we anticipate this will eliminate the need for Forge ports of Sodium, and that it will overall lead to better mod compatibility (read: improved user experience) with Sodium on both platforms.
Things which are in scope:
Providing a fully featured version of Sodium for the NeoForge platform that can sufficiently deprecate other forks
Working with addon mods (notably Iris) to enable compatibility with Sodium on other platforms
Not in scope:
Supporting mods which rely on internal ABI of the existing Forge forks
Backporting existing versions of Sodium to older versions of Minecraft
The text was updated successfully, but these errors were encountered:
The current plan of record is to use Architectury to achieve mod loader independence for Sodium. The platform-specific code for Fabric and NeoForge will be located in separate modules, and they will both share a "common" module that is platform-agnostic.
Eventually, we anticipate this will eliminate the need for Forge ports of Sodium, and that it will overall lead to better mod compatibility (read: improved user experience) with Sodium on both platforms.
Things which are in scope:
Not in scope:
The text was updated successfully, but these errors were encountered: