All versions
0.1.6
Release
Explorer's Ender Chest 0.1.63 months ago 362
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Client and server
Changes
A big quality-of-life and polish update.
Added
- Config screen — via ModMenu (needs Cloth Config; both optional). Toggle
the unlock requirement, "remember open" state, recipe-book auto-close, sounds,
and animation speed. Also editable at
config/enderpocket.json. - Open from anywhere — bind a key in Controls and press it in-world to open your inventory with the panel already out.
- Sounds — ender chest open/close sounds when you toggle the panel.
- Slide-out animation — the panel now glides out from behind the inventory instead of popping in.
- Resource pack support — the panel auto-themes from your pack's own chest
texture, and the button is the vanilla ender chest item so it matches your
pack too. Packs can further override positions (
gui_layout.json) and supply a dedicated panel texture. See the README.
Changed
- The panel now always opens at full size. When the screen is too narrow, the inventory slides left to make room instead of anything shrinking.
- With active potion effects, the panel positions itself below the effect list so nothing overlaps.
- The button now sits inside the inventory's button row when there's space, and moves to the top-right corner when it's occupied (e.g. by other mods).
- Opening the panel auto-closes the recipe book for that inventory session. Re-open the book and it stays — the layout gently scales to fit everything.
Fixed
- Items no longer briefly missing for a few frames when the panel opens.
- The panel no longer peeks out from behind the inventory with some resource packs.
- Recipe-book auto-close no longer stops working for the rest of the session after you re-open the book once.
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:c6hQLvBw:5Av6RNNI"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:c6hQLvBw:5Av6RNNI"
}

