[1.11.2] Mod dependency cycle w/ Better With Mods
jesmores opened this issue ยท 5 comments
Updated to latest Quark 1.2-92. Likely related to the recent fix for #436
Full log here: https://gist.github.com/jesmores/a03f1e19781f625d5a35565ca39be23f
Relevant excerpt:
[18:41:56] [Client thread/ERROR]: A dependency cycle was detected in the input mod set so an ordering cannot be determined
[18:41:56] [Client thread/ERROR]: The first mod in the cycle is FMLMod:quark{r1.2-92}
[18:41:56] [Client thread/ERROR]: The mod cycle involves
[18:41:56] [Client thread/ERROR]: APIContainer{BetterWithModsAPI:Beta 0.6} : before: [quark], after: [betterwithmods]
[18:41:56] [Client thread/ERROR]: Dummy Container (AfterAll) @1866281916 : before: [], after: []
[18:41:56] [Client thread/ERROR]: Dummy Container (After) @848940191 : before: [], after: []
[18:41:56] [Client thread/ERROR]: FMLMod:betterwithmods{1.2.7-1.11.2} : before: [survivalist], after: [mantle, tconstruct, minechem, natura, terrafirmacraft, immersiveengineering, quark, mekanism, thermalexpansion]
[18:41:56] [Client thread/ERROR]: FMLMod:quark{r1.2-92} : before: [autoreglib], after: []
[18:41:56] [Client thread/ERROR]: FMLMod:autoreglib{1.1-4} : before: [], after: []
This looks to be on Better With Mod's side, Quark does not add any load order properties related to Better With Mods, as stated by the log.
it's the recently added better with mods api, the api container loads after the parent mod and before the implementing mod (quark), causing a cycle, because bwm actually also expects to load after quark for some reason.
