Links
Tags
Creators
Details
Licensed GPL-3.0-or-later
Published last year
Updated 6 days ago
All versions
1.2.6
Release
Create: Storage [Forge] 1.2.64 months ago 5,184
Uploaded by
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Required content
Any compatible version
Changes
1.2.6 - 2026-04-22
Changes
- Storage Boxes and Simple Storage Boxes will now always drop with contents intact when destroyed by an explosion, and are immune to any additional explosions.
Bug Fixes
- Fixed Feeder upgrade attempting to insert food remainder items (e.g. bowls, bottles) into slots other than item slots.
- Fixed item duplication when removing a Create filter from the Feeder or Magnet upgrade filter slot.
- Fixed Storage Box and Simple Storage Box not opening the GUI when sneaking with an empty main hand and a placeable item in the off-hand.
- Fixed Storage Box filter not being saved when the box is broken. [NeoForge]
- Fixed Simple Storage Box not setting its filter when the first item is inserted via automation.
- Fixed List/Attribute/Package filters being destroyed when breaking a Smart Passer or Filtered Storage Interface.
- Fixed Ore Mining upgrade suppressing XP drops from blocks. (#55)
- Fixed Ore Mining upgrade preview persisting when the player switches to a non-tool item while holding the preview key.
- Fixed EMI incorrectly reporting backpack ingredients as unavailable when opening the crafting table GUI, due to a stale client-side container cache.
- Fixed the bow/crossbow appearing to charge when the backpack is out of arrows. [NeoForge]
- Fixed a rare issue where disconnecting mid-draw could cause the next bow shot to silently consume an arrow from the backpack.
Optional dependencies
Any compatible version
Any compatible version
Any compatible 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:h6BAXuvn:z5LbIuGf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:h6BAXuvn:z5LbIuGf"
}![Create: Storage [Neo/Forge]](https://cdn.modrinth.com/data/h6BAXuvn/ab86c1c3dd555317a3ca9672a74101dd8ad43931_96.webp)

