Can't launch game with latest version of Sodium & Sodium Extra & Iris & Indium

A few minutes ago I updated my modpack and it doesn't run anymore. Only these 4 mods from the title have been updated.
17 Replies
LilyBot
LilyBot2y ago
2023-05-01-2.log uploaded to mclo.gs
Log Uploading is deprecated in LilyBot. It has been implemented in Allium instead. It will be removed in 4.9.0
Uploaded by Liski#7550
green512
green5122y ago
Sodium Extra and Indium need to be disabled until they release versions that are compatible with the sodium that was just released. and Continuity, which depends on Indium
Deleted User
Deleted UserOP2y ago
But they already release it
No description
No description
Deleted User
Deleted UserOP2y ago
So the only issue is from Continuity?
green512
green5122y ago
No, the dependency is on Sodium 0.4.11, not minecraft. Mods like Sodium Extra are tied to the specific version of Sodium. If Sodium updates, they have to update as well. Oh, I see that Indium and Sodium extra just released versions within the last few hours, so I guess they're ready.
Deleted User
Deleted UserOP2y ago
Yes, I mentioned this at the beginning of our conversation, when I attached these 2 screenshots.
No description
Deleted User
Deleted UserOP2y ago
It turns out that the only problem in Continuity?
green512
green5122y ago
No, the problem is chunksfadein, another mod that attempts to modify Sodium
Deleted User
Deleted UserOP2y ago
I tried to run the game only with these modifications - everything started fine. So the problem is none of what you suggested.
No description
green512
green5122y ago
The log you posted clearly shows chunksfadein is the issue:
[09:10:20] [Render thread/ERROR]: Mixin apply for mod chunksfadein failed #chunksfadein:chunksfadein.mixins.json:chunk.RenderRegionMixin from mod chunksfadein -> me.jellysquid.mods.sodium.client.render.chunk.region.RenderRegion: org.spongepowered.asm.mixin.transformer.throwables.InvalidMixinException @Shadow field chunks was not located in the target class me.jellysquid.mods.sodium.client.render.chunk.region.RenderRegion. Using refmap chunksfadein-refmap.json
[09:10:20] [Render thread/ERROR]: Mixin apply for mod chunksfadein failed #chunksfadein:chunksfadein.mixins.json:chunk.RenderRegionMixin from mod chunksfadein -> me.jellysquid.mods.sodium.client.render.chunk.region.RenderRegion: org.spongepowered.asm.mixin.transformer.throwables.InvalidMixinException @Shadow field chunks was not located in the target class me.jellysquid.mods.sodium.client.render.chunk.region.RenderRegion. Using refmap chunksfadein-refmap.json
Deleted User
Deleted UserOP2y ago
And even with the addition of Continuity, it still starts up.
Deleted User
Deleted UserOP2y ago
Keep a new log with the successful launch of the modifications that I showed in the screenshot above.
green512
green5122y ago
Continuity is not the issue, I mentioned that it would need to be disabled if Indium is not present, but Indium is present.
green512
green5122y ago
On the chunksfadein discord:
No description
Deleted User
Deleted UserOP2y ago
That's the problem: I want to know what exactly breaks Sodium. From the 20-minute tests that I conducted in parallel with talking with you, I found out that the build with these modifications starts, which means that something else breaks compatibility.
No description
green512
green5122y ago
that doesn't mean the problem is not chunksfadein, it just means you didn't hit the bug. It does not mean the bug doesn't exist. for example sometimes the game will boot but crash when you try to load a world, and other things like that.
Deleted User
Deleted UserOP2y ago
@green512, thank you! All I have to do is wait for the Chunk Fade In update. Now I removed it from the assembly and it started, and I was also able to boot into the world.
Want results from more Discord servers?
Add your server