BuildCraft's machines in released source (1.4.1, 2.2.4, 3.1.2 and 3.2.2, 2011–2012)

BuildCraft 1.4.1, the first release (April 2011), adds five pipes (Wooden, Stone, Iron, Golden and Diamond), an Iron Mining Well and the Mining Pipe it lowers. The tag has no engines, oil or automatic crafting. buildcraft/first-pipes

Cited by: BuildCraft, Production chain

BuildCraft 2.2.4 (October 2011) has three families of pipe. Seven transport pipes carry items (wooden, cobblestone, stone, iron, golden, diamond, obsidian); five waterproof pipes carry liquids and are made from a transport pipe of the same material and a pipe sealant made of green dye; three conductive pipes carry energy and are made from a transport pipe and redstone. buildcraft/pipe-set

The waterproof set is wooden, cobblestone, stone, iron and golden; the conductive set wooden, stone and golden.

Cited by: BuildCraft, Fluid network

In 2.2.4 an item in a transport pipe travels to the pipe's center and there picks an exit: any side but the one it came in by that leads to a pipe carrying items, a machine that accepts them, or an inventory with room for it. With several, it takes one at random (single-player) or by a fixed hash of the item's id and the pipe's position (multiplayer). With none, the item drops out of the pipe into the world, and an item that reaches a full inventory drops what doesn't fit. buildcraft/item-routing

Bouncing back the way it came is allowed only where allowBouncing is set (L131), which no pipe here enables; a pipe's own hook can narrow the list (the diamond pipe's filter, the iron pipe's one open side).

Cited by: BuildCraft, Fluid network, Production chain

Items in 2.2.4 pipes move at a base speed of 0.01 block a tick. Entering most pipes takes 0.01 off any speed above that; a stone pipe takes off only 0.005. A golden pipe with a redstone signal sets an entering item's speed to 20 times the base, 0.2 block a tick, which the pipes after it then wear down. buildcraft/item-speed

{
 "baseSpeed": 0.01,
 "poweredGoldMultiplier": 20
}

Cited by: BuildCraft

With 2.2.4's default connection rules (pipes.alwaysConnect false), stone and cobblestone pipes don't join each other, and a golden transport pipe doesn't join another golden one. By 3.2.2 (December 2012) the golden pipe's rule is commented out. buildcraft/pipe-connections

The config comment at BuildCraftTransport.java L88 reads "set to false to deactivate pipe connection rules", the reverse of what the code does: true skips the rules. Why golden pipes refused each other, and when the rule went, isn't in the code.

Cited by: BuildCraft

In 2.2.4 the wooden transport pipe is the one that takes items out: powered by an engine, it pulls from one slot of the inventory it faces as many items as it holds energy, one item per unit and at most a stack, and puts them into the pipe. Blocks named in the config's woodenPipe.exclusion list, empty by default, aren't pulled from. It stores at most 64, and energy it hasn't spent drains, 64 a tick. A two-slot inventory gives from its first slot to a pipe above or below and its second to the sides; a furnace's top, bottom and sides give its three slots. buildcraft/wooden-pipe

Under the default pneumatic power framework the 50-tick latency is set to 0 (PneumaticPowerProvider.java L16-L22), so the pipe acts whenever it holds energy. If that framework fails to load, BuildCraft falls back to a redstone framework (BuildCraftCore.java L100-L106), not covered here. A special inventory (the automatic crafting table) answers through its own extractItem instead.

Cited by: BuildCraft, Production chain

In 2.2.4 an iron pipe lets items out by one side only; each change in the redstone signal it gets turns that side to the next one that faces a pipe, machine or inventory, skipping wooden pipes. A diamond pipe has nine filter slots for each of its six sides: an item goes to a side whose filter holds its kind (ignoring wear on tools), and only when none does to a side with an empty filter. buildcraft/iron-and-diamond-pipes

The diamond pipe's comment says a kind entered in several slots of one side makes that side likelier, since each match adds the side again before the random pick.

Cited by: BuildCraft, Production chain

In 2.2.4 a conductive pipe passes energy on in proportion to what each neighbor asks for, and loses 1% at every pipe it enters (0.1% in a golden one). A pipe that takes 1,000 or more from one side in a tick explodes. buildcraft/conductive-pipes

