Tags
Creators
Details
1.2
Compatibility
Changes
-
Adds option in config for those who don't want to use the texture pack
- This will apply to all newly bucketed mobs across the server after it has been changed and the plugin reloaded. This is something that affects the whole server and is not able to be toggled per-player.
-
Adds the option to change the configured mobs whitelist into a blacklist instead
- This should make it simpler for people who want to enable all mobs or most mobs and use permissions as the main way of handling who can get what
-
Adjusted the default
textures.ymlfile to work properly for wolf variants and horse variants. To generate a new file - delete the old one before a server restart
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:9Ik5z3yE:oIFXDhNh"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:9Ik5z3yE:oIFXDhNh"
}

