Instability In Version 1.8.0

[no-name-provided]

Modpack

FTB Evolution

Modpack version

1.8.0

Launcher

FTB App

Has the pack been modified

Yes

Log Files

https://gist.github.com/no-name-provided/112fee118a24fbf7acf092dbf4168e30

Describe the bug

Multiple crashes, in multiple worlds, immediately after updating to version 1.8.0. The original two crashes in the original world were a mekanism pipe that couldn't remember where the item in it originated. This resulted in a client hang and a server crash.

The next crash (test world) involved accessing enchantment data before it was loaded, and resulted in a crash to desktop. The next crash (on a recent backup from fixing the bauble deletion bug) was something else. These doesn't seem to have produced crash logs.

The last time I tried to load my main world, I was able to do so. I don't know what's going on, but I figured I should share my crash logs.

Every crash occurred on terrain load.

Steps to reproduce

Not sure yet. Seems to involve porting a world to version 1.8.0 while having a complicated bas (eg, lots of mekanism pipes moving things around).

Expected behaviour

No crash

Screenshots

No response

Additional information

Again, running with AllTheLeaks.

[no-name-provided]

The update apparently reset the connection settings (push/pull/disconnect) on at least one mekanism pipe. This resulted in a bunch of combs bypassing my centrifuge and blocking my input chest. Fortunately, I already had an enormous backlog of most items, and I've already done almost everything resource intensive in the pack.

[no-name-provided]

Correction - perhaps half the logistic transporters connected to blocks from productive bees reset their connection status. No longer pulling from heated centrifuges, inserting into feeding slabs, etc. A whole mess. All in one chunk, so far.

[Gaz492]

So all the crash logs look to have the same error caused by the advanced logistical transporter at -103 69 -22
It's very possible that this has been caused by us needing to downgrade Mekanism between 1.7.0 and 1.8.0 due to a crash that was happening.

I would also hazard a guess that the issues you ran into with the pipes are also caused by the need to downgrade Mekanism.

If you are still running into the crashes, try enabling removeTickingBlockEntity in the neoforge-server.toml.
https://docs.feed-the-beast.com/docs/support/Troubleshooting/ticking-entities
This will remove the advanced logistical transporter thats causing the issue, along with any other block(s) that may be causing issues.

[no-name-provided]

That was going to be my next step. Well, that or rollback the rollback, since I hadn't been experiencing this crash you mentioned. Things seem to have settled down, but I'm still finding the occasional oddity:

Don't know if that's from the rollback or if I somehow gave ownership to a fake player. This was the conduit throwing the error, by the way:

It was (supposed to be) pulling from my electric quarry. This is in a different chunk than the one with the bees, but also had a few reset connections.