Tags
Creators
Details
1.2.0
Compatibility
Required content
Changes
Full English changelog available on GitHub. Full French changelog available on our Discord.
Summary
This update adds the Nether Star Infusion system, allowing selected Netherite armor, tools, and weapons to grant one refreshed potion effect while equipped or held.
Added
- Added Nether Star Infusion
- Added 10 Infusion Cores: Night Vision, Water Breathing, Resistance, Fire Resistance, Speed, Slow Falling, Jump Boost, Strength, Haste, and Luck
- Added shapeless recipes for all Infusion Cores using Nether Star Block Core and a matching catalyst item
- Added anvil infusion support for Netherite equipment
- Added refreshed potion effects while infused armor is equipped
- Added refreshed potion effects while infused tools or weapons are held in the main hand
- Added dedicated textures, item models, translations, and tooltips for all Infusion Cores
Changed
- Changed Nether Star Block Core to be the base component for creating Infusion Cores
- Changed tool and weapon infusion effects to activate only from the main hand
- Changed infusion to be limited to Netherite armor, tools, and weapons
Improved
- Improved Nether Star Block Core usefulness with a new late-game upgrade path
- Improved progression around Nether Star crafting and advanced equipment upgrades
- Improved visual clarity for Infusion Cores with distinct colors and symbols
Notes
- Each item can only have one infusion effect
- Already infused items cannot be infused again
- Infused armor effects are active only while equipped
- Infused tool and weapon effects are active only while held in the main hand
- Potion effect icons remain visible, but particles are hidden
- On Arkensia, Master Ball crafting requires
cobblemon:master_ballto be removed from Item Obliterator’sonly_disable_recipeslist
Optional dependencies
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:1Eb2AwPa:ATfIyhsj"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1Eb2AwPa:ATfIyhsj"
}

