-
Bug
-
Resolution: Invalid
-
None
-
1.19.40
-
None
-
Community Consensus
-
Xbox
-
949556
A while back, my friend and I found out that our Minecraft world reverted from 1.15.0 to 1.14.?. As of today, the world is still stuck on 1.14.? without many clues as to why. ** As of now (1.19.40 on 2nd of November, 2022), the bug is still affecting this single world.
Notes:
- The world takes up about 695 MB now.
- This world was created in the Legacy Console edition, about 4-5 years ago. The world was converted shortly after the "Better Together" update.
- The bug occurred on version 1.15.0, and is still ongoing.
- When this glitch occurred, 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. Commands do not work either.
- 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 (1.19.40).
- The world did not have any issues running. There were no major frame-drops 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. Before connecting the world, it says the world is running on the latest version.
- The world plays like normal, except it uses the older version.
- Strangely, any name changes to blocks or items from 1.15+ are shown in the world, such as the "Spawn Zombified Piglin" instead of "Spawn Zombie Pigman," suggesting that the current language features do prevail in the world. It still uses the old zombie pigman model.
Observed Behavior:
- All blocks, items, mobs, and commands that were added post-1.14 are not present.
- 1.15+ items cannot be given to the player through the creative inventory nor can they be given through commands (the screenshot shows the lack of 1.15+ items).
- 1.15+ mobs cannot be summoned through commands (such as bees).
- 1.15+ textures are not present (such as the new ore textures).
- 1.18+ height limit extensions are not present.
- 1.15+ language features (such as item names) are present.
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. 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 something 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 large world. Maybe the world takes up too much space, and letting it continue to future updates would override a 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 storage space on the Xbox, as there have been no warnings about the need for storage.
Expected Results
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.
The screenshots are not great, but I recorded a video earlier today and I took a few screenshots from it. All of these screenshots were taken the 2nd of November, 2022. One shows the original zombie piglin model, another shows the glitched creative menu, and the other shows the spawn egg named "Spawn Zombified Piglin," despite it spawning the old zombie pigman. Note that these screenshots were taken from my PS4 when remotely connecting to the world, but the same problems are seen on all versions.
![]()
![]()
![]()