Links
Tags
Creators
Details
Licensed MIT
Published 2 weeks ago
Updated last month
All versions
1.1.0+26.2
Release
Chest Shield 1.1.0+26.2last month 34
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Changes
Everything is configured from inside the chest now, and the mod no longer depends on owo-lib.
Updating from 1.0.0? You can delete owo-lib. Your chests keep their owner and their password.
Added
- Configuration inside the chest — a lock button next to the chest screen opens all the settings. Crouch + right click is free again, so you can place blocks and item frames against the chest.
- Permissions — give a player access and they open the chest like the owner does, no password needed. Offline players can be added too; they get access when they join.
- Protection switch — turn it off and the chest opens like a vanilla one. Breaking it and changing its settings stay reserved for the owner either way.
- Configurable hoppers — separate switches for putting items in and taking them out, both off by default. Works with Create, AE2 and Refined Storage when enabled.
- The chest title now says who owns it.
/chestshieldshows a chest's owner and settings, for the owner or an admin.- Carry On can no longer pick up a shielded chest.
Changed
- No more owo-lib. Fabric API is the only dependency.
- The guest password is simply set or not set, with a button to clear it.
Fixed
- Hoppers under a double chest only reached the half they were under.
- The two halves of a double chest were lit differently with a light source next to one of them.
- English players saw "This chest belongs to desconocido" when the owner was unknown.
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:UewZ9jZ0:rqtJ0ZOK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:UewZ9jZ0:rqtJ0ZOK"
}