The wooden conductive pipe is where engines feed in (a power receptor storing up to 1,000, PipePowerWood.java L35); its own hook isn't read here.

Cited by: BuildCraft, Power network

BuildCraft 2.2.4 has three engines, and each pushes energy out only while it gets a redstone signal. The redstone engine makes 1 energy a second (every 20 ticks), only while powered, and stores 1,000. The steam engine burns solid fuel for 1 energy a tick (a piece of coal lasts 1,600 ticks, a lava bucket 20,000, wood 300) and stores 10,000; it finishes a piece it has started without the signal, but needs the signal to start the next. The combustion engine burns liquids, only while powered, and stores 100,000. An engine pushes its energy into the machine or pipe it faces in strokes, at most 1, 100 or 500 a stroke for the three, and its piston moves faster as its store fills. buildcraft/engines

The steam engine burns what Minecraft's furnace would through CoreProxy.addFuel for items not listed. Out of signal an engine loses 1 energy a tick (Engine.java L64-L71). The combustion engine's stages follow its heat, not its store (EngineIron.java L142-L154).

Cited by: BuildCraft, Power network

In 2.2.4 a steam engine whose store passes 10,000 explodes (range 4), and a combustion engine explodes (range 8) once its heat has passed 100,000, at the next energy it adds. The combustion engine heats by the energy it makes; while it runs it cools only on water, which holds its heat at 49,000 while the water lasts, at one unit of water per unit of heat above, and unpowered it sheds 10 heat a tick. The redstone engine adds its energy without the overflow check. buildcraft/engine-explosions

Cited by: BuildCraft, Power network

By BuildCraft 3.2.2 (December 2012) the engine's screen names the unit: output in "MJ/t" and the store in "MJ". The 2.2.4 code counts the same energy as a bare integer. buildcraft/minecraft-joules

Cited by: BuildCraft

In 2.2.4 oil is placed as the world is generated, chunk by chunk. A desert chunk has a 3% chance of a small surface pool (radius 3) on sand. Any chunk has a 0.2% chance of a medium deposit, a ball of oil of radius 4 to 7 centered at height 20 to 29, with a surface pool of radius 5 to 9 and oil filling the shaft between, and a 0.005% chance of a large one, radius 8 to 16, with a surface pool of radius 20 to 39 and a column of oil standing up to 30 blocks above the ground. buildcraft/oil-deposits

"Chunk by chunk" is ModLoader's generateSurface hook, which Minecraft calls once per chunk it populates; that call isn't in this source. A pool's radius is the reach of generateSurfaceDeposit, whose blocks are placed at a chance that falls toward the edge (L132-L140), so the radius is an upper bound. The medium and large rolls are independent; when both succeed, the large deposit's sizes are used.

Cited by: BuildCraft

The 2.2.4 pump lowers a tube to the liquid below it and, for 10 energy, takes up one block of it as a bucket's worth (1,000 units), removing the block from the world, then pushes the liquid into an adjacent tank, pipe or machine that holds liquids. A pumped deposit is used up. buildcraft/pump

Cited by: BuildCraft

The 2.2.4 refinery has one recipe: one unit of oil into one unit of fuel for 10 energy, at most one unit a tick, so a bucket of fuel costs 10,000 energy and at least 1,000 ticks. Its two input tanks and its output tank hold four buckets each. buildcraft/refinery

{
 "oilIn": 1,
 "fuelOut": 1,
 "energy": 10,
 "delayTicks": 1
}

Cited by: BuildCraft, Production chain

In 2.2.4 the combustion engine makes 5 energy a tick on fuel, 2 on oil and 1 on lava. Each unit burns for 1 tick plus the fuel's burn time over 1,000, which comes to 255,000 energy a bucket of fuel, 22,000 a bucket of oil and 3,000 a bucket of lava. Refining a bucket of oil costs 10,000, so the refinery multiplies the oil's worth in the engine more than tenfold. buildcraft/combustion-fuels

{
 "fuel": 255000,
 "oil": 22000,
 "lava": 3000
}

The products are this set's arithmetic on the cited lines, not figures BuildCraft states. Engine output is still capped at 500 a stroke and heat limits a run without water (engine-explosions).

Cited by: BuildCraft

