Tags
Creators
Details
All versions
1.0.3
Release
Cloud Storage 1.0.33 months ago 10
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Client and server
Required content
Unavailable version
Changes
Changelog
1.0.3
Added
- Added a Drive Transfer mode to the Electronics Workbench alongside the existing Data Recovery mode.
- Added selective quantity transfers, a removable transfer queue, source-content pagination, and a prominent Move All action for direct drive-to-drive moves.
- Added live source/destination drive status and used/total/free capacity information, plus committed-count progress, current item, completion, cancellation, and destination-full states.
- Added an independent, persistent Workbench transfer journal with idempotent destination-first batch reconciliation for safe reload, interruption, cancellation, and replay.
- Added a detailed website item encyclopedia covering every registered item and block-item, with purpose, behavior, properties, acquisition, production uses, Technician trades, and related entries.
- Added a searchable website recipe book generated from the mod's production data, including Minecraft-styled semantic nine-slot crafting tables, real mod and vanilla ingredient textures, and dedicated smelting and blasting layouts.
Changed
- Workbench drive moves run at 64 items per tick without using Cloud Server CPU, RAM, PSU, cooling, transfer lanes, or CPU durability.
- The Electronics Workbench now persists a backward-compatible destination-drive slot; existing two-slot Workbench saves remain readable.
- Active Workbench transfers lock only their source and destination drive slots. Closing the UI or disconnecting does not stop a loaded Workbench, while unloaded chunks pause it safely.
- Updated the Cloud Storage website and documentation for version 1.0.3 and the new Drive Transfer workflow.
Fixed
- Electronics Workbench Move All now refuses a source drive with items reserved by another transfer instead of silently moving only the unreserved subset, reporting success, and leaving a seemingly unusable stack behind.
- Electronics Workbench drive cards now show the exact reserved-item count, disable every start path while another transfer owns source items, and stop showing an old completed receipt after either drive is removed.
- Reworked both Electronics Workbench tabs with aligned drive/tool cards, centered recovery controls, a compact two-row item browser and queue, clearer paging, and a dedicated transfer notice line so text no longer overlaps item icons.
- Recovery-required transfers now remain visible in every Active Transfer screen with a working Stop button; legacy partially delivered withdrawals are migrated to Stop-only instead of being mislabeled as terminal failures.
- 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; removal safely reconciles transactions and returns buffered items.
- Workbench Drive Transfer safely preserves already committed items and leaves all pending items on the source when cancelled, interrupted, or stopped by a full destination.
Compatibility
- Minecraft Java Edition 26.2, Java 25+, Fabric Loader 0.19.3+, and Fabric API 0.156.0+26.2.
- Existing server registry schema 1, drive schema 3, and transfer journal schemas 1-4 remain readable. Workbench transfer journal schema 1 is additive and independent.
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:QjU4hPMn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:b9sxAR2W:QjU4hPMn"
}

