Server crashes after nearing certain position, because of faulty NBT Data

[Semetix]

Your GTNH Discord Username

Semetix

Your Pack Version

2.7.2

Your Server

Private Server

Java Version

Java 21

Type of Server

Don't know

Your Expectation

That it does not crash

The Reality

https://mclo.gs/qtXTOGf
It crashes as soon we near the node

Your Proposal

To not crash

Final Checklist

• I have searched this issue tracker and there is nothing similar already. Posting on a closed issue saying the bug still exists will prompt us to investigate and reopen it once we confirm your report.
• I can reproduce this problem consistently by follow the exact steps I described above, or this does not need reproducing, e.g. recipe loophole.
• I have asked other people and they confirm they also have this problem by follow the exact steps I described above, or this does not need reproducing, e.g. recipe loophole.

[Semetix]

Its probably not a node, its something below the surface

[Semetix]

We found out its something at a certain coordinate. If are near it Server crashes, and we need to rollback. Its not possible to login then.

[Semetix]

https://mclo.gs/9AKpG5h

[Flanisch]

This looks like chunk corruption to me. Is this inside your base or somewhere different?

[Semetix]

It is near my base, like 500m away

[Flanisch]

Then I can recommend you identify the chunk that's causing you to crash and use mcaselector to delete it. If you then load the chunk again, it will regenerate and you won't crash anymore ^^
Please make a backup of your world before using mcaselector though :)

[Semetix]

Well I tried MCASelector earlier and the world did not load or the application crashed. Can it be that my world is really big and it needs a lot of time to load?

Is GTNH supported? Do I need a different version or is the latest ok?

[Flanisch]

I used mcaselector before on a gtnh world. From experience it takes some time to load. I can take a look at it, when I'm home.

[Semetix]

That would be very helpful. Whats your dc?