Links
Tags
Creators
Details
4.1.0
Compatibility
Changes
Version 4.0.0 includes major database and synchronization changes. Please back up your database before updating.
Special thanks to @TobiBoyGitHub for reporting issue #8 and @muzaaqi for reporting issue #4 . Their reports were the main reason for the synchronization rewrite in 4.0.0.
This release contains all changes since version 3.7.6.
Version 4.1.0
improves the /mpb edit command and fixes several issues with online and offline player editing.
- Restored offline player tab completion.
- Improved inventory and player data editing.
- Added safer saving and additional validation.
Version 4.0.0
- Completely rewritten synchronization system for Paper and Folia.
- Added safer cross-server switching using player leases and individual session tokens.
- Player data is now saved as transactional snapshots to prevent incomplete or conflicting saves.
- Added a dedicated HikariCP connection pool. Database operations no longer run on Minecraft or Folia tick threads.
- Improved join, quit, reconnect, automatic save and shutdown handling.
- Failed saves are retried when possible and written to local recovery files if they cannot be completed.
- Reworked Vault economy synchronization.
- Fixed synchronization of custom namespaced advancements.
- Improved automatic database and legacy-data migrations.
- Updated commands, configuration files, translations and documentation.
- Added automated tests for the new synchronization and database systems.
Version 3.8.0
- Fixed plugin startup continuing before database migrations were completed.
- Added a join lock until the server, database and synchronization system are fully ready.
- Player connections remain blocked if startup or migration fails.
- Updated startup messages and the Chinese translation.
Special thanks to cityjd for the idea behind the startup join-lock system.
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:cYxXuksC:nmggTXbA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:cYxXuksC:nmggTXbA"
}

