Justin Sullivan
Comments
I encountered this bug too when I played split-screen with a PS4 account signed into PlayStation Network who's primary PS4 did not have legacy console edition. The strange thing was that all of my other accounts signed into my PS4 still have the [Editions] button. It was only my account, the one that played split-screen with the non-legacy console account, that got the button removed.
The first picture is of an unaffected account on my PS4, and the second picture is of my affected account. Both of these screenshots came from the same version of Minecraft, the same day, and the same PS4.
[media][media]Although this is rather late, I would like to provide some more information about this bug, as I know the creator of this report personally. I do not have many details now, but I will provide more when I find out more about the Minecraft world this bug was created in, and how it may have been created.
Notes:
The world actually reverted to a version in 1.14, not 1.13. Although, we do not know the exact version yet.
The world takes up about 695 MB now.
This world was created in the Legacy Console edition, about 4-5 years ago.
The bug was created on version 1.15.0.
When this glitch was noticed, there were still 1.15 blocks placed in the world. They acted like normal blocks, except you were unable to pick block them. If you broke them, there was no way to get it back. There seems to be no more 1.15 blocks in the environment, however.
We have already tried making copies of the world, that does not seem to fix the problem.
No other worlds on this account share the same bug, and Minecraft is updated to the latest version.
The world did not have any issues running. There was no major frame-dropping or frequent lag spikes.
Online multiplayer does work on the world, and the other connected players experience the same version revert glitch. The same goes for split-screen and LAN connection.
The world plays like normal, except it uses the older version.
Reproduction of this Bug:
We are still not sure how this bug was created. Although, I have a few theories to how/why this bug was created.
World corruption. Although I'm not too familiar of this subject, this seems like a viable answer to this problem. Nothing major happened prior to the version revert, however. Flaws: Again, I don't know much about world corruption to be making factual assumptions here, but these are my guesses. The world should not be playable if it is corrupted, unless a very specific thing happened to the world to make it revert a whole update. Also, if world corruption is the case, I do not think this would be classified as a bug. If it isn't, we could still use help to figure out what happened.
The world was too large. At almost 700 MB, it is a big world. Maybe the world takes up too much space, and letting it continue to future updates would override the limit. Flaws: Many people have worlds greater in size than 700 MB, but there is not another report for this bug. There also seems to be enough space, as there have been no warnings about the need for storage. Finally, if the world being to large for the system is the answer, then again, this is not a bug.
Expected Results
I will add on later when I get more information about this bug, but here is the general idea of what should happen. When a player logs into a world, they are unable to access 1.15+ features. Blocks, items, commands, and world generation will not update past 1.14. The menus, marketplace, and other worlds are updated to the latest version. For example, you are unable to spawn bees, or generate new nether terrain, but you are able to change the setting for Spyglass Dampening in the world. This does not affect any aspects of the world, except if you had previously placed 1.15+ items/blocks in the world.
If the developers won't fix a bug, they will mark the status as "RESOLVED" and the resolution as "Won't Fix." An example of this is MCPE-39299. It seems that they have still left the status up as open, meaning they are not actively fixing the bug yet, but they may in the future. All we can do is get everyone that has experienced something like this to vote for this issue and to add more details about it to try to reach a conclusion.