Also getting this issue, nothing seems to resolve it, all the "fixes" seem to do is just waste time whilst it sorts itself out. I would really like to know something is being done about this, as my friend is not paying for a Realms server for it to be inaccessible when it is supposed to be available 24/7
First, check to see if multiplayer is on, in the settings of the world. Second, this has happened to me before, and it is a glitch that sometimes fixes itself when I reload the world, you might wanna try that.
Thanks for looking into this Kumasasa. I just loaded up that world and I can verify that chunk -74, 17 is now identical to -76, 15. Thankfully I make regular backups of my Minecraft worlds so I will be able to correct the chunk in question with my backup. (Proves the importance of making regular backups). Goodnight and keep up the good work 🙂
Here are all of my minecraft logs that were made since the last backup of my world was made. I am 99% sure that the issue occurred today (2015-03-03) so those logs are probably the best place to look.
Jack Walker
Also getting this issue, nothing seems to resolve it, all the "fixes" seem to do is just waste time whilst it sorts itself out. I would really like to know something is being done about this, as my friend is not paying for a Realms server for it to be inaccessible when it is supposed to be available 24/7
First, check to see if multiplayer is on, in the settings of the world. Second, this has happened to me before, and it is a glitch that sometimes fixes itself when I reload the world, you might wanna try that.
Thanks for looking into this Kumasasa.
I just loaded up that world and I can verify that chunk -74, 17 is now identical to -76, 15.
Thankfully I make regular backups of my Minecraft worlds so I will be able to correct the chunk in question with my backup. (Proves the importance of making regular backups).
Goodnight and keep up the good work 🙂
Here are all of my minecraft logs that were made since the last backup of my world was made. I am 99% sure that the issue occurred today (2015-03-03) so those logs are probably the best place to look.