Enigmatica 2: Expert - E2E

Enigmatica 2: Expert - E2E

2M Downloads

Crash on World Load

Kirby1844 opened this issue · 9 comments

commented

Modpack version
1.58

Can the issue be reproduced?
Yes, every time I start up a world.

Logs
https://pastebin.com/Ex7tA9Zp

Issue
So, uh, every time I start up a world now, the game just quickly goes to "shutting down internal server" before I have the chance to make any input, and then, after about 30 seconds, just disappears, and I'm back at the Minecraft launcher, which tells me there was an unexpected error. Now, I'm not the best at this, so I might be missing something. Oh, and also, I looked at the crash log, and while I'm not sure, it looks like it has something to do with Dank Null rendering.

Thanks for the help! I hope you have a nice day!

commented

Do you have any idea what items were inside that /dank/null? And does removing the dank null with an NBT editor (or alternatively deleting your playerdata file entirely) fix the issue?

commented

On the first point: yes and no. I have four dank nulls in my inventory, one contains mining junk, another, building blocks, another, mob drops, and the fourth has crop harvests.

I'll have to look into a NBT editor/playerdata file, since that's a little beyond my knowledge right now.

commented

That config would not help in this case unfortunately, as it's not an entity that's causing the crash.

commented
commented

@Kirby1844 could you maybe send me your playerdata file? This way I could see what exactly is inside the /dank/nulls

commented

https://drive.google.com/file/d/1q6aKo3U5rEtcH8YrqZwHKRRo9L-PE_3E/view?usp=sharing
Sure! I made an attempt on a different copy, thought it would be the Danknull with the architecturecraft items and thaumcraft lamps, but no, apparently not.

Google Docs
commented

That's your Cyclic inventory, isn't the /dank/null that's causing the crash in your main one?

commented
commented

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.