Tags
Creators
Details
2.0.4-beta
Compatibility
Changes
-
Implemented a data locking system (
DataLockManager) to prevent race conditions between player join/quit, auto-saves, admin commands, and inventory close events. This resolves all known issues related to data loss, item duplication, and data overwrites. -
Fixed an issue where
/cec open <player>would show stale data for online players by prioritizing the live cache over persistent storage. -
Fixed a bug where changes made by an admin to an offline player's chest would not save correctly or would be overwritten upon the player's next login.
-
Fixed a server crash (
IllegalArgumentException: size 0) that occurred when a player without anycustomec.level.*permissions joined the server. -
Drop Support 1.20
-
Add lombok
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:AipGDIso:oJ6s57YJ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:AipGDIso:oJ6s57YJ"
}

