Fabric Wiki

User Tools

Site Tools

Trace:
tutorial:enchantments

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:enchantments [2020/07/03 18:33] – formatting changes + mapping updates draylartutorial:enchantments [2024/08/23 13:52] (current) – [Adding Translations] solidblock
Line 1: Line 1:
-===== Adding Enchantments =====+====== Adding Enchantments ====== 
 + 
 +===== Adding enchantments since 1.21 ===== 
 +Since 1.21, enchantments has been data-driven, which means you should define them in data-packs, instead of in the codes. Please see [[https://minecraft.wiki/w/Enchantment_definition|Enchantment definition Minecraft page]] for details. 
 + 
 +To use the enchantments in code, you should just store ''RegistryKey'' objects of the enchantment. 
 +<code java TutorialEnchantments> 
 +public final class TutorialEnchantments { 
 +  public static final RegistryKey<Enchantment> FROST = of("frost"); 
 + 
 +  private static RegistryKey<Enchantment> of(String name) { 
 +    return RegistryKey.of(RegistryKeys.ENCHANTMENT, Identifier.of("tutorial", name)); 
 +  } 
 + 
 +  public static void initialize() { 
 +  } 
 +} 
 +</code> 
 + 
 +Remember to refer to the ''initialize'' method in your ''ModInitializer'': 
 +<code java ExampleMod> 
 +public class ExampleMod implements ModInitializer { 
 +  // [...] 
 + 
 +  @Override 
 +  public void onInitialize() { 
 +    // [...] 
 +    TutorialEnchantments.initialize(); 
 +  } 
 +} 
 +</code> 
 + 
 +To add a translated name for your enchantment, see the bottom of the tutorial. 
 + 
 +===== Adding enchantments before 1.21 ===== 
 +:!: This part of the tutorial only applies to older Minecraft versions.
  
 To add enchantments to your mod, you'll need to: To add enchantments to your mod, you'll need to:
Line 10: Line 45:
  
 ==== Creating Enchantment Class ==== ==== Creating Enchantment Class ====
-Our new enchantment is called //Frost// and slows mobs on hit. The slowness effect, durability, and potency will grow relative to the level of the enchantment.+Our new enchantment is called //Frost// and slows mobs on hit. The slowness effect, durability, and potency will grow relative to the level of the enchantment. In our enchantment class, we pass up ''UNCOMMON'' as the enchantment rarity, ''WEAPON'' as the enchantment target, and ''MAINHAND'' as the only valid tool type for our enchantment.
 <code java [enable_line_numbers="true"]> <code java [enable_line_numbers="true"]>
 public class FrostEnchantment extends Enchantment { public class FrostEnchantment extends Enchantment {
- +    public FrostEnchantment() { 
-    public FrostEnchantment(Rarity rarity, EnchantmentTarget type, EquipmentSlot[] slots) { +        super(Enchantment.Rarity.UNCOMMON, EnchantmentTarget.WEAPON, new EquipmentSlot[] {EquipmentSlot.MAINHAND});
-        super(rarity, type, slots)+
     }     }
 } }
Line 22: Line 56:
 We will now override a few basic methods for basic functionality: We will now override a few basic methods for basic functionality:
  
-''getMinPower'' is related to the minimum level needed to see the enchant in a table, but it is not a 1:1 ratio. Most enchantments return something like ''10 * level'', with different scales depending on the max level and rarity of the enchantment. We will return 1 so it is always available.+''getMinPower'' is related to the minimum level needed to see the enchant in a table, but it is not a 1:1 ratio. Most enchantments return something like ''10 * level'', with different scales depending on the max level and rarity of the enchantment. We will return 1 so it is always available. Note that the max power of an enchantment is set to ''min(level) + 5'' by default, which means this enchantment will only appear at very low levels. You will have to tweak your enchantment properties on your own and look at similar enchantment values to find the sweet number spot.
 <code java [enable_line_numbers="false"]> <code java [enable_line_numbers="false"]>
 @Override @Override
Line 42: Line 76:
 @Override @Override
 public void onTargetDamaged(LivingEntity user, Entity target, int level) { public void onTargetDamaged(LivingEntity user, Entity target, int level) {
-    if(target instanceof LivingEntity) { +    if(target instanceof LivingEntity livingEntity) { 
-        ((LivingEntity) target).addStatusEffect(new StatusEffectInstance(StatusEffects.SLOWNESS, 20 * 2 * level, level - 1));+        livingEntity.addStatusEffect(new StatusEffectInstance(StatusEffects.SLOWNESS, 20 * 2 * level, level - 1));
     }     }
  
Line 50: Line 84:
 </code> </code>
 If the entity we are hitting can have status effects (''LivingEntity''s can have status effects, but not ''Entity''), give it the slowness effect. The duration of the effect is 2 seconds per level, and the potency is equivalent to the level. If the entity we are hitting can have status effects (''LivingEntity''s can have status effects, but not ''Entity''), give it the slowness effect. The duration of the effect is 2 seconds per level, and the potency is equivalent to the level.
 +
 +The final enchantment file should look like this.
 +<code java [enable_line_numbers="true"]>
 +public class FrostEnchantment extends Enchantment {
 +    public FrostEnchantment() {
 +        super(Enchantment.Rarity.UNCOMMON, EnchantmentTarget.WEAPON, new EquipmentSlot[] {EquipmentSlot.MAINHAND});
 +    }
 +    
 +    @Override
 +    public int getMinPower(int level) {
 +        return 1;
 +    }
 +
 +    @Override
 +    public int getMaxLevel() {
 +        return 3;
 +    }
 +
 +    public void onTargetDamaged(LivingEntity user, Entity target, int level) {
 +        if(target instanceof LivingEntity) {
 +            ((LivingEntity) target).addStatusEffect(new StatusEffectInstance(StatusEffects.SLOWNESS, 20 * 2 * level, level - 1));
 +        }
 +
 +        super.onTargetDamaged(user, target, level);
 +    }
 +}
 +</code>
  
 ==== Registering Enchantment ==== ==== Registering Enchantment ====
 Registering enchantments follows the same process as usual: Registering enchantments follows the same process as usual:
 <code java [enable_line_numbers="false"]> <code java [enable_line_numbers="false"]>
-private static Enchantment FROST;+public class ExampleMod implements ModInitializer { 
 +    public static Enchantment FROST = new FrostEnchantment();
  
-@Override +    @Override 
-public void onInitialize() { +    public void onInitialize() { 
-    FROST = Registry.register( +        Registry.register(Registries.ENCHANTMENT, new Identifier("tutorial", "frost"), FROST); 
-        Registry.ENCHANTMENT, +    }
- new Identifier("tutorial", "frost"), +
- new FrostEnchantment( +
-     Enchantment.Weight.VERY_RARE, +
-     EnchantmentTarget.WEAPON, +
-     new EquipmentSlot[] { +
- EquipmentSlot.MAINHAND +
-     } +
- ) +
-    );+
 } }
 </code> </code>
 +> **Note:** In practice, if you have many enchantments, it is better to place them in a separate class. Here we did all things in ''ModInitializer'' for simplicity.
 +
 +This registers our enchantment under the namespace ''tutorial:frost''. All non-treasure enchantments are available in an enchanting table, including the ones you register.
  
-This registers our enchantment under the namespace ''tutorial:frost'', sets it as a very rare enchantment, and only allows it on main hand tools.+===== Adding Translations ===== 
 +=) This part works both versions since 1.21 and before 1.21.
  
-==== Adding Translations & Testing ==== 
 You'll need to add a translation to your enchantment as well. Head over to your [[tutorial:lang|mod lang file]] and add a new entry: You'll need to add a translation to your enchantment as well. Head over to your [[tutorial:lang|mod lang file]] and add a new entry:
  
-<code json [enable_line_numbers="false"]>+<code javascript resources/data/tutorial/lang/en_us.json>
 { {
     "enchantment.tutorial.frost": "Frost"     "enchantment.tutorial.frost": "Frost"
tutorial/enchantments.1593801181.txt.gz · Last modified: 2020/07/03 18:33 by draylar