All versions
1.10.0-beta
Beta
Logicore 1.10.0-beta2 months ago 2
Compatibility
Minecraft: Java Edition
1.21
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes

Beta 1.10.0
Release date: 2026-09-01
Stage: Beta
Summary: Okay, this is the storage remaster: Logicore now stores digital size instead of pretending every item costs the same.
Added
- One component-backed DSD with 64 MB, 128 MB, 256 MB, 512 MB and 1 GB capacities
- Storage Modules and deterministic N-to-N upgrades
- Digital Size tiers from 64 KB to 32 MB with data-pack tags
- The thin VSC Interface with automatic Both-mode access to chests, double chests, barrels and shulkers
- Physical-versus-digital source hints in the Data Terminal
Changed
- Modern storage capacity now uses binary KB, MB and GB instead of IP
- The Storage Drive Rack accepts both new DSDs and legacy IDDs
- SDFC rerouting now balances DSD contents atomically
- Jade and WTHIT now report DSD capacity and VSC state
- Old IDDs remain loadable and functional for existing worlds but leave modern crafting progression
Fixed
- DSDs can be inserted through the real Rack menu slots
- VSC arms and topology only connect through the outward connector side
- Double-chest VSC access is deduplicated and sees all 54 slots
- Data Terminal source hints preserve an item's existing lore
Removed
- Modern survival recipes for the five legacy IP-based IDDs
- The old assumption that every item consumes identical storage space
Known Issues
- The VSC crafting recipe is still waiting for a confirmed layout
- VSC 3x2 filters and Allow/Deny/Import/Export controls are intentionally deferred; 1.10 runs automatic Both mode
- No destructive automatic IDD-to-DSD conversion is attempted
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:AJmOFSPL:kFJ29MbR"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:AJmOFSPL:kFJ29MbR"
}

