Newer Fabric Release Errors
sonic2kk opened this issue ยท 1 comments
Describe the bug
The game will crash when trying to load the mod using Fabric Loader version 0.13.3, which I installed from MultiMC. I believe this installs Fabric 0.47.9+1.18.2 from looking at the Fabric develop page.
There are some mod incompatibility/dependency errors at the beginning of the Minecraft log:
[03:16:57] [main/INFO]: Loading Minecraft 1.18.2 with Fabric Loader 0.13.3
[03:16:57] [main/WARN]: Mod resolution failed
[03:16:57] [main/INFO]: Immediate reason: [HARD_DEP_NO_CANDIDATE lambdacontrols 1.7.1+1.17 {depends fabric @ [>=0.36.0]}, ROOT_FORCELOAD_SINGLE lambdacontrols 1.7.1+1.17]
[03:16:57] [main/INFO]: Reason: [HARD_DEP lambdacontrols 1.7.1+1.17 {depends fabric @ [>=0.36.0]}, HARD_DEP lambdacontrols 1.7.1+1.17 {depends spruceui @ [>=3.2.0]}]
[03:16:57] [main/INFO]: Fix: add [add:fabric 0.36.0 ([[0.36.0,?)])], remove [], replace [[spruceui 3.2.0+1.17] -> add:spruceui 3.2.0 ([[3.2.0,?)])]
[03:16:57] [main/ERROR]: Incompatible mod set!
net.fabricmc.loader.impl.FormattedException: Mod resolution encountered an incompatible mod set!
A potential solution has been determined:
- Install fabric, version 0.36.0 or later.
- Replace mod 'SpruceUI' (spruceui) 3.2.0+1.17 with version 3.2.0 or later that is compatible with:
Unmet dependency listing:
- Mod 'LambdaControls' (lambdacontrols) 1.7.1+1.17 requires version 0.36.0 or later of fabric, which is missing!
- Mod 'LambdaControls' (lambdacontrols) 1.7.1+1.17 requires version 3.2.0 or later of mod 'SpruceUI' (spruceui), but only the wrong version is present: 3.2.0+1.17!
To Reproduce
Steps to reproduce the behavior:
- Install Fabric Loader with MultiMC 5.
- Install latest LambdaControls release.
- Launch game
Expected behavior
Minecraft should launch.
Screenshots
N/A.
Desktop (please complete the following information):
- OS: Arch Linux with KDE Plasma Wayland Session
- Minecraft 1.18.2
- Fabric 0.47.9+1.18.2
- Mods: Happens without any other mods present.
- Version 1.7.0+1.17.1
- Branch 1.17.1
Additional context
If this is a compatibility issue with 1.18.X, Curseforge lists the mod as supporting 1.18 and should likely be amended.