By 3.2.2 (December 2012) the values have changed: the combustion engine makes 6 energy a tick on fuel (burn time 100,000), 3 on oil and 1 on lava (20,000 each), and the refinery takes 12 energy a unit. buildcraft/fuel-values-3-2-2

Cited by: BuildCraft

In 2.2.4 a quarry with no landmarks marking an area digs a default box 11 blocks square and 5 high, set beside the quarry on the side opposite its face. It first builds a frame around the box (25 energy per block placed or cleared), then digs out the 9 × 9 inside. Landmarks give a box of their own, at least 3 × 3, raised to 5 high if lower. buildcraft/quarry-area

Cited by: BuildCraft

In 2.2.4 the quarry digs from the top of its box down, a layer at a time in a back-and-forth sweep, always taking the highest block left. It passes over air, water and snow, and a column that reaches bedrock or lava is closed below. Each block goes into an adjacent chest if there is room, else into an adjacent pipe, else it is thrown up into the air from the quarry. The arm's travel is what costs energy: each tick 2 plus a thousandth of the store, moving faster the more it spends, out of a 7,000-energy store. buildcraft/quarry-digging

{
 "maxEnergy": 7000
}

The thrown item leaves from the quarry block's own position with an upward kick (L376-L391). The 3.2.2 changelog's first line is a rewrite of this search ("Refactored quarry algorithm for efficiency to reduce CPU usage", buildcraft_resources/CHANGELOG.txt L3-L4), not read here.

Cited by: BuildCraft

The 2.2.4 Automatic Crafting Table holds a 3 × 3 pattern and crafts one result each time a pipe pulls from it. A slot with more than one item gives one; a slot down to its last item keeps it and takes one from an adjacent chest or other plain inventory instead, and if none has it the table crafts nothing. Items piped in go only to slots already holding that item, the emptiest first. It needs no power of its own; the wooden pipe pulling from it does. buildcraft/auto-workbench

Cited by: BuildCraft, Production chain

BuildCraft 3.1.2 (January 2012) has seven gates, made on the assembly table from a redstone chipset (and pipe wire, above the plain Gate) and fixed onto a pipe: the Gate (one trigger and action), Iron AND and OR Gates (two), Gold AND and OR Gates (four, with a parameter each) and Diamond AND and OR Gates (eight, with parameters). The assembly costs 20,000 energy for the Gate, 40,000 for iron, 80,000 for gold and 160,000 for diamond. buildcraft/gates

Cited by: BuildCraft

In 3.1.2 a gate pairs each trigger with an action. Pairs that name the same action are combined, with AND on an AND gate and OR on the others, and each action whose result is true fires: a redstone signal out of the pipe, a signal on one of the four pipe wires, or a command such as on, off or loop to the machine next to the pipe. Triggers read the pipe (empty, items, liquids, energy, a wire signal on or off), an adjacent inventory or tank (empty, contains, has space, full), a machine (active or not), redstone in, and an engine's heat stage. buildcraft/gate-logic

Cited by: BuildCraft

In 3.1.2 a pipe can carry any of four wires, red, blue, green and yellow, each a separate signal. A gate sending on a wire sets it to 255 in its pipe; each pipe takes the strongest of its wired neighbors less 1, so a signal fades out about 255 pipes from its source, and spreads only through pipes that carry the same color. buildcraft/pipe-wires

Cited by: BuildCraft

BuildCraft 2.2.4's oil chain is short: a pump lifts oil block by block out of a deposit it empties, the refinery's one recipe turns oil into the same amount of fuel, and the combustion engine burns the fuel for energy. Factorio 2.1.23's crude oil is an infinite resource a pumpjack draws from a well; the refinery's basic recipe makes petroleum gas alone, its advanced recipe splits crude oil and water into heavy oil, light oil and petroleum gas, and cracking recipes in the chemistry category, which the chemical plant runs, turn heavy oil into light oil and light oil into gas. buildcraft/oil-vs-factorio

Factorio's side is the factorio-production set's claims (crude-oil, oil-refining, cracking-and-chemistry). In February 2013 kovarex said he liked BuildCraft's oil concept and wanted processing "as in build craft" without copying it completely (factorio-lineage/buildcraft-oil); which parts of the shipped chain follow from that isn't stated by Wube.

Cited by: BuildCraft, Production chain