Greetings, I did not realize there was an expiration on the link.
Uploaded again - same digest as before; filesize of the tar is showing for me 374251708 bytes; download link : https://we.tl/t-EEyOfh85lF
Â
Sounds like a breakthrough finding the corrupted data 🙂
I'm reading up on how to optimize the world, will try that when able.
I just noticed you mentioned I can provide the world download - much easier. Link for world download :Â https://we.tl/t-JsEmBiWXzv - this is the backup I referred to from 4 days ago. I updated the spawn point to get closer to the village area itself.
In case it's needed, I would xz -d <file.tar.gz.xz>
then usual tar xf <file.tar.gz>
digest:
# SHA256 HASH
c3ca4345b2d1139186a81503eb95c723a5d460909dfa4c9f0fa2d04a7ce8c46c mc-server-debug.seed-2952352923753510649.20w15a.coord_-9713.011_74_10230.008.tar.gz.xz
# WHIRLPOOL HASH
14bda8c01db769c75e1425233ed7d14a949d4086c18ea56232e8663823cd04c9759c235f43fb7ef4e9db2ef7f53c667751763537a2aba2ff72d36b2b4ced4d79 mc-server-debug.seed-2952352923753510649.20w15a.coord_-9713.011_74_10230.008.tar.gz.xz
I will attempt to replicate and return with results - I didn't extend beyond mixing running server versions 1.15.2, 20w06a, 20w13b, 20w14a, and 20w15a.
Can confirm - re-building world seed 2952352923753510649 with latest snapshot 20w15a did not present the issue. Maybe helpful information to attempt replicating issue: The world was built and run with version 1.15.2, then followed by running with 20w06a, 20w13b, 20w14a, and 20w15a but I imagine since latest snapshot alone does not repeat the issue I would think it's been fixed. Perhaps just a glitch in transitioning between versions.
It is pure vanilla - so far nothing extra added or removed. I deleted the `world` directory and just now re-building the world under snapshot `20w15a`.
Ah yes, forgot that part - originally this was built in version `1.15.2`.
Added also
[media]while standing in the darkened area instead of next to it like
[media]New screenshot uploaded as file
[media] with debug screen enabled. Thankfully I had a slightly older copy of the server - sort of instinctively I ran inside the building and put a torch in the dark area and that pretty much resolved the bug - then I removed the torch. After restarts and a few game-day cycles it retained the fix after placing and removing the torch.
Commenting to advise this has happened when transitioning from 1.15.2 to 1.16 (20w06a). Removing a previously /op'd player from operator status appears to have restored the ability to break blocks.
Sorry i took a while for me to confirm - finally got to optimizing the world 🙂
I'd like to move this ticket to resolved.
In my search for how to optimize a world I found another ticket referencing this fix:Â MC-142134S6
`java -jar ./bin/20w15a/minecraft_server.20w15a.jar bin/20w15a --forceUpgrade --eraseCache` [solved] the issue.
Another reference I found regarding world optimization was @Â https://www.reddit.com/r/Minecraft/comments/bmqsv3/fixing_server_world/
I was curious whether the Java version would be a defining factor as well but I ultimately don't know - I figured newer versions would still have backwards compatibility.
Many thanks for everyone's support here.