All versions
1.6.0
Release
MCWild 1.6.0last year 21
Compatibility
Minecraft: Java Edition
1.21β1.21.8
Platforms
Paper
Purpur
Spigot
Changes
Version 1.6.0 - Combat Update
βοΈ Added
- Combat Tagging System: Players can no longer use
/wildwhile in PvP combat - Smart Combat Detection: Automatically detects player vs player damage including projectiles
- Configurable Combat Duration: Set how long combat lasts after taking/dealing damage (default: 15 seconds)
- Combat Notifications: Players are notified when entering and leaving combat
- Combat Logout Protection: Optional punishment system for players who log out during combat
- World Blacklisting: Disable combat tagging in specific worlds (spawn areas, creative worlds)
- New Permission:
mcwild.wild.combat.bypass- Allows bypassing combat restrictions - Combat-related Messages: New message configurations for combat status and restrictions
π§ Configuration Options Added
combat-tag.enabled- Enable/disable combat tagging systemcombat-tag.duration- Combat duration in seconds (default: 15)combat-tag.notify-on-tag- Notify players when tagged in combatcombat-tag.notify-on-untag- Notify players when combat endscombat-tag.punish-logout- Enable combat logout punishmentcombat-tag.logout-punishment- Type of punishment ("none", "kill", "damage")combat-tag.logout-damage- Damage amount for logout punishmentcombat-tag.blacklisted-worlds- List of worlds where combat tagging is disabled
π Enhanced
- Improved Logging: Enhanced debug output for combat events
- Thread Safety: Combat tag tracking uses thread-safe data structures
- Memory Management: Automatic cleanup of expired combat tags
- Error Handling: Better error handling for combat-related events
π οΈ Technical Changes
- Added
CombatManager.java- Core combat tagging logic - Added
CombatListener.java- PvP event handling - Updated
MCWild.java- Integrated combat manager - Updated
WildCommand.java- Added combat status checks - Enhanced plugin initialization and shutdown procedures
π Permissions
- Added
mcwild.wild.combat.bypasspermission for staff/VIP players - Updated
mcwild.*permission to include combat bypass
π¬ New Messages
combat-tagged- Notification when entering combatcombat-ended- Notification when leaving combatcannot-teleport-in-combat- Warning when trying to use/wildin combat- Combat logout punishment messages
- Combat help information
βοΈ Compatibility
- Backward Compatible: All existing features work unchanged
- Optional Feature: Combat tagging can be completely disabled via config
- No Breaking Changes: Existing configurations remain valid
- Spigot 1.21+: Optimized for latest Minecraft versions
π Bug Fixes
- Improved chunk loading reliability
- Enhanced error handling for teleportation failures
- Better memory management for player data
π Migration Notes
- No manual migration required
- Combat tagging is enabled by default but can be disabled
- Existing permissions and configurations remain unchanged
- New configuration options will be auto-generated on first startup
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:YLa9NkRH:BIfhO39D"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:YLa9NkRH:BIfhO39D"
}

