Tags
Creators
Details
All versions
1.3.1
Release
Immersive Chests 1.3.15 months ago 13
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Fabric
Supported environments
Client-side
Required content
Unavailable version
Unavailable version
Changes
Fixed
- Fixed immersive camera failing for most workstation/container blocks.
- Fixed Ender Chests incorrectly reusing the previous camera target.
- Fixed stale camera context reuse after interacting with unsupported blocks.
- Fixed regression where only:
- Chests
- Barrels
- Chest Boats
- Chest Minecarts
continued functioning after resolver refactor.
- Fixed barrel targets being rejected by screen compatibility validation.
- Fixed incorrect barrel camera positioning caused by fallback/nearby target recovery.
- Fixed dispenser, dropper, furnace, smoker, blast furnace, and hopper block-face orientation flipping.
- Fixed generic container family compatibility handling for multiple container types.
Added
- Added immersive support for:
- Hoppers
- Hopper Minecarts
- Dispensers
- Droppers
- Added hopper GUI detection.
- Added dispenser/dropper GUI family handling.
- Added additional workstation and functional block target restoration after resolver rewrite.
Resolver / Architecture
- Refactored immersive target resolver pipeline.
- Restored deterministic block detection using:
- screen family validation
- world block resolution
- controlled fallback behaviour
- Improved separation between:
- screen detection
- block/entity target resolution
- camera orientation/yaw resolution
- Improved compatibility handling between:
- generic container screens
- dispenser/dropper screen families
- world-resolved block targets
Future Work
- Planned experimental support for automatic modded container detection using handled screens + nearby block entity resolution.
- Intended to support modded workstation/container blocks (e.g. Farmer’s Delight cooking pot) without requiring explicit hardcoded integrations.
Optional dependencies
Unavailable version
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:t4M26zkN:11aG2a4D"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:t4M26zkN:11aG2a4D"
}

