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

Anyone else experiencing conflicts and -1 exit codes after updating to the latest version? 1/2/25 #4344

Closed
Space-Bacons opened this issue Jan 2, 2025 · 1 comment
Labels
support Issues closed due to being a support request.

Comments

@Space-Bacons
Copy link

Space-Bacons commented Jan 2, 2025

I seem to be running into some issues after installing the latest 0.114 update to fabric. I also updated sodium and Iris as well.
Fabric seems to be having trouble with creativecore and crashes on startup. Then when I removed CC, and ambientsound, it started conflicting with the Waystones mod. After removing both of these mods, the game will launch, but I just encountered an in game crash when I tried to use a furnace, and this time it seems the Wurst client is the issue, which is weird because a new update just came out for that a couple of days ago. I have the crash report for the last instant ready to go. Edit: Double checked to make sure, and it did repeat the crash after trying to use the furnace, so it's definitely not a one-time whoopsie

https://pastebin.com/PSLELaye

Let me know if you've been having trouble as well, or if things are running smoothly for you, and I have to do some more digging on my end. I can also simulate the other instances for crash reports with CC and waystone as well to see if it really is the Fabric update causing these troubles. Perhaps the mod authors have yet a chance to catch up? Makes sense that if the library upholding and loading most of these mods is updated, then said mods would have to update too. Thanks!!

@modmuss50 modmuss50 added the support Issues closed due to being a support request. label Jan 2, 2025
Copy link

github-actions bot commented Jan 2, 2025

👋 We use the issue tracker exclusively for final bug reports and feature requests. However, this issue appears to be better suited for either a discussion thread, or a message on our discord server. Please post your request on one of these, and the conversation can continue there.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
support Issues closed due to being a support request.
Projects
None yet
Development

No branches or pull requests

2 participants