A fatal error has been detected by the Java Runtime Environment (beebuddy) (Kilt-20.1.14+build.5363)

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>

BluSpring · 2mo ago

Happy new year, is it good to say that at almost the end of January? Anyway, guess who's back again, finished my internship, still got other things to do but I decided to take a break from it and drop a bunch of changes for Kilt. Kilt v20.1.13 is now released. ## Kilt no longer depends on Forge Config API Port. One less dependency, Kilt now basically provides Forge Config API Port within itself. We don't have to worry about it anymore, we now have full control over our configs. Oh yeah, this allows you to actually edit your configs now, hopefully. Also say goodbye to the log spam that it would give previously. We now only have 2-4 dependencies for Kilt now. Eventually we might even be able to drop Sodium as a dependency. ## Worldgen should be fixed now! There was a time where world feature generation was broken because of the bundled Feature Recycler mod in Kilt. That no longer exists now, especially because Fabric API has their own safeguard now ([FabricMC/fabric-api#5142](https://github.com/FabricMC/fabric-api/pull/5142)). You can look at the differences here: [KiltMC/Kilt#564](https://github.com/KiltMC/Kilt/issues/564) ## Fixed items not sliding on ice That was an awful bug. How did no one catch that until [KiltMC/Kilt#603](https://github.com/KiltMC/Kilt/issues/603) was made. That's been broken for 8-9 months! ## Fixed Vanilla options resetting automatically Thanks <@195239733553659904> for the help with this one, turns out the limited options loading in FML had a use. That was interesting. ## Finally fixed that awful tooltip duplication bug I'm sure some of y'all are familiar with the issue where tooltips were getting duplicated sometimes when looking at it. This was especially prevalent in Zenith, I believe? That was a Forge fix in one of its hooks so I missed it. I disabled that entirely, so now it doesn't wrap automatically anymore. --- We're still working on 1.21.1, Alpha's been focusing on it quite a bit himself, while I've been busy with a lot so I haven't been able to work on it personally. Once 1.21.1 is functioning I plan to skip entirely to 26.1, because god I am so tired of working with 1.20.1 and 1.21.1. Doesn't mean we're gonna stop supporting them though. Thank you for being so patient and for sticking around. Feel free to help support the project by either [contributing code to the project](https://github.com/KiltMC/Kilt/pulls), or by [donating some money to me](https://ko-fi.com/bluspring), either one works. Thank you. <@&1117923300371337348>

BluSpring · 2mo ago

Happy birthday, Kilt :]

BluSpring · 3mo ago