Hi,
I'm a maintainer on Sodium and today we published the first alpha from our graduated backport experiment. This means that we now have Sodium 0.8.12 on 1.21.1. You can find more information about this in our blog post on discord.
We've since noticed Supplementaries interacting with Sodium and crashing on world load. In particular it appears your CompatSodiumFluidRendererMixin is failing here. The gist is that since 0.8.x includes many changes to various parts of Sodium, including our new Config API, mods such as this one will encounter breakage when users (cluelessly) update modpacks with the latest published versions.
If you'd like to coordinate more closely with us, you're invited to our discord server. I intend for this to be considered a "feature" since this software is currently in alpha and not the mainline release. A lack of compatibility is not a fault on your part, but rather I would just like to notify you of the situation. I hope this doesn't cause too much trouble!
I've made this issue in addition to the user report to point out some general information. You are of course free to close and/or otherwise handle this issue as you please.
Thanks!
Hi,
I'm a maintainer on Sodium and today we published the first alpha from our graduated backport experiment. This means that we now have Sodium 0.8.12 on 1.21.1. You can find more information about this in our blog post on discord.
We've since noticed Supplementaries interacting with Sodium and crashing on world load. In particular it appears your
CompatSodiumFluidRendererMixinis failing here. The gist is that since 0.8.x includes many changes to various parts of Sodium, including our new Config API, mods such as this one will encounter breakage when users (cluelessly) update modpacks with the latest published versions.If you'd like to coordinate more closely with us, you're invited to our discord server. I intend for this to be considered a "feature" since this software is currently in alpha and not the mainline release. A lack of compatibility is not a fault on your part, but rather I would just like to notify you of the situation. I hope this doesn't cause too much trouble!
I've made this issue in addition to the user report to point out some general information. You are of course free to close and/or otherwise handle this issue as you please.
Thanks!