1.1.0
Compatibility
Required content
Changes
Parcel Workbench
Used to create and configure Parcels. Insert multiple encoded patterns, then define how many crafting requests should be submitted for each pattern. The patterns are not consumed.
Parcel Terminal
Connects to an AE2 network and executes a configured Parcel. Insert the Parcel and press Start to submit its stored crafting requests to the network.
The Parcel Terminal does not perform the recipes itself. The ME network must already contain the required patterns, Pattern Providers, machines, crafting CPUs, ingredients, and other normal AE2 autocrafting infrastructure.
Parcel
A punch-card-style item that stores the configured list of patterns and the number of crafting requests associated with each one. Parcels are reusable and do not contain ingredients or completed items.
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:3Ko6vaOI:D8zI3TRZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:3Ko6vaOI:D8zI3TRZ"
}


