1.1.0
Compatibility
Changes
๐ฉ DonutCombat - v1.1.0 Update Changelog
๐ New Features & Improvements
Folia Support Added! ๐งต
- The plugin is now 100% compatible with Folia's multi-threaded region-based architecture. Enjoy seamless performance on high-player servers!
Performance Optimizations โก
- Core combat timers and event listeners have been refactored for significantly lower resource usage.
๐ Bug Fixes
-
Folia Scheduler Fixes: Resolved issues with task scheduling and region-specific teleportation bugs under Folia
-
Console Cleanup: Fixed various internal warnings and potential NullPointerExceptions during combat sequences
-
Combat Tag Stability: Addressed minor edge-case glitches in the combat logging logic to prevent exploits
โ ๏ธ Note: Users updating from v1.0.0 are recommended to back up their server before swapping out the JAR file.

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:FVcYcHyn:pRZ1x7du"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:FVcYcHyn:pRZ1x7du"
}

