All versions
0.2.0-alpha
Alpha
Applied Packaging 0.2.0-alpha3 weeks ago 13
Uploaded by
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
Initial alpha release for Minecraft 1.20.1 Forge and Applied Energistics 2 15.4.10.
Added
- Fluix and 16 dye-colored package items with ordered AEKey contents, sparse layouts, canonical identity, capacity accounting, marker support, and stack-safe semantics.
- ME Package Assembler for local encoded patterns and AE2 Pattern Provider pushes.
- ME Packager for packaging and unpacking the connected ME network storage.
- Dedicated package and advanced-processing pattern carriers.
- Advanced Pattern Encoding Terminal with isolated advanced and package pages.
- Package Storage Bus and Package Unpacking Bus AE2 cable parts.
- Sequence Buffer X/Y/Z linear multiblock for ordered machine input.
- Color, marker, content, fuzzy, inverted, blocking, speed, capacity, redstone, and anti-clog controls.
- Optional JEI and EMI transfer with deterministic Create and GTCEu/Star Technology semantics.
- English, Simplified Chinese, and GuideME documentation.
- GameTest coverage for data, transactions, machines, buses, redstone, capabilities, patterns, optional recipe integrations, and sequence buffering.
Changed
- Package contents preserve order and duplicate positions instead of merging like storage inventory.
- ME Package Assembler input uses one generic AEKey inventory; item and fluid views are derived by AE2.
- ME Packager capacity follows one quarter of the matching AE2 storage-component tier.
- Advanced patterns support 81 package columns with 81 sparse positions per column while syncing only a visible window.
- Package Unpacking Bus resolves general targets through AE2's external-storage extension path and uses an atomic position plan for Sequence Buffers.
- JEI and EMI use separate public API frontends and share only viewer-neutral recipe planning.
- User-facing documentation now describes the current network-connected machine behavior and JEI/EMI integrations.
Removed
- Empty-package gameplay paths and recursive package nesting.
- Package Export Bus and the separate Package Pattern Terminal.
- Development-save, old registry, old carrier, and old NBT migration paths.
- Automated client screenshot/smoke runners, mock release fixtures, manifest/bundle generators, and process-history documentation.
- Obsolete PowerShell verification wrappers that duplicated no effective release gate.
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:NdkuU3xP:xf87g7CI"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NdkuU3xP:xf87g7CI"
}

