User:FireX420

Also known as JEC6789 on the non-discontinued Minecraft Wiki. Overly obsessed with early Pocket Edition versions since 2021.

= Dumping grounds = As far as I can tell, there's currently no guidelines dictating what you can put on a user page on this wiki. So I've decided to put a data dumping section here similar to my blue sandbox on the Minecraft Wiki for information I don't see being successfully incorporated on any pages over there. Feel free to edit anything in this section.

How far is too far? (Pocket Edition)
Everyone always asks if you can safely update from version #1 to version #2, but what about updating from version #1 to version #6,478? Let's talk about that.

Summary
See Java Edition:Potentially Dangerous Versions for danger definitions.

In Pocket Edition v0.1.x alpha, the  file used a compact binary format instead of the NBT format. The file contained information for the world seed, the last played time, and the world name. Player information was stored in a separate file named. Additional information regarding the level format in these versions can be found here.

Before v0.2.0 alpha, all the different colors of wool were split up into their own numeric IDs since the player's inventory did not support metadata values at the time. With the addition of inventory metadata support in v0.2.0, all wool colors were merged into a single numeric ID, with different colors corresponding to different metadata values. If the player updates to v0.2.0 only, any pre-0.2.0 wool blocks are automatically converted to the new wool ID. The game's ability to convert wool was removed in v0.2.1, resulting in potential block damage if the player updates from v0.1.3 or earlier to v0.2.1 or later.

In v0.2.0 alpha, level.dat was changed to use the NBT format, and player information that was previously in player.dat was moved into level.dat. The game automatically converts the level.dat file for a given world once the world is opened in-game.

Outside of the addition of a few fields in level.dat and the addition of  in v0.5.0 alpha, no changes were made to the level format until v0.9.0 alpha build 1. This means that worlds can be safely updated from v0.1.x straight to v0.8.1.

v0.9.0 introduced a large number of changes to the level format, including the addition of the  folder, the removal of the player tag from level.dat, and the removal of   and. While this version does support updating to it from as far back as v0.2.0, the different level.dat format and the existence of player.dat in v0.1.x does cause a number of issues to occur if updating from v0.1.x to v0.9.0.

In v0.9.0, information concerning the player, such as their position and inventory, was moved from level.dat to the db folder. To allow players to update to this version from previous versions without any issues, player data is still able to be read from level.dat if it cannot be read from the db folder. However, starting in v0.10.0 (build 1), the game is no longer able to read player data from level.dat under any circumstances. As a result, if the player updates from v0.8.1 to v0.10.0 while skipping v0.9.x, they will lose all items in their inventory, including any equipped armor.

Updating from v0.1.x to v0.9.0 or later
Opening a world in v0.9.0 or later that was last opened in v0.1.x presents the following glitches: Opening a world in v0.11.0 or later that was last opened in v0.1.x also presents the following glitches:
 * The world type is automatically converted from old to infinite. New chunks generate in place of the invisible bedrock border.
 * Chunks outside the old world bounds may sporadically fail to generate, which can result in any of the following three outcomes:
 * An empty chunk
 * A copy of the northwest-most chunk from the old world
 * A corrupted copy of the northwest-most chunk from the old world that crashes the game when it is loaded in. If the player is able to get close enough to such a chunk, the world can potentially get softlocked.
 * If the players opens the world in v0.10.1 or later, loading these chunks does not crash the game. These corrupted chunk copies are shifted down 21 blocks on the Y-axis and contain a large assortment of seemingly unrelated blocks on their two westernmost rows. Being near these chunks for long enough can still crash the game.
 * Chunks inside the old world bounds may regenerate while still in-game, resulting in glitchy rendering until the player either exits and reenters the world, or unloads and loads the chunk(s) back in.
 * The world no longer has a displayed name on the world selection screen, and its last played time before opening it is displayed as "long ago."
 * The light level of all blocks excluding those that give off light in the old world bounds is zero as long as they do not receive any block updates.