-
Notifications
You must be signed in to change notification settings - Fork 0
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
Exception in server tick loop when loading into any world, or creating new world #49
Comments
Apologies this doesnt seem to have been caused by Global-Packs |
reopening this - on further testing this is related to Global Packs but I am having a really hard time figuring out what other mods cause this. In my pack If I add this mod, I can not create a new world any more. I can load into existing world so its generation related? I have tried to isolate this to what other mod is conflicting but I have not found it, and think it might actually be more than 2! Terrablender also could be related but Global Packs and Terrablender alone are fine.. I'm going round in circles but thought I'd report it anyway |
According to the logs it's an endless loop during world gen. |
Thanks for getting back to me - I did consider this. Currently there is only these 2 resource packs which I do not use, but reinstall themselves when I start the pack if I delete them! I did wonder if these were the cause so I set the options to not look in resoucepacks For testing I have nothing in any of the global_packs folders but I still get the issue. If I disable the mod I can generate a world fine again. I understand this might not be entirely this mods issue, and possibly multiple generation mods at play but I cant find it :/ 2 new logs jsut in case where I only load game and try to make new world. latest.log EDIT, I am going to keep testing mods individually as I think this is a combo or 3+ mods.. |
Those logs provide the same info, infinite loop in world gen. The one thing I could imagine is another mod trying to do something similar to Global Packs which causes an incompatability. A quick way to test out what combination of mods might cause this, would be binary search. There are also no packs loaded by Global packs based on the log. I doubt it would be supplementaries as that's commonly used with the mod. I can't say that I know most other ones though. |
Thanks! Yes I use the binary method, its just hard with so many dependencies haha.. So far I defo know Terrablender is part of this, but if I turn that off it turns off loads of other mods.. I tried a pack with Just those mods though, and it also worked fine! So yeah.. more searching needed |
Disabling Tectonic v2.2 also allows the world to generate, however putting Global Packs and Tectonic in a pack alone DOES work.. |
I have narrowed this down somewhat and you can close it if you want as this is some weird deep interactions of many mods. In case you want to know any one of the below will fix it in my pack:
I tried to see if a new modpack with just KubeJS, a server script, Tectonic, Global Packs and Dramatic Doors would replicate the crash, however it doesnt, and at this point, ive spent 8 hours today and 4 hours yesterday and am fed up lol.. removing Dramatic Doors is not an issue for me, and now my new worlds create fine. Let me know if you want me to export the current 'test' pack I have which I was going through mod by mod, until I found KubsJS and then Dramatic Doors.. its still got 159 mods in it I didnt check yet.. but yeah I am done with this haha |
V1.14.5, Forge 1.19.2
Just adding this mod and loading into an existing world, or trying to create a new world causes this crash to desktop. I have added nothing to global_packs yet and have nothing in resourcepacks except quark programmer and SE Vanilla Consistency which are generated on pack load.
I have tried removing /resourcepacks from config so nothing loads, and I still get the crash!
crash-2024-02-08_22.27.10-server.txt
latest.log
The text was updated successfully, but these errors were encountered: