
Block is the basic unit in Minecraft. It is 3D object that can be placed in the world.
Step-by-step guide: how to make block →
This parameter controls how the block will be "seen" by the AI path navigators of the mobs.
Different AI path node types lead to different decisions on how to proceed with the movement when
near block, depending on the AI path node type.
If block base is used, some parameters might be disabled or might not work due to the base block
requiring them on default values from the base block.
Only use this parameter if there is a good reason for it, most blocks should have this set
to Default basic block (meaning no block base).
Select the color your block will apply to the beacon beam (like the red glass, orange glass, etc).
Leave to DEFAULT to keep vanilla handling (no color change).
This parameter controls the GUI of your block. It's needed to make a chest or crafting block for example.
If this parameter is checked, this block will open the bound GUI on right-click.
This parameter controls sounds and behavior of some block bases:
Sound group that defines this block. This parameter affects sounds as block placement sound,
block breaking sound and sound played when walking on the block.
Here you can list additional custom properties of this block.
Block properties define basic possible states of the block.
Try to make as little combinations as possible, as the more combinations,
slower the game load and higher the memory usage.
The more property combinations possible, the slower the game will load and operate.
If you need to define a lot of states, consider using NBT data instead.
Some properties are used internally (for block rotation, waterlogging, and block bases),
so their names can not be used.
Along with custom ones, you can also include pre-defined block state properties used by vanilla Minecraft blocks.
This condition determines whether using bone meal on this block is successful.
If this returns false, the bone meal will be consumed, but the
"${l10n.t("elementgui.common.event_on_bonemeal_success")}" procedure won't be executed.
This condition determines whether bone meal can be used at all on this block.
If this returns false, the bone meal won't be consumed and nothing will happen.
The block dimensions and bounding box sets the hitbox for the block if its a custom model.
It also can resize a regular block size from something that is cube to other dimensions if no custom model is used.
This will only set the dimensions, not the shape, though.
To understand how bounding box parameters work, click here.
This is the sound played when the block is broken.
If this parameter is checked, any plant can be placed and grow on the block.
If this parameter is checked, the player will be able to walk through it, like tall grass and vines, if you check it.
Block will have bounding box, but it will not be collidable.
This is the color your block appears as on maps.
If set to Default, the color is based on the material of the block.
To see the exact RGB colors of all entries, read the Wiki page here.
Check this parameter if you want the block to work with comparators.
This parameter should only be used in combination with transparent blocks.
This will make internal sides of the block connect similar to how glass, ice and
other similar blocks do this.
This determines what item is selected when you "pick" (middle-click with mouse) the block.
If empty, the creative pick item is the block itself.
This parameter defines a custom item or block that is dropped when this block is mined/broken.
If harvest level is used, only proper level harvest tools will make the block drop.
This is the default value of the block state property when the block is generated/placed in the world.
This parameter specifies the name of this custom block property.
Defines which type of values can be accepted by this block property:
These are the values that this custom block property can have.
If the block has a random model offset, its bounding box will also be moved, unless this option is selected.
If the bounding box is submerging into neighboring blocks because of the offset, check this box to prevent that.
For example, this option would be false for bamboo, and true for tall grass.
Triggers a procedure randomly.
This trigger is triggered on client-side only so no real world modifications except for
playing sounds and placing particles should be done from here.
This parameter controls how many drop items or blocks the block drops when this block is broken.
Check this parameter if you want the items to drop when the block is broken.
Chests use this parameter, for example.
Check this property to have a glowing effect (similar to the magma block) applied to your block.
If you check this parameter, this block will be able to emit redstone power.
If your block rotates horizontally, check this box to allow it facing floor, walls or ceiling at any direction.
This option is used by lever, grindstone, etc.
This parameter controls the power bonus that the block has for the enchanting table.
The power bonus of the bookshelf is 1, of normal blocks, it is 0.
Use this procedure trigger to specify additional harvest condition.
Both vanilla and custom harvest condition need to be met for the block to be harvested.
If this procedure returns false, the block will not be harvested.
This sound is played when the block falls.
This parameter controls how quickly the fire spreads to other blocks.
This parameter determines how quickly the block is consumed by fire.
Vanilla examples:
This parameter should only be used in combination with transparent blocks.
If this is checked, the block won't display the fluid texture when submerged, similar to glass blocks.
Sets the average number of ore veins to spawn per chunk.
Vanilla ore group per chunk values:
This parameter controls the average amount of block per ore veins.
Vanilla ore group sizes:
This parameter controls the Y height range that this block can generate in.
Vanilla generation height ranges:
List of blocks this block can replace when generating.
If you leave this list empty, the block will not naturally generate as it will not be able
to place itself on the world.
The generation shape allows changing how the block is generated depending on the height of the block.
to get this block will be the middle of the minimal and maximal height. Keep in mind that the maximal and minimal
generation heights can be above and below world limits.
This parameter controls how long it takes to mine the block.
A higher value means it takes longer to mine this block.
This parameter controls what tool you want to mine the block.
Ores use pickaxe here, logs axe, dirt shovel.
If set to "Not specified", players will be able to break this block with hand.
If this option is selected, light opacity is determined by the "Light opacity" spinner.
This option should be unchecked in most cases.
If this parameter is checked, the block will fall down like sand.
This parameter will give an inventory to your block. The block will be a tile entity.
This parameter enables features such as:
These features will not work without this parameter checked.
Check this parameter if your block:
If you check this box, the block will:
This is the sound played when the player mines the block.
NOTE: This sound is played in loop while breaking until the block is broken.
If this option is checked, this block can catch fire when it's close to lava.
Input slots will not be used as output/source for hopper item transmission.
This parameter specifies additional condition that must be met in order for
automation (hoppers, 3rd party inventory automation mods) to be able to place
items into the selected slot of this block's inventory.
This condition is checked together with list of slots that allow inserting items,
so both conditions need to be met.
This parameter specifies additional condition that must be met in order for
automation (hoppers, 3rd party inventory automation mods) to be able to take
items from the selected slot of this block's inventory.
This condition is checked together with list of slots that allow taking items,
so both conditions need to be met.
This parameter controls how many slots your block will use for its internal inventory.
If the block is bound to GUI, set this value to the biggest slot ID in the GUI + 1
This parameter controls maximal size of the stack that can be placed in its internal inventory slots.
Keep in mind that the smaller number between this parameter and max item stack size
determines the actual max stack size.
If this option is enabled, the block can be fertilized with bone meal.
If this option is checked, a fixed tint will be applied to the block while it's in the inventory,
matching the tint type.
The tint is applied also when an item texture is specified.
If checked, entities will be able to climb on the block.
The block's width and depth need to be less than 1 for this parameter to work,
so the collisions in the block are detected properly. Change the bounding box
setting to match this if this parameter is used.
Vanilla examples: Ladder and Vines
If checked, water will be placeable inside the block.
Vanilla examples: Slabs, Stairs, etc.
This optional property will change the texture of the block in the inventory.
Commonly used with doors or custom models.
This parameter controls the jump height of entities
Default value used by most of the blocks is 1.0.
The honey block jump factor is 0.5.
This parameter controls how often particles spawn below this block.
Higher values mean the leaves will emit more particles.
This parameter controls which particles spawn below this block. If not specified, it defaults to tinted leaves
particles.
If this block is not tinted, the color of the tinted leaves particles is based on the main texture.
This property determines how much the light level decreases when going through this block. For example, a value of 15
will block all the light, a value of 0 will make the block transparent for light.
This parameter controls how much light the block emits.
It is a value between 0 and 15.
If set to 0, the block won't emit light.
If set to 15, the block will emit as much light as glowstone.
If controlled by a procedure (supported by block mod elements),
make sure to only get block state values
and not modify them, or the game will crash.
Additionally, keep in mind the value is cached, so you cannot use
random as a light level source.
Select the model to be used with this block. Model only defines visual look and not the
bounding box of the block.
When making custom models, JSON is recommended due to vanilla support for this model type.
Selecting JAVA model will force this block to have block entity enabled.
JAVA models also will also be much more resource heavy, so make sure to not use them in blocks
that commonly appear, such as world gen blocks.
Here you can specify animations that this block entity can play and the conditions when animations happen.
**Make sure that animations you use only reference model parts/bones that are present in the model file.
Otherwise, the model may fail to load or the game may crash.**
We recommend using NBT data to provide data for animation conditions, as the condition is client-side
only, but data for toggling animations is usually not client-side.
Existing model animations specified in the model file or during model file import will also
play alongside animations specified here.
This parameter controls the instrument of note blocks placed on this block.
This parameter controls if block placement should be randomly offset and by which axis.
Most plants use one of the offset types.
This procedure determines what happens when bone meal is used successfully on this
block.
Triggers a procedure when a projectile hits the block.
This procedure determines what happens when a vibration is received.
Triggers a procedure when the block is not powered by the redstone power.
Triggers a procedure when the block is powered by the redstone power.
Output slots will not be used as input for hopper item transmission.
This optional property will change the texture of the particles when the block is broken,
an entity lands on the block and so on.
This is the sound played when the player places the block in the world.
This condition determines whether this block can be placed in a specific location. If the position is
no longer valid, the block will be broken once it receives a block update.
NOTE: This condition isn't checked during world generation.
This parameter controls what block is inside the flower pot.
This parameter determines how the block reacts with a piston.
This condition specifies whether the block should receive the detected vibration or not.
If this parameter is checked, redstone dust will always connect to
this block (similar to the Redstone Blocks).
NOTE: The block can still emit redstone power even if this parameter isn't checked.
If emit redstone parameter is checked, this parameter will allow you to modify the emitted redstone power.
When this a conditional procedure is used and returns a number,
the redstone power emitted by this block will be set by the returned number of the procedure.
NOTE: The block can still emit redstone even if redstone doesn't connect to it.
WARNING: When using custom number provider procedure, you will need to notify neighbouring
blocks of redstone value change for them to register the change.
If you check this parameter, the player will be able to place another block
on it (this block can be replaced by other blocks being placed).
Examples: air, most plants
If this option is enabled, the block will drop only when broken with the specified harvest tool.
This parameter controls how the block reacts to explosions.
A higher value makes the block more resistant to explosions.
If this parameter is checked, this block will be sensitive to vibrations like *Sculk Sensor*.
NOTE: Block entity needs to be enabled for this to work.
This is the texture used by signs to render in the world. Make sure the texture is compatible with the sign model.
This texture appears while editing the text of a hanging sign. The texture should be 16x16.
This parameter controls how slippery the block is.
Default value used by most of the blocks is 0.6
This parameter adds a tooltip to the block when
you hold your icon over the block in your inventory.
If you use a procedure-generated tooltip, and your block is
not held by an entity or currently a dropped item entity,
the entity dependency will be null.
This parameter controls the speed of entities on this block.
Default value used by most of the blocks is 1.0.
The soul sand and honey block speed factor is 0.4.
This is how many items in the slots in this block's inventory can stack too.
Keep in mind that there is another slot stack size limit set for the specific items, so this is an upper limit
of the slots that can be further limited by items.
When this parameter is enabled, a bounding box specified in the state
will be used instead of the block's default bounding box.
If collisions are disabled, this parameter has no effect.
Select the model to be used with this block state. Model only defines visual look and not the
bounding box of the block.
When making custom models, JSON is recommended due to vanilla support for this model type.
This list defines block states for this block and their conditions.
Using this system, you can create blocks that change depending on their
block state property values.
If a certain block state property is used in state condition, it needs to be used in
all state conditions.
If block rotation is enabled, Mod Maker will automatically generate all the necessary state combinations to handle rotations.
Missing combinations of properties will be autofilled for you with the default block state.
This is the sound played when an entity walks on this block.
This parameter controls what this block turns into when it's stripped with an axe.
Blocks naturally generated will usually not tick by default, unless tick randomly is used.
This parameter makes block tick randomly, where speed is controled by a global world tick
parameter.
This type of ticking is used by plants, for example.
This parameter controls how often the block will tick. If tick randomly is selected, this parameter
has no effect.
Keep in mind that usually, blocks naturally generated will not tick by default, unless tick randomly
is used.
Default tick rate of 0 means the block will not tick automatically.
If this parameter is set to a number greater than 0, the block will tick automatically. There are 20 world ticks in a second.
This option applies a tint to the block based on biome colors, similar to grass, leaves, and water.
For best results, the tinted faces should use a grayscale texture.
Check this box if your block has transparency -
Leave unchecked for a solid block, check it if your block is similar to leaves, glass, iron bars, etc.
Transparency types:
This parameter defines if the player will be able to mine it.
Vanilla examples: Bedrock and command block
Triggers a procedure when the block is ticked.
Naturally spawned blocks will only tick if random ticking is used for performance reasons.
When enabled, the block will not generate a loot table automatically.
Instead, the user will have to define block drops manually.
Create loot table mod element with registry name blocks/${registryname}, namespace _mod_, and type _Block_.
Loot tables can still override block drops, even if this option is not enabled.
This is the tier of tool required to break this block.
Only the tier of tool you specify will be able to break your block.
If you want more control such as custom tiers,
use custom procedure for harvest condition.
The maximum distance that this block can receive vibrations.
Game events whose vibrations this block can receive.
Triggers a procedure when the block is added to the world (might not be called by some natural generators).
Triggers a procedure when something places the block (entity/block) besides this block.
Triggers a procedure when a player starts to destroy the block.
Triggers a procedure when the block is destroyed by an explosion.
Triggers a procedure when the player breaks the block.
Triggers a procedure when an entity is inside the block.
Triggers a procedure when an entity walks on top of this block.
It won't be called if the entity is sneaking.
Only works with blocks that have full height. It won't work with slabs, pressure plates, etc.
For those cases, use collide trigger instead.
Triggers a procedure when a block next to this one is updated (blockstate changes, new block is placed or
a block is removed).
When a player right-clicks on the block, the procedure will be executed.
The procedure should return an action result of type SUCCESS/CONSUME if it performs an action, and PASS otherwise.
If a GUI is opened on right-click, or if the procedure doesn't return any value, then the action result type
will be SUCCESS.
This is the amount of experience dropped by this block when it's broken by a player.