Description

This crash occured after a server crash (Crash-Report)，then the server goes crash (with the same crash-report which different with further crash-report) every time and could not start/run, whether set B:removeCrashingItemsOnLoad to true or false.

An'the info might different with crash-report in log file.

Environment

happened on Spongeforge server 1.12.2

• SpongeForge: API-7.1.0-Beta-3064
• Minecraft Version: 1.12.2
• AE2 Version: rv5-s11
• Forge Version: 2655

If any information else needed, I'll provided soon 😅
@yueh

I met the same problem too

first crash has nothing to do with ae, second indicates an broken chunk or a forge bug or maybe sponge, also sponge is not supported and third „me too“ without any additional logs or data is pointless and the opposite of helping

Will close for unsupported environment, if you can reproduce with regular forge, call back with another crash report please

@mindforger However, could your please help me to analysis this exception?

A lots of exceptions mention the appeng.me package, so I'm curious about how's that happened and how can I solve that 😳

As i said the crash involving ae looks like the server returning an invalid blockdata. There is a known issue with forge sometimes derping blockdata which has not been solved yet. It may also be an patch inside sponge that worsen the issue in your case. It would require a lot of work to create an dev env AND reproduce this issue. I am sure the devs won't tackle this until you can reproduce it with forge only. Also i am only a collaborator, i am helping filtering issues that are know, fixed, unfixable or caused by other factors close them and advice where to look for help or trying to help as far es my knowledge goes ... And ae code is intense :)