I believe that the first time this occurred I even got "stack overflow" error when I was kicked. I changed the max-tick-time to 6 mins (300000) and the same happened.
The wiki says that this doesn't happen in both singleplayer and multiplayer because of the change. It doesn't say it was intended in any way.
U can change it by changing the
"default_block": {
{{ "Name": "minecraft:stone"}}
{{ }, }}
in the generator settings
ok, thanks 🙂
I hope that a link to Google Drive will be ok, I packed the whole server folder and it's a little more than 100 MB. The world included is vanilla 1.17, made without datapacks, trimmed by mca-selector. In the datapack folder I've just added a 1.18 datapack named "wielipack" which mainly changes the lower bound of the world to -128. Steps to reproduce:
in that folder: java -jar server.jar (port is set to 25566)
wait till the server is loaded
log in on some account (set render distance to 22)
tp player 1000 100 2000 (these are the exact coords where this happens)
don't move, wait half a minute, though you can rotate yourself to see how the world loads
after half a minute server becomes unresponsive and eventually crashes
https://drive.google.com/file/d/1bSQClEHpYnRSmFi_ERrNiqWqVkrdVJVc/view?usp=sharing