Long tick crash via ServerHangWatchdog when near a particular chunk
I run a popular DawnCraft (1.23 on MC1.18.2) server (yay) and it's been running fine (broadly) for a month or so.
Today, however, a player has created what I can only describe as a "bad chunk". It is his base, but it causes the ServerHangWatchdog long server tick error if anyone goes near it. I downloaded the world into SP and systematically tore it down, but I cannot find the issue block/machine/item, it continually crashes even in SP. The logs give very little information.
Does anyone have any experience of how to correct this? At the moment it feels like I have a crashable zone on my server than anyone can go wandering near. I, rather unfortunately, spawn next to this chunk because of my investigations and that causes me to crash the server whenever I go near it.
(I have got MCA and I was going to reset the chunks as an absolute last resort because this is someone's base that they've spent ages on)
Your help is greatly appreciated ❤️
5 Replies
Thanks for asking your question!
Once you have finished, please close your thread.
Make sure to provide as much helpful information as possible such as logs/what you tried and what your exact issue is
command to close
/close
!close
!solved
Requested by .dooburt#0
If it's somebody's base there is likely something saved in that chunk causing problems.
IE a storage array that's gotten far too large
Think book banning but slightly different
Thanks Senor, how best to identify which "thing" is causing the problem - like the storage array for example?
You'd have to manually inspect the chunk data itself. Not too many people know how to actually do that. The general recommendation is to load a backup or delete the chunk
Ok ,so I can open the chunks in question in an NBT editor - and I can see lots of data - but what would I actually be looking for to know something had got to large or gone bad?
To give context, he has 1187 placedPos entries in just a single chunk and I have 24 chunks that could potentially contain the "nasty"