Startup incompatibility screen does not work with Canary
rlnt opened this issue ยท 7 comments
Version Information
- canary-mc1.18.2-0.0.9
- forge-40.1.84
- windows 11 pro
- curseforge launcher
Expected Behavior
When booting the game, a message on a dirt screen should pop up about which mod has compatibility issues according to the respective mod.toml
file.
Actual Behavior
The game won't start if there is a compatibility issue with mods. The window doesn't even open. As an example, the latest version of AE2 (appliedenergistics2-forge-11.6.2) with an older version of JEI (jei-1.18.2-9.7.2.281) can be used. The AE2 version relies on v10 of JEI and is not compatible with v9.7 anymore. Usually, this is displayed on startup but with Canary, the game won't start.
The only log message you get that could slightly show you what's wrong is:
[main/ERROR]: Unsupported installed optional dependencies: jei
Reproduction Steps
- Use two mods that are incompatible with another
- Start the game
- The window won't open
Other Information
startup log (a crash report is not generated since the game doesn't even start)
Can also confirm that the mod incompatibility screen doesn't pop up for me too when Canary is installed.
This issue is not from Canary, the issues you have is other mod compatibilities :
- Better Biome Blend crashes with Rubidium.
- MineTogeather mod crashes Game Menu Mod Option.
Good Luck!
I found out about Canary being the issue by binary search. All other mods are working fine together. The game does not start if Canary is enabled. The same happens with other Lithium forks so I guess this is probably an upstream issue.
The mods you mentioned work pretty fine.
Just for the sake of proving my point, I created a new instance with just these:
And it still happens. It does not happen without Canary. Here's the log from the minimal reproduction setup: https://pastebin.com/a53JE8vY
Please don't shift issues to other mods if you are not a 100% certain about the cause of the issue, please.
Sorry for shifting the issue to other mods but i saw the mod errors in the log, i apologize for that!
The issue is fixed in both 0.1.1 for MC 1.19.2 and 0.0.10 for MC 1.18.2.
I hope you have a good day!