Fabric Wiki

User Tools

Site Tools

Trace:
tutorial:items

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
tutorial:items [2024/08/26 01:04] – solidblocktutorial:items [2024/10/27 14:45] (current) – [Item components] solidblock
Line 8: Line 8:
  
 ===== Create an Item instance ===== ===== Create an Item instance =====
 +
 +:!: If you're in version 1.21.2 or above, please directly read [[#Creating Items in 1.21.2+]].
  
 First, create an instance of ''<yarn class_1792>''. The constructor takes in an ''<yarn class_1792>.<yarn class_1793>'' (or a ''FabricItemSettings'' unless versions since 1.20.5) instance, which is used to set item properties such as the durability, and stack count. For simplicity, we just do it in ''ExampleMod'' class, and store them in static fields. First, create an instance of ''<yarn class_1792>''. The constructor takes in an ''<yarn class_1792>.<yarn class_1793>'' (or a ''FabricItemSettings'' unless versions since 1.20.5) instance, which is used to set item properties such as the durability, and stack count. For simplicity, we just do it in ''ExampleMod'' class, and store them in static fields.
Line 17: Line 19:
     // for versions below 1.20.4     // for versions below 1.20.4
     public static final class_1792 CUSTOM_ITEM = new class_1792(new FabricItemSettings());     public static final class_1792 CUSTOM_ITEM = new class_1792(new FabricItemSettings());
-    // for versions since 1.20.5+    // for versions since 1.20.5, below 1.21.2
     public static final class_1792 CUSTOM_ITEM = new class_1792(new class_1792.class_1793());     public static final class_1792 CUSTOM_ITEM = new class_1792(new class_1792.class_1793());
     [...]     [...]
Line 96: Line 98:
  
 > **Note:** Some experienced users may decide to use reflection to automatically register all static fields of a class. This is also a preferable way, but should be used with caution. > **Note:** Some experienced users may decide to use reflection to automatically register all static fields of a class. This is also a preferable way, but should be used with caution.
 +
 +===== Creating Items in 1.21.2+ =====
 +
 +Since 1.21.2, the item registration is tutally rewrited. You have to store a ''RegistryKey'' in your ''Item.Settings'', so the models and translation keys will be correctly stored in item components. Otherwise, you may see the following exceptions and Minecraft does not run:
 +
 +<code>
 +java.lang.NullPointerException: Item id not set
 +</code>
 +
 +To make it run correctly, you should write like below:
 +
 +<code java>
 +public final class TutorialItems {
 +  private TutorialItems() {
 +  }
 +
 +  public static final Item CUSTOM_ITEM = register("custom_item", Item::new, new Item.Settings());
 +
 +  public static Item register(String path, Function<Item.Settings, Item> factory, Item.Settings settings) {
 +    final RegistryKey<Item> registryKey = RegistryKey.of(RegistryKeys.ITEM, Identifier.of("tutorial", path));
 +    return Items.register(registryKey, factory, settings);
 +  }
 +
 +  public static void initialize() {
 +  }
 +}
 +</code>
 +
 +In the method ''Items.register'', the registry key will be written in the ''settings'' first, and then use that ''settings'' to create the item.
 +
 ===== Adding model and textures ===== ===== Adding model and textures =====
  
Line 138: Line 170:
     }     }
  
 +    // write this if the version is below 1.21.2:
     @Override     @Override
     public class_1271<class_1799> method_7836(class_1937 world, class_1657 user, class_1268 hand) {     public class_1271<class_1799> method_7836(class_1937 world, class_1657 user, class_1268 hand) {
         user.method_5783(class_3417.field_14983, 1.0F, 1.0F);         user.method_5783(class_3417.field_14983, 1.0F, 1.0F);
         return class_1271.method_22427(user.method_5998(hand));         return class_1271.method_22427(user.method_5998(hand));
 +    }
 +    
 +    // write this if the version is 1.21.2 or higher:
 +    @Override
 +    public ActionResult use(World world, PlayerEntity user, Hand hand) {
 +        user.playSound(SoundEvents.BLOCK_WOOL_BREAK, 1.0F, 1.0F);
 +        return ActionResult.SUCCESS;
     }     }
 } }
Line 152: Line 192:
  
     // an instance of our new item     // an instance of our new item
 +    
 +    // For versions below 1.21.2:
     public static final CustomItem CUSTOM_ITEM = register("custom_item", new CustomItem(new class_1792.class_1793()));     public static final CustomItem CUSTOM_ITEM = register("custom_item", new CustomItem(new class_1792.class_1793()));
 +    
 +    // For versions since 1.21.2:
 +    public static final CustomItem CUSTOM_ITEM = register("custom_item", CustomItem::new, new class_1792.class_1793());
     [...]     [...]
 } }
