Changes

6 bytes added ,  21:14, 2 August 2021
Update to 1.17
Line 1: Line 1: −
A <code>Potion</code> is simply a list of <code>Effect</code>s to be applied when used. Each <code>Potion</code> gets applied to every <code>Items#POTION</code>, <code>Items#SPLASH_POTION</code>, <code>Items#LINGERING_POTION</code>, and <code>Items#TIPPED_ARROW</code>. Like effects, potions need to be [[Registration|registered]].
+
A <code>Potion</code> is simply a list of <code>MobEffectInstance</code>s to be applied when used. Each <code>Potion</code> gets applied to every <code>Items#POTION</code>, <code>Items#SPLASH_POTION</code>, <code>Items#LINGERING_POTION</code>, and <code>Items#TIPPED_ARROW</code>. Like mob effects, potions need to be [[Registration|registered]].
    
== Creating a <code>Potion</code> ==
 
== Creating a <code>Potion</code> ==
   −
A <code>Potion</code> requires a passed in list of <code>EffectInstance</code>s to apply to the player when the potion is "consumed". There is also a nullable parameter called <code>baseName</code> that can be set if you would like to use the same name for multiple potions (e.g. a <code>SWIFTNESS</code> and <code>LONG_SWIFTNESS</code> entry can be both <code>swiftness</code> potions).
+
A <code>Potion</code> requires a passed in list of <code>MobEffectInstance</code>s to apply to the player when the potion is "consumed". There is also a nullable parameter called <code>name</code> that can be set if you would like to use the same name for multiple potions (e.g. <code>SWIFTNESS</code> and <code>LONG_SWIFTNESS</code> can be both <code>swiftness</code> potions).
    
== Adding a Brewing Recipe ==
 
== Adding a Brewing Recipe ==