1.5.5
Compatibility
Changes
-
Added Anti-Pvp Perimeter: When placed, it prevents combat within a 20 block radius, this radius can be expanded by feeding the perimeter diamond blocks, for each diamond block, there will be a 20 block expansion up to 60 blocks of distance. The perimeter also removes combat timer, so that waystones can be used within, preventing permanent combat traps.
-
Added Pvp Disabled effect: This is given by the Anti-Pvp Perimeter, and it makes it so that whenever a player hits another, the player that made the hit will receive significant damage, and the player that got hit will not receive any damage.
In future versions, I may make it so that the pvp perimeter cannot be toggled back on during combat, to prevent escaping a combat you're losing. And perhaps I can make it so that it automatically turns back on if any player gets killed within the perimeter's range.
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:7rbm71QO"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:epAf73A1:7rbm71QO"
}

