Java Edition.png
Bedrock Edition.png
Console Edition.png

Java Edition:Bedrock (Item)

From Minecraft Discontinued Features Wiki
Jump to navigation Jump to search
Bedrock.png

Bedrock is intended to be unbreakable and unobtainable, as such it is not normally obtainable in Survival. However, there have been several methods that allow players to obtain Bedrock in survival. Some methods are easy, while others require more complicated setups.

Obtaining

Indev Item Chests

From Indev 20100124-1 to Indev 20100128 new worlds would generate with the Indev House, and inside the house were debug chests. Between Indev 20100124 and Indev 20100125 the chests held items in stacks of 99, while in Indev 20100128 the chests held items in stacks of 100. Bedrock was one of the such items that generated inside the debug chests.

Beta 1.6 Test Build 3 Debug Chests

In Beta 1.6 Test Build 3 new worlds would generate with 11 debug chests. Within the debug chests were a wide variety of items most of which were available in there full stacks some were not. Bedrock was one of the such items that generated inside the debug chests, Bedrock generated in the 1st and 4th chests from the left in the 7th and 18th slots respectively, in stacks of 64.

Enderman Holding Bedrock

In versions Beta 1.8 Pre-release and Beta 1.8 Pre-release 2 ;), the newly introduced enderman could pick up almost any block. This meant that in this version you could obtain an enderman holding bedrock. However, endermen would not drop their blocks when killed in these versions. If you keep the enderman holding bedrock until 15w31a (1.9 snapshot) or later, upon killing the enderman it will drop the bedrock it is holding.

Enderman holding bedrock in Beta 1.8 Pre-release

B Creative

Command Block.png
Warning: Requires Cheats 
This feature requires cheats in some way, which may be dangerous. Perform at your own risk.

In the version 11w49a (1.1 Snapshot), pressing B would toggle the player between Survival and Creative mode. This allowed the player to access the Creative Inventory where the player could then obtain Bedrock.

End Pillar Generation

From 14w18a (a 1.8 snapshot) to 1.8.9, the population of the obsidian pillars in the End dimension could be manipulated in such a way as to allow the obtaining of the bedrock item. This method of obtaining bedrock is difficult and heavily dependent on RNG, but it is the first method for obtaining bedrock in a full release version of the game.

The heart of the method is within the piston extension code. When a piston schedules to extend, two lists are made. First, the list of blocks to destroy (those that are in the way of the moving structure, such as water, torches, leaves, etc.), and secondly the list of blocks to move. These lists are created from the farthest blocks of the structure to the nearest, and executed in that order. After these lists are created, then the game executes those lists. If updates provided from breaking a block early in the break block list cause population, then this population can trigger the placement of an obsidian pillar, and the bedrock block can replace a position within the to break list. When the game reaches that position in the list, the block breaking method is called on the bedrock, allowing it to drop.

The challenge of this method lies in the population of the obsidian pillar, because unlike Overworld population, End population does not set the world's RNG upon population, resulting in the pillar RNG not having the same results in each population. This can easily be seen if you create multiple worlds with the same seed: the pillar generation will be different. This can be mitigated in two ways. Firstly, if chunk savestating is utilized, the player may simply reload the savestate and try multiple times until the RNG succeeds. Secondly, RNG manipulation may be used to determine and predict the values of the End's world RNG.

For more information on this method and survival implementations, see the videos below:

End Crystal Explosion

From 15w44a to 15w51b (1.9 snapshots), bedrock was obtainable via a bug with end crystal explosions and the dragon resummoning sequence[1]. This method is not 100% guaranteed due to the 1/6 chance for blocks blown up by end crystals to drop as an item.

First, the player must remove the bedrock on the top of the pillar and place the end crystal in the bedrock's location. From 15w44a to 15w47c, this may be done easily by using the end crystal on the bedrock block below, which will result in the crystal placing fire into the upper bedrock's location. From 15w48a to 15w51b, another method of bedrock breaking must be used to do so. Next, the player must begin the ender dragon's resummoning sequence using 4 end crystals on the sides. Finally, the player should interrupt the summoning sequence by exploding one of the crystals on the 4 sides. The explosions can be done by punching the end crystals or shooting them with a projectile safely from a distance. It should be noted this method will also work if you kill the ender dragon rather than interrupting the dragon's resummoning sequence or if you put the first end crystal in a location other than the central pillar, as long as the crystal places fire into a location where the exit portal will place bedrock and the explosion of the 4 summoning crystals blows up the 5th crystal as well. Do note that it is quite likely for the bedrock item to fall through one of the end portals and arrive at the Overworld spawn point.

This method is demonstrated in the videos below.

Silk Touch Instant-Mine

This method exploits an oversight in block breaking code that was introduced in 15w31a (1.9 snapshot).

Firstly, the block breaking code stores the blockstate of the block position being mined. This is then used in the calculations of the block breaking percentage. Next, the fire extinguish code is called. Updates chained from the removal of a fire block may be used to update blocks in an invalid state (such as BUD powered rails), and these updates can cause the population of a chunk by loading a 2x2 square of chunks. This can result in the original block being mined to be modified. Then, the game uses the cached blockstate to check how much mining progress was made to break the block. If it could be instant mined, the code to break the block is called. Otherwise, the game increments the block breaking percentage. The code to actually break the block will then use the newly modified block state, allowing one to call the code on any block in the game that is placed from population.

If an instant mineable block (e.g. a slime block) is replaced with world population from the updates chained off of a fire being extinguished such that it places bedrock into the original location, and the player is holding a silk touch pickaxe, the bedrock item will be dropped. Silk Touch is required, as silk touch bypasses the default air drop for the bedrock block.

