Some of you might have noticed issue #572 and the "discussions" going on in there for supporting a fork of Embeddium, called Celeritas, and dropping support for Sodium, and their threats to fork Kilt and remove the Sodium dependency.

The reason why we haven't removed Sodium as a dependency yet? We can't. Not at the moment.
There is a bug with rendering in Kilt that I have still yet to be able to figure out, where the chunk rendering becomes visibly corrupted with holes in the world. This issue does not occur when using Sodium. The temporary solution was to mark Sodium as a dependency to make sure this doesn't cause problems for users that don't use Sodium. Sodium is also always used in our development environment to make sure we don't break anything rendering-related.

I never got around to fixing Kilt working on Vanilla purely because I don't have the prerequisite rendering knowledge to fix it myself. I'll likely revisit it some other time, or if someone wants to figure it out themselves, feel free to PR a fix. I most likely got a patch wrong somewhere.

Now, as for Embeddium / Celeritas... considering the aggressive way they decided to come in for requesting for that support, frankly I do not plan to add support for it myself. Someone else can PR it in if they want to, as long as it can co-exist with Sodium too. I'm not intending to drop support for Sodium, and I'm especially not gonna do that just because some people came in and threatened to fork Kilt to remove it themselves.

(fun fact: the mixins in Kilt for Sodium support were originally designed to not fully require a dependency on Sodium, there was originally intention for both Sodium and Embeddium to work with Kilt a few years ago, but the codebases diverged enough for me to not be able to properly support it. if they decided to look at it a tiny bit closer, they might've been able to see it, rather than make those threats.)

@1117923409687490571
image.png
Was this page helpful?