ON THIS WIKI
|This article is about BuildCraft's Assembly Table. You may be looking for TrainCraft's Assembly Table I, II or III.|
The Assembly Table is a BuildCraft 3 machine used to produce various redstone-related items such as Redstone Chipsets, Pipe Wires and Gates. The chipsets and gates produced with the Assembly Table can also be used in many recipes as a substitute for IndustrialCraft 2's Electronic Circuits and Advanced Circuits due to GregTech's behavior allowing these components to be used in this way. This behavior may be disabled in GregTech's configuration files. Additionally, it is possible to produce Applied Energistics's ME Basic Processor and ME Advanced Processor in the Assembly Table by enabling this behavior in the config file.
Assembly Tables do not directly use power, but needs to be partnered with Lasers in order to craft items. To work, the Assembly Table must be in a range of 4 blocks of the Laser. Multiple Lasers can be used to increase production speed. Still, it takes a considerable amount of time (and MJ power) to fabricate items. Consider using multiple Lasers and a Chunk Loader.
The Assembly Table allows gates to detect "Work Scheduled". Using this you can deactivate the Lasers' power source once the Assembly Table runs out of materials or recipes.
Items produced by the Assembly Table will pop out into the World. If a Chest or Transport Pipe is adjacent to the Assembly Table however, produced items will be placed in them.
Right-clicking on an Assembly Table will open the GUI. To the left is an area to put crafting materials. When it contains the materials needed to craft an item, the output item will be displayed in the right side. Clicking on items on the right side will mark them for production, clicking again will un-mark them.
If multiple items are marked for production, the Assembly Table will cycle through them. The item being produced will be highlighted in red and any queued items will be highlighted in a darker red.
Progress towards the item being crafted is displayed in the bar in the center of the GUI.
All these recipes require an Assembly Table with powered Lasers.
- Redstone Chipset - Redstone (10,000 MJ)
- Redstone Iron Chipset - Redstone + Iron Ingot (20,000 MJ)
- Redstone Golden Chipset - Redstone + Gold Ingot (40,000 MJ)
- Redstone Diamond Chipset - Redstone + Diamond (80,000 MJ)
- Pulsating Chipset x2 - Redstone + Ender Pearl (40,000 MJ)
- Red Pipe Wire x8 - Redstone + Iron Ingot + Rose Red (500 MJ)
- Blue Pipe Wire x8 - Redstone + Iron Ingot + Lapis Lazuli (500 MJ)
- Green Pipe Wire x8 - Redstone + Iron Ingot + Cactus Green (500 MJ)
- Yellow Pipe Wire x8 - Redstone + Iron Ingot + Dandelion Yellow (500 MJ)
- Gate - Redstone Chipset, Red Pipe Wire(20,000 MJ)
- Iron AND/OR Gate - Iron Chipset, Red Pipe Wire (40,000 MJ)
- Gold AND/OR Gate - Gold Chipset, 1 each Red & Blue Pipe Wire (80,000 MJ)
- Diamond AND/OR Gate - Diamond Chipset, 1 each Red, Blue, Green, & Yellow Pipe Wire (160,000 MJ)
Any gate can be upgraded to an Autarchic Gate with the gate, an iron chipset, and a pulsating chipset. e.g.: Autarchic Gold OR Gate requires 1 Gold OR gate, 1 Iron Chipset, and 1 pulsating chipset.
- Facade x6 - 3 Cobblestone Structure Pipe + appropriate block (8,000 MJ)
- Pipe Plug x8 - Cobblestone Structure Pipe (1,000 MJ)
There appears to be a visual bug with the GUI of the Assembly Table where, if multiple items are selected for production, it will cycle through them, as intended, however the vertical progress bar, and the item highlighted on the right of the GUI will not be updated when it cycles to the next item. This causes it to appear as if the table is only working on a single item. However, it does actually switch items. Ingredients for the actual active item will be consumed and the actual active item will be produced. If the items have different production times, the length of time that the progress bar advances will reflect the appropriate production time of the actual active item even though the percentage complete will not. (Observed in Mindcrack 8.3.2, BuildCraft 3.4.3, possibly fixed in later releases)