Conflict between latest version of Sodium and Controlify! [URGENT]

Mod Info (fill out the following information)

• Mod name: Sodium
• Mod version: sodium-fabric-0.8.11+mc1.21.11.jar

Describe the problem
Controlify loads before Sodium and attempts to accquire a Default Config before the Configs are loaded! (pretty much incompatible because it's trying to load a json before it's ready, resulting in a HARD crash.

To Reproduce
Steps to reproduce the behavior:

1. Go to make a new instance including Sodium, Iris, and Controlify.
2. Use settings provided to make sure it's the buggy behavior,
3. launch your game.
4. yeah.

Expected behavior
The game should prioritize loading controlify AFTER Sodium is initialized (if detected)!

Screenshots
I could just add my log file...

crash-2026-05-05_22.20.29-client.txt

Minecraft Info (please complete the following information):

• OS: Windows 10
• Minecraft Version: 26.1.2 (same thing as 26.1.1, just a TINY hotfix with messages in servers.)[I suggest you look up the exact update ahhaha]
• Controlify Version: 3.0.0 for fabric 26.1.1

Additional context
Add any other context about the problem here.

Start by reproducing the crash with Sodium, Iris, and Controlify on the reported Minecraft versions, then inspect the attached crash log for the configuration-loading failure. Trace the initialization ordering that causes Controlify to acquire its default config before Sodium's configs are ready; done means the reported setup launches without this crash.