Minecraft:Block properties

Block properties control how different Minecraft:block types interact with various gameplay Minecraft:mechanics. While some block behaviors are specific to individual block types, such as the ability to open a Minecraft:chest or activate a Minecraft:lever, block properties specify how blocks behave in response to interactions that can occur with any block. For example, Minecraft:fire may attempt to spread to any nearby block, in which case the Minecraft:flammable block property is used to determine if the spread succeeds. Similarly, a Minecraft:piston may attempt to push any block, and the Minecraft:push reaction block property is used to determine if the push succeeds, fails, or destroys the block.

For the most part, block properties are really properties of block types, not properties of individual blocks. For example, if a given block is Minecraft:flammable, all blocks of the same type will be as well. However, the values of some block properties can vary depending on the given Minecraft:block state—for example, Minecraft:fence gates are Minecraft:collidable when closed, but not when open.

List of properties

Solid

The legacy solid block property, usually just called solid, determines if a block is considered "solid" for a number of game mechanics. It is distinct from many other notions of solidity, such as whether the block is Minecraft:opaque, Minecraft:conductive, Minecraft:collidable, is a Minecraft:full block, or allows Minecraft:mob spawning. A slight variant of the legacy solid property is known as blocks motion for historical reasons, though it is also unrelated to whether or not a block is collidable.

Many gameplay mechanics are affected by the legacy solid property, including support for certain attached blocks like Minecraft:candles, conversion of Minecraft:farmland to Minecraft:dirt, destruction of Minecraft:cactus, summoning of Minecraft:iron golems, and Minecraft:pathfinding. Additionally, the blocks motion property influences random Minecraft:teleportation and certain Minecraft:fluid mechanics.

Collidable

The collidable block property determines whether or not a given Minecraft:block has a Minecraft:collision box that Minecraft:players, Minecraft:mobs, or other Minecraft:entities cannot move through. It is distinct from whether or not the block is considered solid or Minecraft:movement-blocking for certain other gameplay mechanics. Most blocks are collidable, but the following blocks are not:<ref>https://joakimthorsen.github.io/MCPropertyEncyclopedia/?selection=has_collision&filter=(has_collision:Yes)</ref>

Conductive

The conductive block property determines whether a given Minecraft:block can conduct Minecraft:redstone signals when Minecraft:powered by Minecraft:redstone components. For historical reasons, conductive blocks are often called solid or opaque and non-conductive blocks are often called transparent, but conductivity is separate from whether a block is considered solid, Minecraft:collidable, or Minecraft:opaque.

As a rule of thumb, Minecraft:opaque Minecraft:full blocks (like Minecraft:stone) tend to be conductive while partial blocks (like Minecraft:slabs) or Minecraft:transparent blocks (like Minecraft:glass) tend to be non-conductive. However, there are numerous exceptions. For example, Minecraft:glowstone and Minecraft:observers are not conductive despite being opaque Minecraft:full blocks, while Minecraft:mud and Minecraft:soul sand are conductive despite not being full blocks.

Valid spawn

The valid spawn block property determines whether ordinary Minecraft:mobs can spawn on top of a given Minecraft:block (assuming their other spawn conditions are met).

As a rule of thumb, blocks with a full, solid top face tend to allow mob spawning while other blocks tend not to. For example most Minecraft:full blocks allow mob spawning, as do upside-down Minecraft:stairs and Minecraft:azaleas, as their top face is solid and spans the entire block. However, there are numerous exceptions. For example, mobs cannot spawn on Minecraft:glass or Minecraft:bedrock even though they are full blocks, and mobs can spawn on Minecraft:soul sand even though it is not. A full list is given below.

Block	Valid spawn?<ref>https://joakimthorsen.github.io/MCPropertyEncyclopedia/?selection=spawnable</ref>
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockSpriteTemplate:BlockSpriteTemplate:BlockSpriteTemplate:BlockSprite Minecraft:Crops	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc
Template:BlockLink	Template:Tc

Flammability

Three related block properties determine how Minecraft:fire spreads to and interacts with other Minecraft:blocks:

• The ignite odds property controls how quickly a block catches fire if nearby Minecraft:fire is available to spread there.

• The burn odds property controls how quickly a block that is currently on fire burns away.

• The ignited by lava property determines whether or not nearby Minecraft:lava can cause the block to catch fire.

The word flammable is often used to describe blocks capable of burning away—that is, blocks that have burn odds greater than zero—but it is also sometimes used to describe blocks capable of catching fire at all.

Some blocks can be ignited by fire but not by lava and vice versa. For example, Minecraft:hay bales can be ignited by fire but not by lava, while Minecraft:mushroom blocks are ignited by lava but cannot be ignited by nearby fire. Blocks in the latter category never burn away, and they usually extinguish themselves quickly. The only exceptions are blocks that burn forever, such as Minecraft:netherrack and Minecraft:soul sand.

