All versions
0.1.0
Release
ChestShare 0.1.03 months ago 8
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Server-side
Singleplayer
Changes
First release. Server-side only — nothing to install on clients, works with vanilla players.
Added
- Per-player instanced loot containers - Every world-generated container (chests, trapped chests, barrels, shulkers, dispensers, chest/hopper minecarts, and modded containers built on vanilla mechanics) gives each player their own copy of the loot. Same seed for everyone: two players opening the same dungeon chest see the exact same items, each in their own instance.
- Capture at chunk generation - Containers are registered the moment their chunk generates, whether they carry a loot table or were pre-filled with items by a mod (full NBT serialization, custom modded items included).
- Deposit support - Players can take and store items in their own instance; everything is persisted with the world.
- Automation blocked - Hoppers and pipes can neither extract from nor insert into shared containers.
- Natural breaking - Breaking a shared container drops the breaker's own instance and removes the container for everyone. Player-placed chests are never touched and keep vanilla behavior — including when placed where a shared container was destroyed (duplication-safe).
- Double chest support - Combined 54-slot screen, each half instanced and persisted separately.
- Admin commands (op level 2) -
/chestshare convert <pos> <loot_table>restores a single already-looted chest;/chestshare reset <pos>regenerates loot for all players. - Mass recovery for existing servers -
/chestshare export <file>and/chestshare import <file> [force]: regenerate a mirror copy of your world from the same seed, export every captured container, and import on the live server to restore chests that were looted before the mod was installed. The import runs progressively across server ticks (no freeze, watchdog-safe) and skips non-empty containers by default to protect player storage.
Notes
- Validated end-to-end on a live COBBLEVERSE (Cobblemon, Minecraft 1.21.1) server: 332 containers exported from a regenerated mirror, 241 restored on the origin server, non-empty containers preserved, no server stall.
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:6BCWQ9WC:FkeIDPu5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:6BCWQ9WC:FkeIDPu5"
}

