Minecraft restore causing chunk errors

  • Last Post 2 weeks ago
Wrayzor posted this 2 weeks ago

Hi, I have started a new Minecraft world and after playing for a short time, wanted to do a restore from the last backup. I have a 30 min scheduled backup setup and they seem to be running. When I did a restore and started playing, I notice a weird/misplaced chunk and checked my amp log. It seems when my user logged in, it caused some chunks to move/error. it did not happen on server boot, only after a user logged in, I tested two accounts.

Server thread/ERROR 13:43:16
Chunk file at [80, -27]: is in the wrong location; relocating. (Expected [80, -27], got [65, -24])
Server thread/WARN 13:43:17
Wrong location! (65, -24) should be (80, -27), bap['Sheep'/174, l='ServerLevel[world]', x=1041.20, y=88.00, z=-376.50]
Server thread/ERROR 13:43:18
Chunk file at [55, -23]: is in the wrong location; relocating. (Expected [55, -23], got [55, -22])
Chunk file at [55, -22]: is in the wrong location; relocating. (Expected [55, -22], got [55, -21])

I restored the backup from 30 mins before this the "latest one" and was able to log in and saw no chuck errors in the log,

I have created a couple worlds to test this and almost every time it seems to be getting chuck errors on restore. I also encountered this issue on the last release. Any Ideas? Let me know what settings/info you need. Thanks

OS  Linux
Platform    Ubuntu 20.04.1 LTS
System Type x86_64
Virtualization  None
Module  MinecraftModule
Loaded Plugins  FileManagerPlugin, EmailSenderPlugin, WebRequestPlugin, LocalFileBackupPlugin, CommonCorePlugin
Application Name    AMP
Application Version
Release Stream  Release
Build Date  03/09/2020 11:37
InstanceID  542351d4-e07b-46b4-80b7-5459d895cabd
Last Executable /usr/bin/java
Last Arguments  -Xmx1024M -Xms1024M -jar minecraft_server.jar nogui

Mike posted this 2 weeks ago

Try deleting the existing world (take another backup first) before restoring a backup over the top of it. This isn't really something we can help with though as it's in-game behaviour rather than something AMP controls.