Tags
Creators
Details
Licensed ARR
Published last year
Updated 2 weeks ago
All versions
2.2.2
Beta
EnderChest 2.2.22 months ago 1,507
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
1.20.x
1.19.x
1.18.x
Platforms
Folia
Paper
Purpur
Spigot
Changes
Changelogs:
Added:
- Page counts are now remembered for offline players, so admin tools report the same number of pages whether a player is online or not. Live permissions always take priority while a player is online.
- On first startup after this update, page counts are restored automatically from existing chest data for players who haven't logged in recently.
/ec pageinfonow also shows the effective page total including pages granted by permission, not just admin-assigned ones.
Fixed:
- Critical: two separate item duplication exploits in the page system. Both allowed items to be multiplied through normal page switching. Updating is strongly recommended for all servers running with pages enabled.
- Switching pages could write a page's contents into the wrong page.
- A page that failed to load (for example when an item came from a temporarily disabled plugin) opened empty and overwrote the stored data on the next save. The page is now left untouched and the player is informed.
- Opening a page holding more items than the chest's current size silently destroyed the excess. Those items are now returned to the player, matching the behaviour when opening a chest normally.
- Chest size during a page switch was taken from whoever was viewing the chest instead of its owner, which resized shared chests incorrectly.
/ecsee <player> <page>only allowed page 1 for offline players while every page worked for online players.- Commands used during a page switch could open a second chest window and discard changes.
- Item search determined its page range from the searching player instead of the chest owner.
Removed:
- Nothing removed in this Update.
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:4mnCJWrg:1klK9O0J"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4mnCJWrg:1klK9O0J"
}

