Tags
Creators
Details
2.3.0
Compatibility
Changes
Important Changes
To leverage the new config system you must delete your old config.yml and let the plugin create a new config.
New Features
- add Folia support (dfdb19dcacd9d6d1a6c0cf15eeaeee9149095562 by @darksaid98)
Bug Fixes
- use configurate instead of crate (5cbf6e55a68d55aa501b840bcff5d65d93e1513b by @darksaid98)
Build System & Dependencies
- don't add vault when running testing (524547c5189e0c15bc9d15c3a62eb15c3cb997e7 by @darksaid98)
- bump com.github.milkdrinkers:colorparser from 2.0.3 to 3.0.1 (00aa19afa2a938af1c7fdcf567472cee992d1c04 by @dependabot[bot])
Chores
- bump version to v2.2.1 (89b509ecd5243792e3112464e93ae7d815a02eef by @darksaid98)
Full Changelog: https://github.com/milkdrinkers/Enderchester/compare/2.2.1...2.3.0
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:iEpIvtaS:yaePHq8n"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:iEpIvtaS:yaePHq8n"
}

