The issue does prove elusive in pure vanilla 1.17.1, but is amplified to almost 100% of the time when using the Caves and Cliffs data-pack or modded versions of 1.17.1.
I'm of the impression it's some kind of chunk saving issue, as the same thing happened after a power failure I had, effectively corrupting the world like these bad backups.
That said, I did discover a kind of workaround by compressing the world files.
As a .zip file, the world data seems to back up properly and I have not yet had any issues when these are restored and decompressed, even when an uncompressed version backed up at the same time has been corrupted.
This suggests to me the issue is that Minecraft saves in such a way that Time Machine gets confused, which is not the case for a .zip file as it has a completely different (and more normal) data structure.
Anyway, it would still be nice to have this bug fixed as not only is compressing data regularly quite tedious, each iteration is in effect a new copy of the world and so it hogs quite a bit of space in Time Machine, but yeah.
The Dark Lord
MC-226112
Can confirm for 1.17 as well, and it does appear to be quite a bit worse than in 1.16.5.
Anyone know any tricks or workarounds?
The issue does prove elusive in pure vanilla 1.17.1, but is amplified to almost 100% of the time when using the Caves and Cliffs data-pack or modded versions of 1.17.1.
I'm of the impression it's some kind of chunk saving issue, as the same thing happened after a power failure I had, effectively corrupting the world like these bad backups.
That said, I did discover a kind of workaround by compressing the world files.
As a .zip file, the world data seems to back up properly and I have not yet had any issues when these are restored and decompressed, even when an uncompressed version backed up at the same time has been corrupted.
This suggests to me the issue is that Minecraft saves in such a way that Time Machine gets confused, which is not the case for a .zip file as it has a completely different (and more normal) data structure.
Anyway, it would still be nice to have this bug fixed as not only is compressing data regularly quite tedious, each iteration is in effect a new copy of the world and so it hogs quite a bit of space in Time Machine, but yeah.