Tags
Creators
Details
All versions
1.0.2
Release
Cloud Storage 1.0.23 months ago 6
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Client and server
Required content
Unavailable version
Changes
Changelog
1.0.2
Added
- Added same-direction queue appends: new uploads or downloads can expand an already active transfer while keeping one restart-safe transaction, ETA, reservation set, Stop operation, and Cancel rollback.
- Added creative-style storage categories for All Items, Building Blocks, Natural Blocks, Ores & Materials, Food & Drinks, Tools & Utilities, Combat, Mob Drops, Cloud Technology, and Miscellaneous. The All Items view is grouped by category, and search filters within the selected category.
- Added a visible, draggable scrollbar to the 18-column, five-row virtual storage grid while retaining mouse-wheel scrolling and bounded server paging.
Changed
- Unplaced and re-mined Storage Uplinks now explicitly stack to 64; ownership and server-link identity continue to exist only while the block is placed.
- Storage categories now follow Minecraft's creative-tab membership instead of item-name fragments, with exact ore/material tags and deliberate food and mob-drop overrides.
- Cloud-to-local transfers now fill the 27-slot main inventory before using hotbar slots, keeping the hotbar free whenever capacity allows.
- While the storage search box is focused, ordinary keybind letters are consumed as text instead of closing the UI or opening another mod's screen. Escape still closes the screen, and Shift remains available for transfer shortcuts.
- Advanced the transfer journal to schema 4 for persisted append recovery and irreversible-withdrawal safety metadata; transfer journal schemas 1–3 remain readable.
- Storage Uplink blocks can now be stacked in the local player inventory as well.
Fixed
- Storage Uplink capacity now syncs as lossless 16-bit words instead of overflowing vanilla menu-data fields (for example, 54,000 displaying as 4,294,955,760), and its idle GUI now shows the linked server's calculated transfer speed instead of "Instant."
- Storage Uplinks can now be mined by their owner, including while automation has an item transaction in flight. Ownership is validated only by the authoritative server instead of an ownerless client-side block-entity copy cancelling every mining attempt; removal safely reconciles transactions and returns buffered items.
- Fully consumed upload stacks no longer finish as a false failed transfer with permanently reserved inventory slots; committed recovery finalization is idempotent and releases all resolved slots.
- Moving, spending, or trading already-delivered download items can no longer strand a transfer or enable rollback duplication. The transfer pauses immediately, permanently disables Cancel, and remains safely available through Stop, which commits exactly the delivered count and releases the untransferred reservation.
- Final withdrawal commit no longer attempts to reclaim items already delivered to the player, preventing inventory changes during other container interactions from producing a false failure.
- Storage category/search responses use isolated client page caches, so an out-of-order page cannot populate the wrong category.
- Fully consumed inventory stacks now finalize as empty after a successful upload instead of falsely entering recovery and leaving their slots reserved.
- Affected committed uploads retry their idempotent finalization once after loading, and genuinely unresolved recovery jobs remain visible with red reserved-slot borders.
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:b9sxAR2W:vSVzaAzV"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:b9sxAR2W:vSVzaAzV"
}

