2.0.2+neoforge-26.1.1
Compatibility
Changes
Update - 2.0.2
New
- Explosions no longer destroy spawners
TNT a player lit (or a fireball they sent back) now disables a spawner for that player, like a hit, instead of blowing it up for everyone. Any other explosion, like a creeper's, leaves it as it is. Player-placed spawners treated as vanilla still blow up.
Compatibility
- Spawner Control's spawn limit
With Spawner Control's
spawnLimit, a spawner that reaches its limit no longer disappears for the whole server: it runs out only for the players near it who used it up, and stays for everyone else with a fresh count. (Minecraft 1.20.1 to 1.21.5, the versions Spawner Control supports)
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:ltl1ms4K:ceU60Taj"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ltl1ms4K:ceU60Taj"
}

