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

Daily Quests + FTB Quests Incompatibility/Crash #2786

Open
wExtraBenji opened this issue Dec 7, 2024 · 4 comments
Open

Daily Quests + FTB Quests Incompatibility/Crash #2786

wExtraBenji opened this issue Dec 7, 2024 · 4 comments
Assignees
Labels
Incompatibility Two mods aren't working together. Mod Label Missing A new issue where the mod label has yet to be assigned.

Comments

@wExtraBenji
Copy link

Information

Minecraft version: 1.21.1
Modloader: Neoforge 21.1.83
Environment: Singleplayer
First mod name: Daily Quests
First mod version: 1.21.1-1.8

Second mod name: FTB Quests
Second mod version: 2101.1.1

Description

When both mods are installed, a crash happens at day rollover that then causes any subsequent world launch attempts to crash as well. Was able to launch the world again after turning daily quests off.

Crash report

Here
crash-2024-12-06_20.56.10-client.txt

@wExtraBenji wExtraBenji added Incompatibility Two mods aren't working together. Mod Label Missing A new issue where the mod label has yet to be assigned. labels Dec 7, 2024
@wExtraBenji
Copy link
Author

Update: this incompatibility corrupted the entire modpack. trying to connect to any singleplayer worlds caused "failed to sync registries from the server: java.lang.nullpointerexception" errors which would then kick me out to the multiplayer menu. If I tried again it would crash minecraft entirely.

@James103
Copy link

James103 commented Dec 16, 2024

trying to connect to any singleplayer worlds caused "failed to sync registries from the server: java.lang.nullpointerexception" errors which would then kick me out to the multiplayer menu.

Can you please post the logs you got from this failure?
Specifically, if the disconnect created what looks like a crash report, named disconnect-YYYY-MM-DD_HH.MM.SS-client.txt, please attach it here.

If I tried again it would crash minecraft entirely.

Can you please attach the corresponding crash report?

@wExtraBenji
Copy link
Author

crash-2024-12-13_18.53.04-client.txt
2024-12-13-1.log
I believe this should be the right log
the crashlog is for sure

@wExtraBenji
Copy link
Author

Also if these aren't good enough let me know, I deleted the first pack that got corrupted but I can try and recreate the circumstances to get new logs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Incompatibility Two mods aren't working together. Mod Label Missing A new issue where the mod label has yet to be assigned.
Projects
None yet
Development

No branches or pull requests

3 participants