Links
Tags
Creators
Details
Licensed MIT
Published 4 years ago
Updated 2 years ago
All versions
1.18.2-1.0.0
Release
1.18.2-1.0.04 years ago 275
Compatibility
Minecraft: Java Edition
1.18.2
Platform
Forge
Supported environments
Client and server
Changes
- Add recipes for enchantments from other mods
- CoFH Core
- Ensorcellation
- Twilight Forest
- Apotheosis
- VanillaTweaks
- Add support for registration conditions in enchantment recipes
mod_loaded: Checks if a mod is loadedapotheosis_module: Checks if an Apotheosis module is enabledcofh_enabled: Checks if a CoFH Core-based enchantment is enabledtag_exists: Checks if an item tag has any entries in itnot: Inverts the conditionand: Resolves true if all conditions are trueor: Resolves true if at least one condition is truexor: Resolves true if all conditions resolve the same
- Add client configuration option to display enchantment levels in Enchanter's Workbench and Precision Grindstone as numbers rather than Roman numerals
- Expand
/precisionenchanter checkrecipescommand to find all enchantments that don't have a registered enchantment recipe - Add optional parameter to
/precisionenchanter checkrecipescommand:impossible|free|missing - Rename creative mode tab title from "Precision Enchanting"
- Enchantment instances with levels above 9 are now sorted correctly in the Enchanter's Workbench
- Fix recipes in the Enchanter's Workbench not appearing until interacting with it at least twice in multiplayer
- Cost of previewed enchantment recipe now appears in multiplayer
- Fix crash caused by registering an enchantment recipe with an unregistered item
- Fix crash caused by registering an enchantment recipe with no ingredients or no resulting enchantment
- Reloading server data no longer deletes all enchantment recipes
- Hovering over the recipes tablet button in the Enchanter's Workbench now displays "Show|Hide Recipes" (1.18.2, 1.19.2)
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:EwPfmT4T:Q0HjxS3y"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:EwPfmT4T:Q0HjxS3y"
}

