1.8.0
Compatibility
Changes
SimpleCombatLog v1.8.0 - The Safezone Update
โ ๏ธ IMPORTANT: This version ONLY supports Minecraft 1.21+ (Java 21). If you need support for versions 1.12 - 1.20, please download Version 1.4 from the versions tab.
โจ New Features
-
๐ Native Spawn Protection (No Dependencies):
-
You can now define a radius around the world spawn point in
config.yml. -
Tagged players are physically prevented from entering this radius, even if you don't use WorldGuard.
-
-
๐ฉ Custom WorldGuard Flag:
-
Added the
combat-entryflag! -
Instead of listing regions in the config, you can now simply run
/rg flag <region> combat-entry denyto create safezones.
-
-
๐ก๏ธ Hologram Stabilization:
-
Fix: Added a de-duplication check to prevent "stacked" holograms if the server reloads multiple times.
-
Fix: The plugin now checks if chunks are loaded before trying to update the leaderboard to prevent "ghost" entities.
-
๐ ๏ธ Config Changes
- Added
spawn-protectionsection (Enabled by default, 16 blocks).
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:79ZvL4gp:uISv0w4N"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:79ZvL4gp:uISv0w4N"
}