Line 159: Line 204:
  
 ===== Item components ===== ===== Item components =====
-Sometimes you may need to add some default components for the item, such as max stack size or fire durability. This can be done by calling ''component'' method in ''Item.Settings''. Detailed information about item components can be found in [[https://docs.fabricmc.net/zh_cn/develop/items/custom-data-components|the tutorial in Fabric docs]].+Sometimes you may need to add some default components for the item, such as max stack size or fire durability. This can be done by calling ''component'' method in ''Item.Settings''. Detailed information about item components can be found in [[https://docs.fabricmc.net/develop/items/custom-data-components|the tutorial in Fabric docs]].
  
 In this example, the item will be unbreakable by default, while hiding tooltips about it. In this example, the item will be unbreakable by default, while hiding tooltips about it.
 <yarncode java> <yarncode java>
-    public static final CustomItem CUSTOM_ITEM = new CustomItem(new class_1792.class_1793().component(DataComponentTypes.UNBREAKABLE, new UnbreakableComponent(true)));+    // For versions below 1.21.2: 
 +    public static final CustomItem CUSTOM_ITEM = register("custom_item", new CustomItem(new class_1792.class_1793() 
 +        .component(DataComponentTypes.UNBREAKABLE, new UnbreakableComponent(true)))); 
 +    // For versions since 1.21.2: 
 +    public static final Item CUSTOM_ITEM = register("custom_item", CustomItem::new, new Item.Settings() 
 +        .component(DataComponentTypes.UNBREAKABLE, new UnbreakableComponent(true)));
 </yarncode> </yarncode>
  
-Specifically, max stack size can be simply set by calling ''maxCount'' method (which is valid also before 1.20.5). Note that if your item is damageable you cannot specify a maximum stack size or the game will throw a RuntimeException.+Specifically, max stack size can be simply set by calling ''maxCount'' method (which is valid also before 1.20.5). Note that if your item is damageable you cannot specify a maximum stack size or the game will throw a ''RuntimeException''. 
 <yarncode java [enable_line_numbers="true"]> <yarncode java [enable_line_numbers="true"]>
 public class ExampleMod implements ModInitializer { public class ExampleMod implements ModInitializer {
- 
     // An instance of our new item, where the maximum stack size is 16     // An instance of our new item, where the maximum stack size is 16
-    public static final CustomItem CUSTOM_ITEM = new CustomItem(new class_1792.class_1793().maxCount(16));+     
 +    // For versions below 1.21.2: 
 +    public static final CustomItem CUSTOM_ITEM = register("custom_item", new CustomItem(new class_1792.class_1793().maxCount(16))); 
 +    // For versions since 1.21.2: 
 +    public static final Item CUSTOM_ITEM = register("custom_item", CustomItem::new, new Item.Settings().maxCount(16));
     [...]     [...]
 } }
Line 183: Line 237:
     [...]     [...]
          
 +    // For versions below 1.21.2
     @Override     @Override
     public void onInitialize() {     public void onInitialize() {
         [...]         [...]
-        FuelRegistry.INSTANCE.add(TutorialItems.CUSTOM_ITEM, 300)+        FuelRegistry.INSTANCE.add(TutorialItems.CUSTOM_ITEM, 300);
     }     }
 } }
 </code> </code>
  
-In practice, when you have many items to register, as registering quantities of items may be effort-consuming and messy, you can consider placing them in a separate method. Here is an example:+However, in practice, when you have many items to register, as registering quantities of items may be effort-consuming and messy, you can consider placing the codes in a separate method, instead of writing like above. 
 + 
 +In versions below 1.21.2, you need to use Fabric API's ''FuelRegistry.INSTANCE''.
 <code java> <code java>
 public final class TutorialItems { public final class TutorialItems {
     [...]     [...]
          
 +    // For versions below 1.21.2
     public static void registerFuels() {     public static void registerFuels() {
-        FuelRegistry.INSTANCE.add(CUSTOM_ITEM, 300)+        FuelRegistry.INSTANCE.add(CUSTOM_ITEM, 300);
     }     }
 } }
 </code> </code>
 +
 +In versions since 1.21.2, use Fabric API's ''FuelRegistryEvents'':
 +<code java>
 +public final class TutorialItems {
 +    [...]
 +    
 +    // For versions since 1.21.2
 +    public static void registerFuels() {
 +        FuelRegistryEvents.BUILD.register((builder, context) -> {
 +            // You can add multiple items at once in this lambda.
 +            builder.add(CUSTOM_ITEM, 300);
 +        });
 +    }
 +}
 +</code>
 +
 And then refer to this method in your ''ModInitializer'': And then refer to this method in your ''ModInitializer'':
 <code java> <code java>
tutorial/items.1724634264.txt.gz · Last modified: 2024/08/26 01:04 by solidblock