1.2.0
Compatibility
Changes
SpawnProtection v1.2.0 — Better Spawn Area Configuration
Added
-
Added
spawn.world. -
Server owners can now choose which world spawn should be protected.
-
SpawnProtection no longer depends on the first loaded world.
-
Added
spawn.check-y-axis. -
false: uses cylindrical protection based only on X/Z distance. -
true: uses spherical protection including height difference. -
Added protection mode details to
/spawnprotection info. -
Protected world
-
Radius
-
Protection mode
-
Y-axis check status
-
Configured language
-
Added a built-in config migration system.
Changed
- SpawnProtection now uses the configured world from
spawn.world. - Radius checks now support both cylindrical and spherical protection.
- Cylindrical protection is now the default mode.
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:RyOzGsH2:S371gDgn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:RyOzGsH2:S371gDgn"
}

