1.0.0+neoforge-1.21.1
Compatibility
Changes
Hender Chests
Hender Chests is a customizable storage solution for your Minecraft server, allowing players to create personal virtual chests with unique identifiers.
Features
- Fully configurable number of rows per chest (up to 6).
- Per-user/group limits on how many Hender Chests can be created.
- Quick-access your Hender Chests directly via chat using a custom prefix.
- Integration with LuckPerms for fine-grained permission control.
Quick Chat Access
Players can open their Hender Chests using a chat message that starts with the configured prefix (default: ..).
Example:
..mobdrops
Opens the player's Hender Chest named mobdrops (if it exists).
Configuration
The main config file is located at:
/config/HenderChests/HenderChests.json
In the config, you can set:
- Default number of rows (max 6)
- Default limit on how many Hender Chests each user can create
- Whether to enable LuckPerms support
Permissions
Hender Chests supports permissions for both regular users and admins.
Permissions follow this format (LuckPerms or any other compatible system):
General Permissions
| Node | Description |
|---|---|
hc.user |
Grants access to all user commands. |
hc.admin |
Grants access to all admin commands. |
Row and Limit Control
| Node | Description |
|---|---|
hc.rows.<INTEGER> |
Sets how many rows a user/group can create Hender Chests with. (Max: 6) |
hc.limit.<INTEGER> |
Sets how many total Hender Chests a user/group can create. |
Examples:
hc.rows.5→ Limits this user/group to 5-row Hender Chests.hc.limit.2→ Limits this user/group to 2 total Hender Chests.
User Commands (require hc.user)
| Node | Description |
|---|---|
hc.view |
View your own Hender Chests. |
hc.create |
Create a new Hender Chest. |
hc.delete |
Delete your own Hender Chests. |
hc.list |
List your Hender Chests. |
Admin Commands (require hc.admin)
| Node | Description |
|---|---|
hc.viewother |
View another player's Hender Chests. |
hc.deleteother |
Delete another player's Hender Chests. |
hc.listother |
List another player's Hender Chests. |
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:G87Nf62D:JmkTWy9z"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:G87Nf62D:JmkTWy9z"
}

