Tags
Creators
Details
Licensed ARR
Published 7 months ago
Updated 5 months ago
All versions
2.3
Release
Container Limits + Swaps5 months ago 22
Compatibility
Minecraft: Java Edition
26.1.x
1.21.x
1.20.1–1.20.6
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
Added
- Added new
container-onlyitem action. - Added separate per-container storage limits for supported storage blocks.
- Added support for separate
container-onlyrules usingMATERIAL#container-only. - Added support for storage containers including chests, barrels, shulkers, hoppers, droppers, dispensers, furnaces, smokers, blast furnaces, crafters, brewing stands, decorated pots, chiseled bookshelves, jukeboxes, lecterns, and ender chests.
Changed
container-onlyis now fully separate from the normalcontainersaction.container-onlylimits now check the contents of the target container instead of the player inventory.- Normal item rules and
container-onlyrules can now use different limits for the same material. /itemlimiter listand/itemlimiter infonow display separate normal andcontainer-onlylimits when both exist.
Fixed
- Fixed
container-onlyrules being blocked by the “item already exists” error when the same material had a normal rule. - Fixed
container-onlynot applying to storage blocks like crafters and furnaces. - Fixed number-key inventory swaps being blocked while at the item limit.
- Fixed offhand swaps being blocked while at the item limit.
Notes
- Use
container-onlyto limit how many of an item can be stored inside each supported container. - Use
MATERIAL#container-onlyinconfig.jsonwhen the same item needs a separate storage limit. container-onlydoes not count bundle contents; it only counts plain item stacks inside the container.- The normal
containersaction still works separately and continues to limit taking items from containers into the player inventory.
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:4nl3owbf:nIpQFmBj"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4nl3owbf:nIpQFmBj"
}