This method is first possible in 16w39a, with the introduction of the randomly generated gateways in the outer end islands providing a way to place bedrock during population. It was patched in 18w06a (a 1.13 snapshot) due to the rewrite of world generation which prevents population from placing blocks into neighboring chunks.

The main difficulty in this method is getting a player to break blocks close enough to unloaded chunks to allow the population code to be called when the fire is extinguished. This requires using a precise pearl cannon to teleport the player to the edge of loaded chunks, thousands of TNT to lag the game in the right tick phase, and a separate TNT cannon to apply momentum to the player to bypass the vanilla movement anticheat if on a multiplayer connection.

Earthcomputer's video on the main concepts.

Xcom6000's survival method.

Word Tearing and Any Falling Block via Asynchronous Threads

From 14w32a (1.8 snapshot) to 17w46a (1.13 snapshot), asynchronous block updates allow for block palette corruption, and this corruption, when combined with the registry palette type, can allow for the creation of any block that can exist, such as bedrock. Asynchronous block updates also allow for usage of the "generic method" to create a falling block entity of any existing block in your world.

These falling blocks may also be used to obtain their respective item, if it exists in item form, such as end portal frames. Blocks such as end gateways cannot be obtained as items with this method, as they have no corresponding item. Falling blocks also allow for the placement of both blocks that cannot normally be placed, either due to operator restrictions (e.g. command blocks) or not having an item form (e.g. end gateways).


22w13oneBlockAtATime Endermen Spawning

Pink Wither.png
Warning: April Fools' 
This feature requires April Fools' versions which may require file renaming or file deletion to load. See the Loading April Fools' Versions tutorial for more information.

Endermen in the April Fools' version 22w13oneBlockAtATime spawn carrying random blocks. One of these blocks they can spawn with is bedrock. There are 902 different blocks that are equally likely for them to spawn with and so there is a 1/902 = 0.11% chance of the enderman spawning with this block specifically. If the enderman spawns holding a generic_item_block (1/902) there's also a 1/1105 chance it will be this block as its block state, but there's only a 0.0001% chance of this occurring.[2]

In the version, the block can be received from the enderman by angering it then letting it attack the player with an open hand. This will cause the block to transfer into the player's hand. Also, if the enderman dies and the falling block launches from the enderman, this can be picked up by the player. The items can be stored in 22w13oneBlockAtATime by switching the block from carrying to the offhand, shift right-clicking onto a donkey/mule with a chest, and then swapping the item into a slot. Additionally, the enderman carrying the block can be updated and then killed in a later version to obtain the item.

22w13oneBlockAtATime Any Falling Block

Pink Wither.png
Warning: April Fools' 
This feature requires April Fools' versions which may require file renaming or file deletion to load. See the Loading April Fools' Versions tutorial for more information.

Any block can be made a falling block in 22w13oneBlockAtATime using several methods. The bedrock item, if it exists, can be obtained by dropping its falling block onto certain blocks or by picking it up.

Mining in 22w13oBAAT

In the April Fools snapshot 22w13oneblockatatime, the player can directly mine bedrock with no restrictions, but it takes several minutes to do so. Once mined, they can then be either turned into falling blocks, or stored in the inventories of donkeys, mules, or llamas. This can be done by moving the item into the offhand by pressing F, opening the inventory, hovering over a slot, and pressing F again.

It is more efficient to use the dropper or dispenser methods due to the long time it takes to mine.

23w13a_or_b Votes

Pink Wither.png
Warning: April Fools' 
This feature requires April Fools' versions which may require file renaming or file deletion to load. See the Loading April Fools' Versions tutorial for more information.

The April Fool's snapshot 23w13a_or_b introduces a plethora of ways to obtain every block and item in the game, including bedrock. These include:

  1. The egg_free vote, when applied, will allow chickens to lay any block or item in the game (without NBT). This means all chickens have the chance of laying bedrock.
  2. The fish_anything vote, when applied, will allow any item from the creative menu (not the operator tab, with NBT) to be fished (combine with the buff_fishing vote to greatly increase fishing speed). What this means is that there is a chance that bedrock can be randomly fished.
  3. The give_item vote, when applied, will give every online player a random amount of any block or item in the game (without NBT), meaning that you could have bedrock randomly given to you.
  4. The replace_items vote, when applied, will replace all items in online players' inventories with any block or item in the game (NBT of the original replaced item is preserved). This allows for bedrock with Any NBT.
  5. The replace_loot_drop vote, when applied, will replace all loot drops of a random block or item with any block or item in the game (if the original item that is being dropped has NBT, it will be preserved). This is also another method for bedrock with Any NBT.
  6. The replace_recipe_output vote, when applied, will replace all recipes for the given item with any block or item in the game (NBT is preserved if the original output item is supposed to have NBT.) This is yet another method for bedrock with Any NBT.
  7. The villager_gem vote, when applied, will replace all emeralds in all loaded villager's trades with any block or item in the game (without NBT). This means that you can get a villager that trades bedrock, allowing for infinite amounts of bedrock.
  8. The basalt_gen_replace, cobblestone_gen_replace, obsidian_gen_replace, and stone_gen_replace votes, when applied, replace the block of their respective fluid interaction with any block in the game, allowing for blocks in invalid positions and the placement of operator-only blocks such as the Command Block.

See also

References

  1. MC-93119. bugs.mojang.com.
  2. 1/902 * 1/1105 ≈ 0.0001%