Tags
Creators
Details
1.1.0
Compatibility
Changes
🚀 Release v1.1.0 — Initial Launch
We are excited to debut chromas-enchant-banner, an elegant, modern solution to enchantment balancing built explicitly for modern Minecraft architectures.
🌟 New Features
Granular Configuration Engine: Implemented full YAML mappings mapping modern lowercase namespaced keys (e.g., sharpness, mending) directly to Bukkit material item variants.
Anvil & Table Interception: Added strict event monitoring listeners (EnchantItemEvent, PrepareAnvilEvent) to natively block restricted combinations from entering the world.
Modern API Optimization: Tailored specifically for Paper 1.21.1 to correctly read Mojang Data Components safely without throwing legacy deprecation warnings.
Admin Utilities: Added the /ceb reload control command complete with a modular permission nodes array (enchantbanner.admin and enchantbanner.bypass).
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:jau870rL:QFd8ofuY"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:jau870rL:QFd8ofuY"
}

