1.1.0
Compatibility
Changes
v1.1.0 - Custom items support
Added support for using items from popular custom-item plugins as the base material for your command items:
- Oraxen
- ItemsAdder
- DGTexture
- Nexo, MMOItems, MythicMobs
Just hold the custom item in your hand, open /dgci, and the plugin auto-detects it. Textures, models, names and lore from the source plugin are kept intact.
Also includes a bunch of internal stability improvements and bug fixes from the latest audit.
š¬ Need help or want to report a bug? Join our Discord: https://discord.gg/ZZhVKUtSNS
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:2ofJzmvb:21cmMr9t"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2ofJzmvb:21cmMr9t"
}

