All versions
1.5.11
Release
Loads of Bugfixes4 months ago 13
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Changes
- Fixed people sometimes getting stuck on the nether roof, this was due to the auto-unstuck procedure assuming that nether is overworld-like and attempting to unstuck the player by sending them to the nether roof. It should be fixed now.
- Fixed naturally generated chests being unbreakable, they should no longer be under protection of anti-grief procedure.
- Fixed players being able to open each others chests bypassing the anti-grief procedure. Now, only owners/trusted can open each other's chests.
- Fixed trusted players being unable to interact with their friends' chests. If they are trusted, they should now have permission to open the chests.
- Fixed anti-build perimeter making players unable to break their own graves.
- Buffed Eye Of Vengeance, players should now be able to teleport twice as fast to their death location, also, just for fun, made it so that the Eye Of Vengeance is eaten while being used. Dependant on player feedback, this may be reverted.
- Players can no longer place lava or water while under the effect of an anti-pvp perimeter. This would let players burn or hurt each other without directly interacting with one another. With this change, it should now be even harder to do such thing.
- Anti-pvp and Anti-build will now disappear if you use an Eye Of Vengeance and there isn't any perimeters nearby. This is to prevent carrying over your effects when you use your Eye Of Vengeance from bases, because usually it takes around 10 to 15 seconds to get rid of the effect, making it a headache sometimes to go back to your death point.
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:epAf73A1:pSJHnNFK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:epAf73A1:pSJHnNFK"
}

