Tags
Creators
Details
Licensed MIT
Published 3 years ago
Updated 4 months ago
All versions
1.1.2
Release
Hotfix - Disable Mob Griefing 1.1.24 months ago 722
Compatibility
Minecraft: Java Edition
1.21.x
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
1.15.x
1.14.x
1.13.x
1.12.2
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
v1.1.2
Bug Fixes
- Fixed TNT, TNT minecart, and ender crystal config keys not mapping correctly across server versions (Paper 1.21+ renamed TNT → primed_tnt, TNT_MINECART → minecart_tnt, END_CRYSTAL → ender_crystal internally)
- Fixed explosions silently disappearing with no sound or particles when griefing was disabled — explosions now always play visually and audibly; only block damage is suppressed
- Fixed
explosion_player_damageconfig key not being read correctly; renamed toexplosions_damage_players(existing value auto-migrated on upgrade)
Changes
- All mob griefing now defaults to
trueon fresh installs, mirroring vanilla Minecraft behavior — disable only what you need - Removed
require_opconfig key; permissions are handled by plugin.yml and LuckPerms/permission plugins - Block damage and player damage from explosions are now controlled independently:
disabling a mob's griefing stops block damage while the explosion still affects
players; set
explosions_damage_players: falseto also prevent player damage
New Commands
/mobgriefing verbose <true/false>— toggle verbose console logging in-game/mobgriefing explosions_damage_players <true/false>— toggle player damage from explosions in-game- Tab completion now includes
verbose,explosions_damage_players, andreload
Upgrading from v1.1.1
explosion_player_damagein your config will be automatically renamed toexplosions_damage_playerson first load — no manual action needed- All griefing keys that were previously
false(disabled) will remain as-is; new installs default totrue
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:lVJGboKm:33FEZ0cC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:lVJGboKm:33FEZ0cC"
}