Replaceable

Template:Info needed section If a Minecraft:block has the replaceable block property, blocks placed on, against, or in the same location as the replaceable block replace it rather than being placed on or against it. For example, placing a block on a block containing Minecraft:short grass replaces the grass with the block. Most blocks are not replaceable, but the following blocks are:<ref>https://joakimthorsen.github.io/MCPropertyEncyclopedia/?selection=replaceable</ref>

The replaceable block property is also used by a few other game mechanics:

• Minecraft:Falling blocks that fall onto replaceable blocks replace them.
• Minecraft:Huge fungi may replace replaceable blocks when generated or grown.
• Minecraft:Nether portals may replace replaceable blocks when generated.
• Minecraft:Cobwebs spawned by the Minecraft:weaving effect may replace replaceable blocks.

Suffocates

The suffocates block property determines whether an entity Minecraft:suffocates if its head is inside a block.

Usually, blocks are suffocating if and only if they are Minecraft:full blocks that also Minecraft:block motion. For example, Minecraft:stone suffocates mobs, but Minecraft:slabs do not (because they are not full blocks), and neither do Minecraft:chorus flowers (because they are not considered motion-blocking). However, there are some exceptions:

• Minecraft:Copper grates, Minecraft:glass, Minecraft:stained glass, Minecraft:tinted glass, Minecraft:leaves, and Minecraft:mangrove roots do not suffocate mobs despite being motion-blocking full blocks.

• Minecraft:Dirt path, Minecraft:farmland, Minecraft:mud, and Minecraft:soul sand suffocate mobs despite not being full blocks.

Blocks vision

The blocks vision block property determines whether the player can see while their head is inside a Minecraft:block. If a block is vision-blocking, the player's screen is obscured by a darkened version of the block's texture if their head is inside the block.

Almost all blocks that are suffocating are also vision-blocking and vice versa. However, there are a few exceptions:

• Minecraft:Snow blocks vision if it is 8 layers tall, but it never suffocates.

• Minecraft:Trial spawners and Minecraft:vaults do not block vision but do suffocate.

Push reaction

The push reaction block property determines what happens when a Minecraft:piston attempts to push or pull a Minecraft:block. It has four possible values:

• normal: The block can be pushed and pulled by pistons.
• push_only: The block can be pushed by pistons but cannot be pulled.
• destroy: The block breaks when pushed and cannot be pulled.
• block: The block cannot be pushed or pulled. If a piston must push the block to extend, the attempt to extend fails.

If a block's push reaction is anything other than normal, the block also does not stick to Minecraft:slime blocks or Minecraft:honey blocks.

Relationship between solid, opaque, and similar properties

There is no single property that determines if a Minecraft:block is a "solid block" for all gameplay mechanics. As such, the words solid, opaque, and transparent are colloquially applied to several different block properties, which can cause confusion. Much of this confusion stems from the fact that earlier versions of Minecraft used a single property to determine which blocks were Minecraft:opaque, Minecraft:conductive, caused Minecraft:suffocation, or allowed Minecraft:mob spawning, so the words solid and opaque were (and often still are) used synonymously to refer to all three.

Further confusing matters, although contemporary versions of Minecraft use distinct block properties to control distinct behaviors, the behavior of many blocks added in earlier versions has been intentionally preserved. This can result in surprising inconsistencies and exceptions with no intuitive explanation. For example, mobs cannot spawn on or suffocate inside Minecraft:glass blocks even though they are Minecraft:full blocks. This can create the mistaken impression that mobs cannot spawn on any block that is not fully Minecraft:opaque, but in fact mobs may spawn on top Minecraft:slabs, upside-down Minecraft:stairs, Minecraft:azaleas, Minecraft:slime blocks, and many other transparent blocks.

Furthermore, even if explicit terms like opaque, conductive, and valid spawn are used instead of the catch-all term solid, some game mechanics do depend on whether a block is considered "solid" in a more conventional sense, and several different mechanisms are used to make that determination even within that category:

• Some mechanics, such as Minecraft:enderman teleportation, determine whether a block is solid using the Minecraft:legacy solid block property.

• Other mechanics, such as Minecraft:iron golem summoning, determine whether a block is solid by checking if it a Minecraft:full block, which is a property of its Minecraft:collision box.

• Still other mechanics, such as determining whether a block can have a Minecraft:torch or Minecraft:button attached to one of its faces, uses a separate system that checks geometric properties of the supporting block's "support box", which is usually the same as its collision box, but is different for certain blocks.

As the word "solid" is sometimes used to refer to all of these things, the set of "solid blocks" can be difficult to precisely define without additional context to determine which notion of solidity is being discussed.

See also

• Minecraft:Block states