Crashed just after creating a new world, broke down a tree, collected my bonus chest and made a few stonepaxels, then put some stuff in my backpack, equipped my charms and ring, then jumped like 3 times around then boom
latest.log: https://gnomebot.dev/paste/mclogs/9TYiI2S
crash-2025-11-03_17.10.35-server.txt: https://gnomebot.dev/paste/mclogs/yhZ8dTH
crash_assistant_app.log: https://gnomebot.dev/paste/mclogs/m0wNy3W
modlist.txt: https://gnomebot.dev/paste/mclogs/0f6eHGQ
#Crash on new world
1 messages · Page 1 of 1 (latest)
wharraido
Linggango crashed. The logs have been uploaded to gnomebot.dev:
latest.log | crash-2025-11-03_17.10.35-server.txt | crash_assistant_app.log | modlist.txt | CurseForge: skip launcher
Mod list changes on top of the modpack:
[2;32m16[0m added, [2;31m17[0m removed, [2;34m23[0m updated.
i didnt see the giant green button lol
happened again and I just loaded in
I cannot create new worlds at all
it crashes instantly
Linggango crashed. The logs have been uploaded to gnomebot.dev:
latest.log | crash-2025-11-03_17.24.42-server.txt | crash_assistant_app.log | modlist.txt | CurseForge: skip launcher
Mod list changes on top of the modpack:
[2;32m16[0m added, [2;31m17[0m removed, [2;34m23[0m updated.
Bonsai Ghosts is being flagged by C2ME on world generation.
what mod are those from
It's the issue that it's trying to do randomized numbers which C2ME is flagging.
What you can do if you want to bypass C2ME:
Find c2me.toml in the config
Set fixes.enforceSafeWorldRandomAccess = false
This will make c2me log it was a warning rather than forcing a crash.
will this create any further conflicts?
It shouldn't unless other mods cause issues after the world is made and loaded.
so that config setting would make any mod bypass C2ME?
i ll try it nonetheless
just hoping that it wont affect future crash logs
Not like "bypass", but it will make C2ME log it as a warning in the console rather than crashing MC.
thanks!
Let me know if this works because multiple people are having an issue with the same mod.