Tags
Creators
Details
Licensed ARR
Published 10 months ago
Updated 2 months ago
All versions
26.3.4-SNAPSHOT
Release
PlayerDataSync 26.3.4-SNAPSHOT8 months ago 209
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
Purpur
Spigot
Changes
[PlayerDataSync-26.3.4-SNAPSHOT] - 2026-03-11
π§ Fixed & Improved
- Legacy Minecraft Support (1.8-1.16): Resolved multiple critical issues for older server versions.
- Java 8 Compatibility: Fixed
NoSuchMethodError: String.isBlank()by replacing it with Java 8 compatible alternatives inMessageManager. - FastStats Isolation: Isolated Java 17-dependent metrics library to prevent
UnsupportedClassVersionErroron Java 8 environments. - JDBC Driver Fixes:
- Implemented explicit driver registration to solve "No suitable driver found" errors in shaded environments (PaperSpigot 1.8.8).
- Fixed
AbstractMethodError: Connection.isValid()by adding safety wrappers for legacy JDBC drivers (SQLite).
- Configuration Robustness:
- Fixed an issue where
config.ymlwas being stripped of content and comments on older Bukkit versions by reducing unnecessary saves. - Implemented explicit UTF-8 loading for configuration files to prevent character encoding issues on Windows servers.
- Enhanced configuration migration and initialization to correctly merge defaults without overwriting existing user settings.
- Fixed an issue where
- Stability and Performance:
- Fixed a race condition where default configurations were not being saved to disk before being reloaded during the first startup.
- Consolidated maintenance mode and version checking logs for better readability.
Optional dependencies
Any compatible version
Any compatible version
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:xIV08o16:I4yxiXk9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xIV08o16:I4yxiXk9"
}

