Incompatible with NeoForge version of Sodium

[leetftw]

Minecraft version

26.1.x

Describe the bug

The game crashes upon joining a world

Steps to reproduce

1. Install latest NeoForge (26.1.2.76) and Sodium (NeoForge version, 0.8.12+mc26.1.2)
2. Install Forgified Fabric API and Forgified Fabric Loader (0.152.1+3.0.5+26.1.2 and 2.5.75+0.18.4+26.1 respectively)
3. Try creating/opening/joining any world and the game will crash

Logs

https://gist.github.com/leetftw/90cab33752f3ba3cbc58f7a0830ef7ba

Additional context

No response

[Lolothepro]

It's caused by Sodium, not by ForgifiedFabricAPI

[Su5eD]

It looks like Sodium declares they provide a custom renderer in their metadata, which causes Indigo to disable itself and look for another renderer instead, but that is never registered.

CC @IMS212 might wanna take a look at this

[leetftw]

Thanks for helping investigate, I really appreciate it! I will close this for now as it does not seem to be directly caused by ForgifiedFabricAPI. See related issue on Sodium here: CaffeineMC/sodium#3766

[leetftw]

From what JellySquid told me and what I read on the Sodium Discord server, there are no plans for FRAPI support for newer versions of Sodium. I understand their POV that it is hard to maintain, but it poses a problem for ForgifiedFabricAPI.

I understand that actually getting the Fabric Rendering API to work would require stuff on the Sodium side. However, not all Fabric mods (for when Connector gets ported) or mods that use ForgifiedFabricAPI use the rendering APIs. Currently even with no mods using FRAPI, the game crashes with Sodium installed, which is not ideal.

Would it be possible to make it only crash when the FRAPI is actually invoked by a mod?

[Su5eD]

In that case we're going to provide FRAPI support ourselves if possible