Crashes on startup when Iguana Tweaks Reborn is installed [Quark 1.20.1 Beta]
MidasMischief opened this issue ยท 5 comments
The current public beta test for Quark 1.20.1 crashes when Iguana Tweaks Reborn is installed, checked the log file and its likely due to do both mods modifying sponges, I've tried disabling improved sponges in the quark config but the same crash happens so it could be something else or the mixin is not actually being disabled im not sure. I've attached the log if that helps and heres the mod link for iguana tweaks reborn.
https://www.curseforge.com/minecraft/mc-mods/iguanatweaks-reborn
I'm getting a crash with Inventory Sorter installed which may be caused by the same section of code (spongepowered.asm.mixin). Would you like the log file here, or would you like a separate issue created? (Side note my pack has 198 mods and Quark seems to be functioning fine with all the rest)
I'm getting a crash with Inventory Sorter installed which may be caused by the same section of code (spongepowered.asm.mixin). Would you like the log file here, or would you like a separate issue created? (Side note my pack has 198 mods and Quark seems to be functioning fine with all the rest)
Create a new issue please
I'm getting a crash with Inventory Sorter installed which may be caused by the same section of code (spongepowered.asm.mixin). Would you like the log file here, or would you like a separate issue created? (Side note my pack has 198 mods and Quark seems to be functioning fine with all the rest)
Create a new issue please
Turns out its not Inventory Sorter. Trying to narrow down where the conflict is.
I'm getting a crash with Inventory Sorter installed which may be caused by the same section of code (spongepowered.asm.mixin). Would you like the log file here, or would you like a separate issue created? (Side note my pack has 198 mods and Quark seems to be functioning fine with all the rest)
Create a new issue please
Turns out its not Inventory Sorter. Trying to narrow down where the conflict is.
Don't worry just make a new issue with the log & I'll take a look