tutorial:blocks
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
tutorial:blocks [2020/06/14 00:17] – more formatting fixes + highlights draylar | tutorial:blocks [2023/06/28 10:52] – [Registering your Block] baka4n | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Adding a Block ====== | ====== Adding a Block ====== | ||
- | ==== Introduction ==== | + | Adding blocks to your mod follows a similar process to [[tutorial: |
- | To add a block to your mod, you will need to register a new instance of the Block class. For more control over your block, you can create a custom block class. We'll also look at adding a block model. | + | ===== Creating |
- | ==== Creating a Block ==== | + | Start by creating an instance of '' |
- | To start, create an instance of Block in your main mod class. Block' | ||
<code java [enable_line_numbers=" | <code java [enable_line_numbers=" | ||
public class ExampleMod implements ModInitializer { | public class ExampleMod implements ModInitializer { | ||
- | // an instance | + | /* Declare and initialize our custom block instance. |
- | public static final Block EXAMPLE_BLOCK = new Block(FabricBlockSettings.of(Material.METAL)); | + | We set our block material to `METAL`. |
- | | + | |
+ | | ||
+ | | ||
+ | Stone has a hardness of 1.5f and a resistance of 6.0f, while Obsidian has a hardness of 50.0f and a resistance of 1200.0f. | ||
+ | |||
+ | You can find the stats of all vanilla blocks in the class `Blocks`, where you can also reference other blocks. | ||
+ | | ||
+ | // public static final Block EXAMPLE_BLOCK = new Block(FabricBlockSettings.of(Material.METAL).strength(4.0f)); // fabric api version > 0.77.0 | ||
+ | | ||
@Override | @Override | ||
public void onInitialize() { | public void onInitialize() { | ||
Line 21: | Line 28: | ||
</ | </ | ||
- | ==== Registering | + | ==== Registering |
+ | |||
+ | Blocks should be registered under the '' | ||
- | Registering blocks is the same as registering items. Call //Registry.register// and pass in the appropriate arguments. | + | If you're using version 1.19.2 or below, please replace '' |
- | <code java [enable_line_numbers=" | + | <code java [enable_line_numbers=" |
public class ExampleMod implements ModInitializer { | public class ExampleMod implements ModInitializer { | ||
- | // an instance of our new block | + | // public static final Block EXAMPLE_BLOCK = new Block(FabricBlockSettings.of(Material.METAL).strength(4.0f)); |
- | | + | public static final Block EXAMPLE_BLOCK = new Block(FabricBlockSettings.create()).strength(4.0f); |
| | ||
@Override | @Override | ||
public void onInitialize() { | public void onInitialize() { | ||
- | Registry.register(Registry.BLOCK, new Identifier(" | + | Registry.register(Registries.BLOCK, new Identifier(" |
} | } | ||
} | } | ||
</ | </ | ||
- | Your block will //not// be accessible as an item, but it can be seen in-game by using ''/ | + | Your custom |
- | ==== Registering | + | ==== Registering |
- | In most cases, you want to be able to place your block using an item. To do this, you need to register a corresponding BlockItem in the item registry. You can do this by registering an instance of BlockItem under Registry.ITEM. The registry name of the item should usually be the same as the registry name of the block. | + | In most cases, you want to be able to place your block using an item. To do this, you need to register a corresponding BlockItem in the item registry. You can do this by registering an instance of BlockItem under '' |
- | <code java [enable_line_numbers=" | + | <code java [enable_line_numbers=" |
public class ExampleMod implements ModInitializer { | public class ExampleMod implements ModInitializer { | ||
- | // an instance of our new block | + | // public static final Block EXAMPLE_BLOCK = new Block(FabricBlockSettings.of(Material.METAL).strength(4.0f)); |
- | | + | public static final Block EXAMPLE_BLOCK |
| | ||
@Override | @Override | ||
public void onInitialize() { | public void onInitialize() { | ||
- | Registry.register(Registry.BLOCK, new Identifier(" | + | Registry.register(Registries.BLOCK, new Identifier(" |
- | Registry.register(Registry.ITEM, new Identifier(" | + | Registry.register(Registries.ITEM, new Identifier(" |
} | } | ||
} | } | ||
</ | </ | ||
- | ==== Giving your block a model ==== | + | ===== Giving your Block Visuals ===== |
- | As you probably have noticed, the block is simply | + | At this point, your new block will appear as a purple and black checkerboard pattern in-game. This is Minecraft' |
+ | * A blockstate file | ||
+ | * A block model file | ||
+ | * A texture | ||
+ | * An item model file (if the block has an item associated with it). | ||
+ | |||
+ | The files should be located here: | ||
Blockstate: src/ | Blockstate: src/ | ||
Line 67: | Line 82: | ||
Block Texture: src/ | Block Texture: src/ | ||
- | The blockstate file determines which model that the block should use depending on it' | + | The blockstate file determines which model a block should use depending on its blockstate. |
<code JavaScript src/ | <code JavaScript src/ | ||
Line 77: | Line 92: | ||
</ | </ | ||
- | The block model file defines the shape and texture of your block. | + | The block model file defines the shape and texture of your block. |
<code JavaScript src/ | <code JavaScript src/ | ||
Line 88: | Line 103: | ||
</ | </ | ||
- | In most cases you want the block to look the same in hand. To do this, you can make an item file that inherits from the block model file: | + | In most cases, you will want the block to look the same in item form. You can make an item model that has the block model file as a parent, which makes it appear exactly like the block: |
<code JavaScript src/ | <code JavaScript src/ | ||
Line 96: | Line 111: | ||
</ | </ | ||
- | Load up Minecraft and your block should | + | Load up Minecraft and your block should have visuals! |
- | ==== Adding a block loot table ==== | + | ===== Configuring Block Drops ===== |
- | The block must have a loot table for any items to drop when the block is broken. Assuming | + | To make your block drop items when broken, you will need a //loot table//. The following file will cause your block to drop its respective item form when broken: |
<code JavaScript src/ | <code JavaScript src/ | ||
Line 124: | Line 139: | ||
</ | </ | ||
- | When broken in survival mode, the block will now drop an item. | + | In minecraft 1.17, there has been a change for breaking blocks. Now, to define harvest tools and harvest levels, we need to use tags. Read about tags at: [[tutorial: |
- | ==== Creating a Custom Block Class ==== | + | Harvest tool: src/ |
+ | Harvest level: src/ | ||
+ | |||
+ | <code JavaScript src/ | ||
+ | { | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | ] | ||
+ | } | ||
+ | </ | ||
+ | |||
+ | <code JavaScript src/ | ||
+ | { | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | ] | ||
+ | } | ||
+ | </ | ||
+ | |||
+ | For the harvest level tags (needs_stone_tool, | ||
- | When creating | + | |
+ | <code java [enable_line_numbers=" | ||
+ | public static final Block EXAMPLE_BLOCK = new ExampleBlock(FabricBlockSettings.of(Material.METAL).strength(4.0f).requiresTool()); | ||
+ | </ | ||
+ | |||
+ | ===== Creating | ||
+ | |||
+ | The above approach works well for simple blocks | ||
<code java [enable_line_numbers=" | <code java [enable_line_numbers=" | ||
Line 139: | Line 182: | ||
</ | </ | ||
- | Just like we did in the item tutorial, you can override methods in the block class for custom functionality. | + | You can override methods in the block class for custom functionality. |
- | If you want your block to be transparent, | + | <code java [enable_line_numbers=" |
- | <code java> | + | public class ExampleBlock extends Block { |
- | | + | |
- | </ | + | |
- | In versions before 1.15/ | + | public ExampleBlock(Settings settings) { |
+ | super(settings); | ||
+ | } | ||
- | <code java> | ||
- | @Environment(EnvType.CLIENT) | ||
@Override | @Override | ||
- | public | + | public |
- | return | + | if (!world.isClient) { |
+ | player.sendMessage(Text.of(" | ||
+ | } | ||
+ | |||
+ | return | ||
} | } | ||
+ | } | ||
</ | </ | ||
- | To add this block into the game, replace | + | To use your custom |
- | <code java [enable_line_numbers=" | + | <code java [enable_line_numbers=" |
public class ExampleMod implements ModInitializer { | public class ExampleMod implements ModInitializer { | ||
- | | + | public static final ExampleBlock EXAMPLE_BLOCK = new ExampleBlock(FabricBlockSettings.of(Material.STONE).hardness(4.0f)); |
- | | + | |
| | ||
@Override | @Override | ||
public void onInitialize() { | public void onInitialize() { | ||
- | Registry.register(Registry.BLOCK, new Identifier(" | + | Registry.register(Registries.BLOCK, new Identifier(" |
- | Registry.register(Registry.ITEM, new Identifier(" | + | Registry.register(Registries.ITEM, new Identifier(" |
} | } | ||
} | } | ||
</ | </ | ||
- | Your custom block should now be transparent! | + | ==== Custom Shape==== |
- | + | When using block models | |
- | ==== Custom VoxelShape ==== | + | |
- | + | ||
- | When making custom blocks | + | |
{{: | {{: | ||
+ | To fix this, we have to define the '' | ||
- | We have to define the VoxelShape of the new block into one which is not an entire block: | + | < |
- | + | public class ExambleBlock extends Block { | |
- | < | + | [...] |
- | @Override | + | |
- | | + | public VoxelShape getOutlineShape(BlockState state, BlockView view, BlockPos pos, ShapeContext context) { |
- | | + | return VoxelShapes.cuboid(0f, |
- | } | + | } |
+ | } | ||
</ | </ | ||
- | By doing so we also define getCollisionShape, | + | Note that the //collision shape// |
{{: | {{: | ||
- | ==== Next Steps ==== | + | ===== Next Steps ===== |
[[tutorial: | [[tutorial: | ||
[[tutorial: | [[tutorial: | ||
+ | |||
+ | To make your block flammable (that is, can be burned in fire), you may use '' |
tutorial/blocks.txt · Last modified: 2024/07/04 16:29 by mineblock11