Tags
Creators
Details
2.0.0-beta
Compatibility
Required content
Changes
This update brings some things to the table.
Besides rewriting the whole mod in Kotlin, which might seem useless, but honestly since I enjoy programming with Kotlin more than Java it really makes me more prone to actively work on the project and finally add the features I felt were missing from the start.
This update is currently in Beta, I will wait until I get some positive feedback, or at least some downloads without any negative feedback, before changing this to the Release channel.
The main missing feature that was finally added was the option to choose which items to utilize to check where the enchantments can be applied. This is pretty straight forward but unfortunately, due to some limitiations with my proficiency with the widely available config APIs, there is no way to change this setting ingame :(
The other decent feature is that now all the default configs can be overwritten by any other mod or even via resource pack. This is not exactly the actual feature itself but honestly I see no problem letting it be this way. Power to the player.
The actual original point of the this feature was for people to be able to share configs via resource packs but more importantly for modders to be able to ship a single json file in their mod that will add default values to their custom enchantments for example.
I think this should be about it. It felt like more was accomplished but that might be due to the fruitless time I spent trying to bend mod config apis to my will. I'll try again soonish™.
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:yjpXhps7:BFUBguW1"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:yjpXhps7:BFUBguW1"
}
