This shows you the differences between two versions of the page.
| ae2_mechanics_autocrafting [2025/09/14 18:56] – created jack | ae2_mechanics_autocrafting [2025/09/14 19:27] (current) – jack | ||
|---|---|---|---|
| Line 4: | Line 4: | ||
| ^ Category | Storage & Automation | | ^ Category | Storage & Automation | | ||
| - | Autocrafting | + | Autocrafting |
| + | |||
| + | ^ Function | Description | | ||
| + | | Automatic Assembly | Items and fluids | ||
| + | | Export Automation | Crafted items can be sent directly into machines or inventories. | | ||
| + | | Stock Control | Networks can maintain set amounts of items in storage. | | ||
| + | | Extended Support | With addons, autocrafting can handle fluids, gases (Mekanism), and more. | | ||
| + | |||
| + | Autocrafting is complex, but once mastered it becomes one of the most powerful automation tools in modded Minecraft. | ||
| + | |||
| + | ---- | ||
| + | |||
| + | {{: | ||
| + | |||
| + | ===== How Autocrafting Works ===== | ||
| + | |||
| + | An autocrafting setup always requires **three core components**: | ||
| + | |||
| + | ^ Component | Purpose | | ||
| + | | Request Source | Player terminal, Export Bus, or Interface with a crafting card. | | ||
| + | | Crafting CPU | Manages the job, calculates ingredients, | ||
| + | | Pattern Provider | Pushes inputs into machines and accepts results back. | | ||
| + | |||
| + | **Process of a Crafting Job: | ||
| + | - A request is created (terminal / automation). | ||
| + | - The Crafting CPU calculates the required steps. | ||
| + | - Pattern Providers push inputs into machines: | ||
| + | - Crafting | ||
| + | - Processing recipes → Modded machines / setups | ||
| + | - Results re-enter the ME Network (via Import Bus, Interface, or Provider). | ||
| + | - Intermediate products are held in the CPU until needed. | ||
| ---- | ---- | ||
| ===== Patterns ===== | ===== Patterns ===== | ||
| - | * Craft **blank patterns** and encode them with recipes. | ||
| - | * Insert patterns into a **Pattern Provider**. | ||
| - | * Providers expose recipes to the network. | ||
| - | ===== Crafting | + | Patterns are encoded in a **Pattern Encoding Terminal** using blank patterns. |
| - | * When you request | + | |
| - | * If so, it automatically pulls inputs | + | ==== Types of Patterns |
| + | |||
| + | ^ Pattern Type | Function | | ||
| + | | Crafting | ||
| + | | Smithing Table | Encodes smithing recipes. Automated like crafting patterns. | | ||
| + | | Stonecutting | Encodes stonecutter recipes. Automated like crafting patterns. | | ||
| + | | Processing | Defines input → output, regardless of process. Works with machines, smelters, or full production chains. Supports batching (e.g., 8 cobblestone → 8 stone). | | ||
| + | |||
| + | ==== The Most General Pattern | ||
| + | |||
| + | ^ Method | Usage | | ||
| + | | Level Emitter + Crafting Card | Emits redstone to request | ||
| + | |||
| + | ---- | ||
| + | |||
| + | ===== Crafting CPUs ===== | ||
| + | |||
| + | Crafting CPUs are **multiblocks** that manage jobs. They must form a rectangular prism. | ||
| + | |||
| + | ==== Components ==== | ||
| + | |||
| + | ^ Component | Role | | ||
| + | | Crafting Storage | (Required) Determines job size. Sizes: 1k, 4k, 16k, 64k, 256k. | | ||
| + | | Co-Processing Unit | (Optional) Sends ingredients to multiple machines at once. | | ||
| + | | Crafting Monitor | (Optional) Displays active jobs. Can be dyed. | | ||
| + | | Crafting Unit | (Optional) Filler block to shape the multiblock. | | ||
| + | |||
| + | ==== Behavior ==== | ||
| + | |||
| + | ^ Feature | Details | | ||
| + | | Job Handling | Each CPU handles one job. Multiple jobs require multiple CPUs. | | ||
| + | | Intermediates | Stores items between multi-step recipes. | | ||
| + | | Request Sources | Can accept requests | ||
| + | |||
| + | ---- | ||
| + | |||
| + | ===== Pattern Providers ===== | ||
| + | |||
| + | Pattern Providers push ingredients to machines and handle returned results. | ||
| + | |||
| + | ==== Behavior ==== | ||
| + | |||
| + | ^ Rule | Details | | ||
| + | | Ingredient Handling | Inputs are pulled directly from the CPU, never stored in the provider. | | ||
| + | | Push Mode | Always sends all ingredients at once (no partial batches). | | ||
| + | | Output Handling | Results can be piped back into the same provider, saving channels. | | ||
| + | |||
| + | ==== Subnet Interaction ==== | ||
| + | |||
| + | ^ Interaction | Details | | ||
| + | | With Empty Interface | Provider bypasses the interface and injects straight into subnet | ||
| + | |||
| + | ==== Parallelization ==== | ||
| + | |||
| + | ^ Rule | Details | | ||
| + | | Multiple Providers | Identical patterns run in parallel. | | ||
| + | | Distribution | Providers round-robin jobs across connected faces. | | ||
| + | |||
| + | ==== Variants ==== | ||
| + | |||
| + | ^ Variant | Function | | ||
| + | | Normal | Pushes to all sides. Full network connection. | | ||
| + | | Directional | Pushes only to one side. No connection on that side (used for subnets). | | ||
| + | | Flat | Cable part. Multiple can share a single cable for compact setups. | | ||
| + | |||
| + | ==== Settings ==== | ||
| + | |||
| + | ^ Setting | Purpose | | ||
| + | | Blocking Mode | Prevents new batches if ingredients remain in machine. | | ||
| + | | Lock Crafting | Holds provider until previous result is inserted or under redstone. | | ||
| + | | Visibility | Can hide or show in Pattern Access Terminals. | | ||
| + | | Priority | Higher priority providers are chosen when multiple patterns exist. | | ||
| + | |||
| + | ---- | ||
| + | |||
| + | ===== Molecular Assemblers ===== | ||
| + | |||
| + | The **Molecular Assembler** executes recipes from patterns. | ||
| + | |||
| + | ^ Role | Function | | ||
| + | | Craft Execution | Runs Crafting, Smithing, | ||
| + | | Output | Auto-ejects results | ||
| + | | Pairing | Works best directly next to Pattern Providers. | | ||
| + | |||
| + | ---- | ||
| + | |||
| + | ===== Summary ===== | ||
| - | ===== Processing Patterns ===== | + | AE2 Autocrafting combines four parts: |
| - | * For machine-based recipes (furnaces, crushers, etc.), encode as **processing patterns**. | + | |
| - | * The system knows what goes in and expects the output to be imported back. | + | |
| - | ===== Parallelization ===== | + | ^ Component | Function | |
| - | * Splitting patterns across multiple providers allows multiple crafts to happen at once. | + | | Patterns | Define recipes. | |
| - | * Useful for mass production setups. | + | | Pattern Providers | Push inputs and receive results. | |
| + | | Molecular Assemblers | Execute crafting recipes. | | ||
| + | | Crafting CPUs | Manage jobs and intermediates. | | ||
| - | ===== Fluids ===== | + | This system scales from simple smelting to massive modded megafactories, |
| - | * Patterns also support fluid recipes. | + | |
| - | * Requires compatible machines or fluid interfaces. | + | |