Links
Tags
Creators
Details
1.4.0
Compatibility
Changes
## SpawnProtection v1.4.0 — World Protection Mode
This update adds a new protection area mode, making SpawnProtection more flexible for both simple survival servers and dedicated hub/lobby worlds. **
Added**
- Added
protection-area.mode. - Added support for two protection modes:
radius— protects an area around the configured spawn world center.world— protects the entire configured world.
- Added automatic config migration to
config-version: 3. /spawnprotection infonow shows the active protection area mode.
### Changed
- Protection checks are now centralized internally through the plugin protection area logic.
- All listeners now respect the selected protection mode automatically.
- Radius settings are now ignored when using
worldmode. /spawnprotection infonow displays clearer information depending on the selected mode.
### Improved
- Better support for dedicated lobby/hub worlds.
- Server owners can now protect an entire lobby world without WorldGuard, regions, or complex setup.
- Existing radius-based protection remains available for simple survival servers where the spawn is inside the main world.
### Compatibility
- Existing configs are migrated automatically.
- Existing values are preserved during migration.
- A backup is created before migration.
config-versionis now3.- Existing commands, aliases and permissions remain unchanged.
- No manual config deletion is required.
### Example
Protect only a spawn radius:
protection-area:
mode: "radius"
spawn:
world: "world"
radius: 50
check-y-axis: false
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:4GC208HY"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:O1WrNhcu:4GC208HY"
}

