User:JEC6789/Downgrading

In Minecraft, downgrading refers to reverting to an older version of the game.

Users may need to downgrade as newer versions drop support for older hardware. For example, dropped support for systems using  microprocessors, so anyone using them would have to downgrade to  to continue playing the game. Certain Minecraft servers may also downgrade due to technical changes in later versions that break the server software they use, such as the addition of block states in or "The Flattening" in.

$$, downgrading can generally be done through the Minecraft Launcher's backwards compatibility feature. For versions not available via the launcher, links to download the client and server may be available on their respective version pages on this wiki.

$$, downgrading can be done by uninstalling the current version and searching for, downloading, and installing an unedited of an older version online.

Issues
Since older versions of the game are not supported by Mojang, any issues associated with downgrading will not get fixed.

Bedrock Edition

 * If the player places down a block and then downgrades to a version where it does not exist, it will get replaced with an info_update2 block. Updating back to a version where it does exist will not change it back to its original form.
 * Since info_update blocks did not exist before Android v0.2.0/iOS v0.1.3, the game would simply crash instead once any chunks that had invalid block IDs got loaded in.
 * If the player saves a world under certain conditions in v0.2.0 or later and then loads in the world in v0.1.3 or earlier, the player gets moved to an extremely high Y-level. This is so far confirmed to happen under the following conditions:
 * The world is saved while the player is flying.
 * The game mode is Survival.
 * If the player gets an item in Survival mode and then downgrades to a version where it does not have an item form, it will permanently disappear from their inventory.
 * If any options are changed in v0.7.0 or later and the user downgrades to v0.6.1 or earlier, all the settings will get reset. This is due to a different method of setting storage being used instead of options.txt.
 * Downgrading to another version from any pre-0.7.0 version will also reset all settings. This is likely due to the settings being stored directly in the game itself instead of in the separate com.mojang folder.
 * Since downgrading does not delete the options.txt file, updating back to v0.7.0 or later will change the settings based on what is in it.
 * If a world is loaded in v0.9.0 (build 1) or later and is then loaded in v0.8.1 or earlier, its save gets corrupted and generates a new world with the same seed. This is due to later versions using the LevelDB level format, which is not compatible with earlier versions. Any blocks and items in the inventory with a valid ID are still saved.
 * Since the player's Y-level is also still saved, this can potentially result in terrain spawning inside the player and causing suffocation, especially if a flat world gets downgraded.