Links
Tags
Creators
Details
Licensed MIT
Published last month
Updated 3 weeks ago
All versions
1.0.6
Release
Hoardi v1.0.63 weeks ago 66
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.9–1.21.11
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
Safe on public servers
- Network owners: a network belongs to the player who placed its first shelf. Another player's shelf nearby starts their own network (even with the same wood), a shelf on someone else's chest is refused, and only the owner, trusted players and admins can open the network through its shelves or unload shulkers into it.
- New commands:
/hoardi trust <player>,/hoardi untrust <player>,/hoardi claim./hoardi infoshows owner and trusted players. - Networks from before 1.0.6 have no owner and stay shared. Servers among friends can keep everything shared with
settings.network_owners: false. - Claim and protection plugins are respected: if they refuse a click on a shelf, the chest behind it stays closed.
Fixes
- Closing a barrel now sorts the network like closing a chest
- A chest belongs to one network only, a second shelf on it just shows its contents too
- Breaking one of two shelves on a double chest no longer drops the chest from the network
- The automatic sort skips networks whose chunks aren't loaded instead of loading them
- Missing sections in config.yml fall back to the defaults
Quieter
- "Items sorted" appears in the action bar instead of the chat after every chest close
Cleanup
- Removed the settings that had no effect:
spatial.stack_height,spatial.spiral_direction,performance.items_per_tick
Paper, Purpur or Spigot 1.21.9 – 26.3, Java 21. Tested on Paper 1.21.9, 1.21.10, 1.21.11, 26.1.2, 26.2 and 26.3.
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:JH4klaTw:Ia9qLXi6"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:JH4klaTw:Ia9qLXi6"
}

