Peter Lillington
Comments
Yes, it's not fixed, but at the same time after a few months languishing in bug limbo, we figured out it was never going to get fixed. Onwards and upwards to the next bug! 🙂
Yes, I think this one is confirmed now - though I suspect it's never going to be fixed, too late now for most of us. However - it would be good in 1.9 or something to change the upgrade to properly handle old chests, so that dusty worlds we have hanging about from years ago at least could be upgraded to a new version without corruption.
I changed the title to more accurately reflect the problem - Chest are missing after upgrade from 1.7.x to 1.8, not Beta version to 1.8. The worlds that are affected by the upgrade corruption are a subset - those that were initially created prior to Beta 1.8.
Thanks Gargaj. I wonder if this is something that will get looked at? Probably it's too late now, we've moved on in our MP world, despite missing chests, and I suspect others will have also.
But, should this ever be assigned I'd ask that future upgrades be tested on old worlds - some of us just keep building on what we have from a long time ago!
Hi Kumasasa,
I'm not convinced by that interpretation of Nathan's analysis. The bug appears to be in how 1.8 (specifically 14w26c and later) mishandles worlds first created in Beta 1.7.3 and earlier. If there was a support statement or something that worlds originally generated in Beta 1.7.3 and earlier are not supported on 1.8 or greater, then that would be something (though not great). However, as far as I am aware, that's not Mojang's current position?
Great research, thanks Nathan.
The only thing I would add is that, in my experience, whether pre-beta 1.8 chests make it through the 1.8 update may not necessarily be predicated on whether they went through the beta 1.8 update. My world began in Beta 1.x - 1.3/1.4? I believe we did take this world through Beta 1.8 - I remember the chests reorienting themselves randomly after that update. Of those chests, I'd guess that 60% are now missing - so some survived the 1.8 massacre. 😉
Anyway, it does begin to look like old Beta worlds do not cleanly update to 1.8.
Not sure - all I can say is that this is the first time I've had this problem since the world was initially generated in Beta 1.x. MC 1.4.7 did not cause any problems.
OK, thanks. Should the Status be changed to Reopened?
Hello Kumasasa. The world is uploaded at this link: https://dl.dropboxusercontent.com/u/10365435/world%20-%201.7.9%20before%20update.zip. This is a 1.7.9 world.
Replicate the issue as follows:
Load this world on a 1.7.9 (or 1.7.10) server.
Tp 340 103 21. View chests.
Tp 336 109 21. View water.
Reload this world on a 1.8 server.
Go to the same Tp points - note missing chests and corrupted water feature.
These is only one location I have found with the corrupted water. However, multiple chests are missing in the more central locations of this world after the 1.8 upgrade.
Please can you confirm that you are seeing the same issues I am seeing? Thanks.
I did not upload my world, because I wasn't seeing anybody else had the same problem. Now I do, I'll try to upload it tonight.
Checked two other worlds with old (Alpha/Beta) terrain yesterday, and they appear to be OK, no corruption. So it's possible the corruption is limited to the one world. Will perform one more test tonight.
Yes I can, but not directly, zipped up it is 450Mb. I will try to get it to you later today as a dropbox link.
Further update. I restored the world back to 1.7.9, upgraded the server again to 1.8 (this time going through the 1.7.10 update first in case that was significant). Exact same issue, chests disappear, sections of the world corrupt.
The corruption is weird - as per the second attached picture, not only is some water removed, but the sand is turned to andicite.
I suspect that the 1.8 update was not tested on worlds with old terrain?
First update that parts of the world have disappeared, I consider that a bug. Looks to me similar to this one https://bugs.mojang.com/browse/MC-66631 which apparently was incorrectly assigned as a duplicate of a bug where chests were invisible. To confirm, these chests are not invisible, they are gone.
Additional tidbit - one door was half invisible, required breaking and replacing.
Seems to me that this version is better described as 1.7 was - the Update that Changed the World. 😉
NOGUI option worked for me. Running the GUI: 20-40% CPU with no users. Now purring along at 0-2%, much better.
Win7 x64 9GB RAM Intel Core i7
Ah, right, that's what I gave K9 too. Why do they make you jump through hoops if they're not even interested in fixing the problem?
I have a support ticket in with K9 - jumped through the hoops, wireshark, user initiated BSOD etc. Now waiting for them to get back to me - if I hear more I will report back.
I got a reply - I haven't tested yet but I will let you know once I do (or, if anybody else tries it, please let us know). I think it's probably a generic "upgrade to the latest version" reply, but still...
Thank you for contacting K9 Support. We now have an updated version of K9 available which should address the issues you have been experiencing. You can download the new installer by clicking on this link:
http://www.k9webprotection.com/download/k9-webprotection-beta.exe
Please run the installer, reboot your computer and then try browsing normally. Please let me know if you continue to have your issue, or if you have any other problems.
I'm going to raise this issue with K9.
K9! Wow, I think you are onto something. 3 of my 5 computers have K9, and those computers are affected. I'd give this a very high probability of being the cause, particularly as we'd checked off just about every other option...
I'm curious, I see Mojang have Resolved this issue, marking Resolution as "Done". What was done to fix this one?