Talk:Bedrock Edition level format

mayBuild
Can this be confirmed? In 0.8.1 this attribute is not present in the file, and after adding it, it does not seem to have the desired effect. (I did not write this myself, I only took it out of the page because I think it should not be there but here) --Elike98 talk 14:01, 10 March 2014 (UTC)
 * ''1 or 0 (true/false) - true if the player can place and destroy blocks.

terrain.meta
Should info for the terrain.meta format be added? The file is unique to pocket edition, and could be useful for those adding new textures. It only handles texture UV information used in rendering though, and stores no data from the game. --Jocopa3 (talk) 22:18, 27 July 2014 (UTC)

v0.9.5 Comments
The main page indicates the following: "There's also the special key ~local_player for an entity data entry that holds the local player entity. If entity data exists here, it takes precedence over the player data stored in level.dat."

I believe this needs some clarification. The data contained in the ~local_player entry seems mostly different than the data contained in the level.dat file. The only overlap I've noticed is SpawnX, SpawnY, and SpawnZ.

There is also a special key for remote players which consists of two parts. The first part is the prefix "player_" (without the quotes) and the second part is the client ID which is contained in the remote player's clientid.txt file. Note this client ID was used as the file name for remote player data files in the player directory in earlier versions of MineCraft.

The main page indicates the following: "Entity and tile entity data entries consist of individual entity CompoundTags concatenated together."

I don't believe this is correct. For example the ~local_player entry and remote player entries with the "player_" prefix both only have a single compound tag at the root level. They both contain compound tags at other levels but none of the compound tags are concatenated. Mcpemaniac (talk) 02:28, 10 August 2014 (UTC)