Links
Tags
Creators
Details
All versions
0.2.1+26.3
Release
AE2 Objects 0.2.1+26.31 hour ago 7
Compatibility
Minecraft: Java Edition
26.3
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Changes
AE2 Objects 0.2.1
Changes since 0.2.0.
Added
- Minecraft
26.2and26.3builds, alongside the existing26.1.2build. - Separate release jars for each supported Minecraft version, so players only install the jar that matches their game.
Changed
- Item and fluid housings now use distinct recipes:
- Item recipes use an amethyst block.
- Fluid recipes use a copper block.
- The housing centre remains empty for the storage component.
- All quartz glass in the direct-cell and housing recipes is now Vibrant Quartz Glass.
- NeoForge and Applied Energistics 2 versions are pinned per Minecraft version through the version catalog.
Fixed
- Added the 26.3 inventory/drop prediction API compatibility layer.
- Split the creative-menu clone hook between
AbstractContainerMenuon 26.1.2 andSlot.safeCloneon 26.2+. - Added 26.3 data-generation event support and advancement format conversion.
- Isolated 26.3 datagen output so it cannot overwrite the canonical 26.1 recipe data.
Notes
- The
26.2and26.3builds currently require Applied Energistics 2 alpha releases. - MEGA Cells
1m–256msupport remains disabled until a MEGA Cells 26.x build exists. - Applied Mekanistics chemical support remains inactive until an appmek 26.x build exists.
- Install only the jar matching your Minecraft version.
Full Changelog: https://github.com/Likos-Lupus/AE2Objects/compare/0.2.0...0.2.1
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:gsM3QPTf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:FFQXRXv7:gsM3QPTf"
}

