Links
Tags
Creators
Details
All versions
0.2.0+26.1.2
Release
AE2 Objects 0.2.0+26.1.228 minutes ago 0
Compatibility
Minecraft: Java Edition
26.1.2
Platform
NeoForge
Supported environments
Client and server
Required content
Unavailable version
Changes
AE2Objects 0.2.0
Changes since 0.1.0+26.1.2.
Added
- Deep fluid storage cells for ME drives and chests, covering 1k through 256k tiers.
- Portable deep storage cells for items and fluids, covering 1k through 256k tiers.
- Portable-cell battery/menu integration, FE energy capability, charged creative variants, and Void upgrade support.
- Catalog-driven deep-cell registration with item and fluid channel bindings.
Changed
- Deep-cell storage was reorganized into domain, channel, persistence, inventory, and client-snapshot layers.
- Existing 1k–256k item cells keep their registry IDs, data components, and saved-data format.
- Deep-cell tooltips now use NeoForge's
RegisterTooltipAppendersEvent; family, UUID, capacity, partition, and portable energy lines are preserved. - Storage hot paths now cache total amounts, use bounded top-ten previews, encode and preview in one pass, defer filter/context creation, and fast-path nested-cell checks.
- Fluid cell colors were adjusted for the fluid series.
- Development artifacts include the commit hash; release artifacts use
ae2objects-0.2.0+26.1.2.jar.
Fixed
- Server cell context is resolved per thread; client and pre-server code no longer touches the server repository.
- Recovered cells are dropped when the player's inventory is full instead of being lost.
- Clone operations without a server context create an independent client-side identity without repository access.
- Saved-data snapshots are exposed read-only.
Internal
- Added Stonecutter-based builds, release packaging, CI build workflow, Dependabot configuration, and expanded documentation.
Notes
- MEGA Cells 1m–256m support is disabled in 0.2.0: no items are registered and no recipes are generated. It will be re-enabled once a MEGA Cells 26.1 build is available.
- Applied Mekanistics chemical support remains inactive until an appmek 26.1 build exists.
Full Changelog: https://github.com/Likos-Lupus/AE2Objects/compare/0.1.0%2B26.1.2...0.2.0
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:FFQXRXv7:MCYntNsV"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:FFQXRXv7:MCYntNsV"
}

