Tags
Creators
Details
1.10.1
Compatibility
Changes
Changelog
-
Fixed support for 1.21: Some vanilla entities were renamed starting Minecraft 1.21 and stopped working properly. Apart from fixing the issue internally, new aliases have been added for some entities. You can use either the legacy name or one of the aliases, no matter which Minecraft version you are on. Even if you use an alias, you will still see the legacy name everywhere else in the plugin.
- TNT and PRIMED_TNT
- TNT_MINECART and MINECART_TNT
- END_CRYSTAL and ENDER_CRYSTAL
-
Fixed exploding block configuration: BED and RESPAWN_ANCHOR vanilla blocks were announced to be supported starting ExplodeAny 1.10. However, they couldn't be properly configured through VanillaEntity. Now they can be fully configured!
Server support
- Bukkit-based server 1.7 - 1.21 (Bukkit, Spigot, Paper...)
- Folia-based server 1.19 - 1.21
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:b3oVwYdE:OjsD9ijl"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:b3oVwYdE:OjsD9ijl"
}

