Tags
Creators
Details
Licensed MIT
Published 3 months ago
Updated 2 days ago
All versions
1.19
Release
1.192 days ago 284
Compatibility
Minecraft: Java Edition
26.4-snapshot-5
26.3
26.2
26.1.2
26.1
1.21.10–1.21.11
1.21.8
1.21.4
1.21.1
Platforms
Fabric
NeoForge
Supported environments
Client-side
Changes
Added
- Added an Include / Exclude switch next to the container type chips. Excluded types are hidden from the results and remembered.
- Added a container icon next to the container name in the results.
- Added support for items inside shulker boxes. They show up in the results as "in <box name>" and point at the container holding the box.
- Added ender chest support. The ender inventory is listed once, on the nearest standing ender chest. Locating it highlights every ender chest you opened. If all of them were broken, the items stay listed with a "(removed)" tag and locating says so in chat.
- Added an "In shulker box" quick filter.
- Added
include:,exclude:,loc:,enchant:,inside:andis:to the search box, for exampleinclude:chest,shulker_boxorexclude:dropper. The start of a name is enough (include:che). - Added a highlight duration setting (5 to 300 seconds on the slider, up to 3600 typed in). Default is 60 seconds.
- Added typing a custom search distance by clicking the distance value.
- Added the size of the saved data to the Settings tab.
- Added a "View other server data" page in Settings. It lists every server and world with its containers, items and size, and lets you view or delete each one.
- Added a Discord button to the header and a Community card to Settings.
Fixed
- Fixed the "No container types" text overlapping the footer divider.
- Fixed menus that servers open on a right click (virtual chests, shops, plugin menus) being saved as the chest you clicked.
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:Zavp3bBd:sI9NnO3m"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Zavp3bBd:sI9NnO3m"
}

