Tags
Creators
Details
Licensed GPL-3.0-or-later
Published 2 years ago
Updated last week
All versions
1.20
Release
Opponent Tracking, Logout Modes & WorldGuard Fixeslast month 10.3K
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.4–1.21.11
Platforms
Paper
Purpur
Changes
Added
| Feature | Config |
|---|---|
Logout punishment modes none, kill, commands |
punishment.logout.mode, punishment.logout.commands |
| Command whitelist mode | command-restrictions.mode: whitelist |
| Allow Ender Pearls while teleporting is disabled | restrictions.teleporting.allow-enderpearl |
| Choose who gets tagged on a hit: both, attacker or victim | triggers.tag-mode |
| Only start combat below a set health | triggers.start-below-health |
Fixed
- Untag on kill now only removes the killer's tag if no other opponent is still active
- Dead players are now untagged on death
- Combat players could clip into
allow-combat-entry: denyregions by placing blocks at the barrier - Combat players could enter protected regions via teleports or Ender Pearls
- Players who still end up inside a protected region during combat are pushed back out
- Namespaced commands (
/plugin:command) bypassed the command blacklist - Tag effects no longer flicker on every hit, they get refreshed instead
Config
- Config version
3→4, migrated automatically (backup:config.v3.bak.yml) punishment.kill-on-logout→punishment.logout.mode(truebecomeskill)blocked-commands→command-restrictions.commands- New keys get their comments added on migration
Optional dependencies
Any compatible version
Any compatible version
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:LI8sodAD:XQkuttdy"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LI8sodAD:XQkuttdy"
}

