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 on start (again) #5

Closed
entusiastaIA opened this issue Oct 12, 2022 · 6 comments
Closed

Crash on start (again) #5

entusiastaIA opened this issue Oct 12, 2022 · 6 comments
Assignees
Labels
bug Unexpected behavior other mod Not compatible with other mod, needs work from them

Comments

@entusiastaIA
Copy link

Describe the bug
I've seen this has happened before, but cannot know the reason. On latest Fabric 1.18.2 version (and previous one), 1.1.0.0 (and 1.0.0.2), if I add the mod i cannot launch minecraft.

Captura

@entusiastaIA entusiastaIA added the bug Unexpected behavior label Oct 12, 2022
@Crystal-Spider Crystal-Spider added the other mod Not compatible with other mod, needs work from them label Oct 12, 2022
@Crystal-Spider
Copy link
Member

The reason of the crash is similar, but different.
Basically another mod is trying to modify the same part of the code I do, and so it crashes.
The incompatible mod is sihywtcamd (So I heard you were talking crap about Minecraft's difficulty?).

Anyway, using the latest versions of Soul Fire'd and sihywtcamd I can't replicate the issue (my game launches) for 1.19.2.
Using 1.18.2 I can replicate the issue, but it's likely an issue of sihywtcamd: most probably its latest 1.18.2 version does not include commit c032277b48b02a09d38efd957e3c99c23f550d6f that fixed incompatibility with other mods.

I opened a new issue on the other mod GitHub.

@entusiastaIA
Copy link
Author

Thank you very much for taking the time to check it this much! Could that issue with that mod affect other one's too? I am trying to narrow down random crashes I am getting that afterwards leave the world unloadable.

I can confirm that removing sihywcamd and enabling back SoulFire'd allow me to run the game again.

@Crystal-Spider
Copy link
Member

Definitely this issue can affect other mods, but only if other mods are changing something in the behavior of a Zombie attack.
On my end I cannot do anything to fix this, it's up to sihywcamd to fix that by porting the fix that's already in 1.19.2 to 1.18.2.

If it's fine for you, I'd close this issue and you can follow the progress on the other issue I opened on sihywcamd.

@entusiastaIA
Copy link
Author

Perfect thank you!

@charlyb01
Copy link

charlyb01 commented Oct 13, 2022

Hello, I'm going to update the 1.18 version to get the fix then. Sorry for that, I noticed it a bit late so it stayed on this version!
[Edit] Done!

@entusiastaIA
Copy link
Author

Thank you very much, I updated and it is working! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Unexpected behavior other mod Not compatible with other mod, needs work from them
Projects
Development

No branches or pull requests

3 participants