
Entangled Chests
Store items from anywhere. Entangled Chests adds a bundle you can link to a chest — anything you drop into the bundle is teleported straight into its linked chest, no matter how far away you are. Think of it as a personal chute to your base storage.
Tags
Creators
Details
1.1.0
Compatibility
Required content
Changes
Changelog
All notable changes to Entangled Chests are documented here. This project adheres to Semantic Versioning.
[1.1.0] - 2026-07-21
Added
- NeoForge support. The mod now ships for both Fabric and NeoForge from a single shared codebase, built with Architectury. Download the jar matching your loader.
Changed
- Architectury API is now a required dependency on both loaders.
No gameplay changes — mechanics, recipes and behaviour are identical to 1.0.0.
[1.0.0] - 2026-07-20
Initial release for Minecraft 1.21.11 (Fabric).
Added
- Entanglement Crystal — crafted from an echo shard surrounded by lapis lazuli.
- Entangled Chest — a single chest (27 slots) with a unique identity that bundles can link to. Placing one for the first time drops a bundle already linked to it. Name it on an anvil before placing to label it.
- Entangled Bundle — a real bundle that, once linked to a chest, teleports any
items placed into it straight into that chest.
- Link a bundle by right-clicking a placed Entangled Chest with it.
- Link as many bundles as you like to a single chest.
- Items can't be withdrawn from a linked bundle; if the chest is full they buffer in the bundle until space opens up.
- Breaking or picking up a chest unlinks every bundle tied to it — even for offline players.
- Tooltip shows the linked chest's name (or a short id).
- Enchantment glint on the crystal and chest (item and placed block), and on the bundle only while it is linked.
- Cross-dimension linking and persistence across world saves.
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:Tsbi2VwQ:fHMPTvMt"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Tsbi2VwQ:fHMPTvMt"
}
