Creators
Details
Licensed MIT
Published 7 months ago
Updated 2 weeks ago
All versions
26.1-1.0.0
Release
Casting Tools - 26.1-1.0.08 months ago 23
Compatibility
Minecraft: Java Edition
26.1
Platform
NeoForge
Supported environments
Changes
1.0.0
- Now called Modifier instead of Equipment Modifier
- Old system completely removed
- Modifier are now their own classes and extend a base Modifier class
- This allows for much better creation of custom modifiers for other mods as well as helping various modifiers work together
- This system also allow for better compatibility by setting other modifiers as incompatible with each other if needed, example of this is Silk Touch and Fortune modifiers are incompatible with each other as they are in vanilla Minecraft
- All Equipment Modifier Items are removed
- JEI now shows the modifier effect and recipes inside a single category
- Searching for tools like pickaxes will now show the modifiers category and only show modifiers that are compatible with the item you searched
- All of that is also driven my the main Modifier class
- Basically adding modifier just requires a few steps now instead of bascically re making the systme for each modifier
- Tooltips significantly improved
- Leveling up to get additional modifier is now removed
- All modifiers application requires Experience now, as defined in the Modifier Class
- Modifiers can still use either a fluid, a sized ingredient or both this too is defined in the Modifier Class
- Modifiers can also be customized in the config, at the moment the required fluids/ items are hard coded but can be changed in the future if required
- Valid items for modifiers are now a list of Tags, as defined in the modifier class
- Valid items can also be a List of items as well, for example ignite can be applied to sticks and swords again defined in the modifier class
- Modifiers no longer work in ticks, its more like a crafting table now where you can see the effect added to the item before taking the item. When taking the item all required fluids and items are consumed.
- Due to that change outputs can no longer be automated out of the Modifier
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:LVJmpiSe:wQv873bg"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LVJmpiSe:wQv873bg"
}

