Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash, mod conflict most likely #6

Open
corgiblu opened this issue Sep 3, 2018 · 7 comments
Open

Crash, mod conflict most likely #6

corgiblu opened this issue Sep 3, 2018 · 7 comments

Comments

@corgiblu
Copy link

corgiblu commented Sep 3, 2018

https://paste.ee/p/nexHP

https://modlister.com/beanaboston

Crashes before loading screen even pops up. I have foamfix, betterfps, and optifine (already tried disabling optifine and that didn't work) I'll try with foamfix and betterfps later. I've got some issues with my CT scripts that i've gotta fix and would like to get working on those.

Works fine with the mod on it's own btw. So most likely a mod conflict.

@SalmonSays
Copy link

I've been checking launch alongside Foamfix, Optifine, and 152 other mods without problems so far to effectively stress test for problems on my branch. It's possible BetterFPS is the culprit, though why it in particular would cause "Required mixin config mixins.smartmoving.core.json requires mixin subsystem version 0.7.8" to rear its head (sort of again except 0.7.8->0.7.5 instead of 0.7.10->0.7.8) is beyond my current understanding of mixin.

TL;DR it's probably worth checking if BetterFPS specifically causes the crash because if not something wacky is going on under the hood.

@corgiblu
Copy link
Author

corgiblu commented Sep 3, 2018 via email

@Tommsy64
Copy link
Owner

Tommsy64 commented Sep 3, 2018

The mod LagGoggles-FORGE-1.12.2-4.1.jar is loading its own older version of Mixins before SmartMoving is (See line 471).

Decreasing the required Mixins version to 0.7.5 shouldn't cause any major issues.

@HighwayStar54
Copy link

HighwayStar54 commented Sep 22, 2018

Decreasing the required Mixins version to 0.7.5 shouldn't cause any major issues.

How could I do that? I'm using MultiMCand I have his same problem, is there any conventional way to change the mixins version?

EDIT: Oh and, for me the incompatible mod is Malisis Core.

@Tommsy64
Copy link
Owner

@HighwayStar54 Malisis core appears to be loading Mixins 0.7.4 before SmartMoving can load 0.7.8.

@HighwayStar54
Copy link

Ok, I asked the mod author if they could update their mod, is there anything more I could do or does the waiting game start now?

@Tommsy64
Copy link
Owner

Tommsy64 commented Oct 2, 2018

I'm not 100% sure, but I think forge examines mods in alphabetical order. Try renaming the SmartMoving-1.12.2-0.0.4.jar to something like aaaaaaaa_SmartMoving-1.12.2-0.0.4.jar. This might cause SmartMoving's version of Mixins to be loaded first.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants
@Tommsy64 @SalmonSays @HighwayStar54 @corgiblu and others