Talk:Reserved6

This looks fake... It only supplies two images, and both are examples. Can someone make video proof? Pokechu22 22:34, 25 April 2013 (UTC)

I can confirm that .name is still present in 0.7.1. Try editing it in with PocketInvEditor, for example. Http500 07:36, 9 June 2013 (UTC)

I'm not fake! :( -tile.reserved6.name- (talk) 19:30, 15 May 2024 (UTC)

Anyways, I've edited this post for it. -tile.reserved6.name- (talk) 19:41, 15 May 2024 (UTC)

wait hold on!!!!!!! no I'm late!!!!!!!! -tile.reserved6.name- (talk) 19:58, 15 May 2024 (UTC)

If you for SOME reason are viewing this, it's very laggy. Don't blame it on me, you should blame it on poor quality screen recorders. Bandicam doesn't seem to go well with MC-Wiki Media Upload Files... -tile.reserved6.name- (talk) 00:20, 16 May 2024 (UTC)

Use of interrobangs and ellipsis, no consistent grammar, injections of opinions, advocating for add-ons(?). This article is an absolute mess.

I'm a Java player, so I don't know much about Reserved6, but if anyone knows literally anything about it, please help clean this up.

--👁 Image
DigiDuncan! (talk) 00:44, 19 June 2020 (UTC)

Versions downloaded/tested: 0.3.2 – 0.7.0
So I was just taking some cleanup shears to this page like I would to any other one last night, and once I had pretty much finished up my cleaning up, I had a strange feeling. The non-cleaned version implies that fire, with an ID of 51, got replaced with this reserved6 block, with an ID of 255, in 0.3.3; and in 0.7.0, any reserved6's were still reserved6's and did not get changed back to fire. I kinda just felt like that info didn't add up. So I decided to hop into 0.3.2, generate over 25 worlds just so I could find lava, and figure out what actually happened with the removal of fire. Here's the results of all of my testing:

• For Mushroom § History: in 0.3.2, mushrooms appeared to ignore light levels upon initial generation and could spawn pretty much anywhere. This was not the case when I first started playing Minecraft in 0.7.1, which means this got changed at some point between the two versions.
• For Leaves § History: in 0.3.2, spruce leaves had a glitched crafting table texture when held in the player's hand. It looked like this, but without the green tint. The linked page has a history item from an unknown version, and based on my mentioned in-game observation as well as what I've found this wiki, 0.3.0 and 0.3.2 are both versions in which this glitch and that history item occured, with earlier versions not being out of the question.
• For Fire § History: fire was indeed invisible in all versions before 0.7.0.

Now on to reserved6:

• In 0.3.3, fire did NOT get replaced by reserved6, or at least not a block with a stone texture. Any fire that was already in a world would still emit light and light mobs on fire, but would no longer spread or burn anything up.
• In 0.7.0, the fire from 0.3.2 and 0.3.3 once again behaved like fire and used the fire texture.

If you want to test any of this out yourself, the seed "shit" has a lava spring you can use to create fire. If I didn't screw up any of my testing, this would mean reserved6 never served as a placeholder block for fire, making its true purpose unknown. Since my testing doesn't change the fact that the game's code directly linked reserved6 to fire, here's the conclusion I have come to about reserved6:

In 0.3.3, reserved6 did not replace existing fire blocks in a world. It instead inherited fire's spreading mechanics until they could get fixed in 0.7.0.

My conclusion is obviously complete conjecture, and I have no way of testing it out at all, but that's what would make the most sense to me, especially since this forum user found reserved6 to be extremely glitchy in 0.5.0. What are y'alls thoughts on this?
– JEC _talk 18:17, 23 January 2021 (UTC)

Turns out, it has nothing to do with fire. Reserved6 is actually used to hold empty inventory slots. You can tell this by opening the level.dat in an inventory editor, and checking the empty slots. They are all labeled as reserved, with an id of 255 and a count of -1. Presumably this was a change implemented in order to allow inventory reorganizing of some sort, or perhaps offer easy pointers within the inventory. Reserved6 has a fluctuating damage value that corresponds to something, my guess is maybe it refers to a position inside the inventory. My educated guess is that the 9 slots with reserved6 each have a damage value that refers to a specific inventory slot, in order for a hotbar slot to match to an inventory slot.

Not only is the purpose wrong, but the history is wrong too on this page. It was not added in 0.3.3, it was actually added in at least 0.2.0. There is of course a chance it was added in 0.1.0, but there is no good way to check versions prior to 0.2.0.

I have to guess that upon discovery of the block, nobody truly knew what reserved6 was, so they simply drew correlations with some other random change. I am curious to find out where this rumor originated, considering it is such a variance from the actual purpose.

Sl1mJ1m4 (talk) 17:55, 4 January 2023 (UTC)