All versions
0.2
Release
Health-Sync10 months ago 609
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.x
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
1.15.x
1.14.x
1.13.x
1.12.x
1.11.x
1.10.x
1.9.x
1.8.x
Platforms
Bukkit
Paper
Spigot
Changes
Changelog
All notable changes to the HealthSync project will be documented in this file.
[0.2] - 2026-01-08
✨ New Features
- Smart Respawn System: Implemented logically consistent respawn mechanics.
- Respawning players now inherit the group's current low health/hunger state instead of healing the group to full.
- Prevents "tactical suicide" to restore team health.
- Invitation Expiry: Group invites now automatically expire after 60 seconds to prevent invite spam lingering.
🐛 Bug Fixes
- Infinite Damage Loop: Fixed a critical recursion issue where syncing damage would trigger the damage event again, causing server crashes (StackOverflow).
- Potion Effect Loop: Resolved an issue where syncing potion effects caused an infinite update loop between client and server.
- Hunger Sync Glitch: Fixed an issue where saturation synchronization could cause "ghost hunger" updates.
- Group Cleanup: Fixed a logic error where groups would not properly dissolve if the owner disconnected, leaving "ghost groups".
⚡ Improvements
- Performance: Optimized the
HealingListenerandHungerListenerto use cached values, reducing the number of unnecessary packet updates. - Code Structure: Refactored
LinkManagerto better handle Group objects instead of raw UUID maps. - GUI: Updated the Management GUI to correctly display live heart/hunger values of members.
[0.1] - Previous
- Initial Groups Implementation.
- Basic Health Sharing.
- GUI Introduction.
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:ZOKLevpf:6rStGuPS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ZOKLevpf:6rStGuPS"
}

