1.0.0.2
Compatibility
Changes
Changelog – EnderShare v1.0.0.2 ✔ New Features /ec unshare now requires the partner to be online and confirm the unshare action.
Shared EnderChests can still be broken with a left-click while maintaining proper enderchest sync.
GUI notification added for unshare requests (Accept/Reject).
Tab-completion fully supports all subcommands and online players. ✔ Improvements Enhanced /ec info to display plugin version, author, brief usage, and all available subcommands.
Fully stabilized shared enderchest syncing for partners. ✔ Bug Fixes Fixed errors related to UUID handling in shared inventories.
Corrected enderchest update issues when partners go offline during unshare.
Minor backend optimizations and code cleanup.
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:cYgdRLca:NCVY1bcf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:cYgdRLca:NCVY1bcf"
}

