Links
Tags
Creators
Details
1.6.2
Compatibility
Changes
[SIZE=5][B]SpawnProtectionLite v1.6.2[/B][/SIZE]
This update strengthens protection around the exact boundaries of the protected area.
[LIST] [*][B]Improved multi-block placement protection[/B] Beds and other structures that affect multiple blocks can no longer be placed partially across the protection boundary.
[*][B]Fixed projectile PvP boundary bypasses[/B] Projectiles now remember whether they were launched from inside the protected area, preventing players from shooting from spawn and leaving before impact to bypass protection.
[*][B]Improved fluid boundary protection[/B] Water and lava can no longer flow into the protected area or modify protected source blocks by flowing outward.
[*][B]Improved version handling[/B] The plugin version is now obtained automatically from the Maven project during compilation. [/LIST]
[B]No configuration changes are required.[/B]
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:O1WrNhcu:TEd2mpWL"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:O1WrNhcu:TEd2mpWL"
}

