[1.21.1 Neoforge] Incompatible with required dependency

[dulphMain]

Sodium Options API requires Reese's Sodium Options, but Reese's Sodium Options is not compatible with Sodium Options API (in 1.21.1 neoforge).

[Camawama]

The same thing is happening to me.

[pickachulvr2010-ux]

this is the same problem everyone is having, but the mod creator is being lazy or something

[LunaDalenuit]

I don't believe this is an issue with Sodium Options API but an issue with Reese's Sodium Options having put the wrong version of Sodium Options API in the metadata.

[SavageVictor]

Yep same issue, tried to remove the incompatibility error in metadata, launched and get crash in video settings. I guess some specific version is needed for it to work, though I don't know which one.

[pickachulvr2010-ux]

I don't believe this is an issue with Sodium Options API but an issue with Reese's Sodium Options having put the wrong version of Sodium Options API in the metadata.

the second you get rid of the sodium options API everything returns to normal, Rees's s up to date while the crater of sodium options API is basically dead

[deadlywolf301]

and unfortunately sodium options api is a required dependency for toni's immersive lanterns so i guess his mods are useless in 1.21.1 neo, i also tried it with embedium and that didn't work either

[SaturnsRing98]

You don't actually need the Options API to use Toni's Immersive Lanterns, but you'll need to manually edit the options file.
However, I greatly wish to see the Options API updated. Here's the error in text:
[18:24:36] [main/ERROR]: Incompatibilities between mods: Mod 'reeses_sodium_options' is incompatible with 'sodiumoptionsapi', versions: '[0,)'; Version found: '1.0.10'
[18:24:50] [Render thread/FATAL] [ne.ne.fm.ModLoader/CORE]: Error during pre-loading phase: Mod reeses_sodium_options is incompatible with sodiumoptionsapi 0 or above Currently, sodiumoptionsapi is 1.0.10
Like what was mentioned above, simply editing the metadata does let the game launch, but the game crashes in video options, so it it not fully on Reese's end. Reese also clarifies the conflict is left as is due to Sodium also using it's own options API, stated here: FlashyReese/reeses-sodium-options#172 (comment)