Note: I will be improving this guide over it's lifetime, such as reducing wordiness or including better images. Everything in this guide is accurate as of 0.148 (the changes from previous verions have mostly fixed bugs related to compute blocks but do not impact the core mechanics discussed here.)

As someone proficient with logistic blocks but entirely intimidated by compute blocks, I noticed a lack of any sort of walk-through on the subjects. There is an in-depth video guide on logistics blocks by Sampstra Games, however I had some issue accessing the video through steam. This guide will cover the basic function of logistics blocks, but if you would like to see some practical examples and problem solving, check the video out here:
https://www.youtube.com/watch?v=rGexXIUoeOM&t=14s
Or check out their channel here for videos on early access strategy games:
https://www.youtube.com/channel/UCksg1ApbNOYyxMmTcNKjwlg

To Sampstra, I hope you don't mind the plug, I did subscribe to your channel as compensation :)

In any case, I am now fairly confident in my abilities to use compute blocks, and I hope that this guide allows you to say the same.

This section will only cover the basic functions of Logistic blocks for now. While the game offers some straightforward instruction on how to use logistics blocks, these tools will be covered in the interest of being thorough. If you would like to see some actual designs using logistic blocks, check out the video by Sampstra linked in the Preface above.

Pretty much does what it says; will block all worker/item movement along a designated path/conveyor, respectively, while active. No filter.

Also self explanatory; designates a stop as an instant loading or unloading point for minecarts. No filter, but minecarts can be filtered.

No surprises; restricts movement along a path to a single direction. Useful when multiple transport units are operating on congested routes.

Will force filtered items from a conveyor into a buildings inventory or adjacent conveyor, but can get jammed if the destination is full.

Similar to a sorter, this block redirects filtered items to a building or separate conveyor but will allow them to pass through if destination is full.

Will pull filtered items from a target building onto a conveyor at any elevation the building occupies. Can even pull water from a well.

Diverts items onto adjacent conveyors or into adjacent buildings. Useful for allocating fuel between multiple buildings.

Prevents specified items from passing through. Acts as a blacklist (everything but this.)

Only lets specified items through. Acts as a whitelist (only this.)

Honestly, this is the real reason you came here. While the game offers some information about what these blocks do, many players will have a hard time figuring out how to actually use them in their factories. These blocks are covered in their cataloged order, with examples that become increasingly complex.

The primary interface between a user and a logic circuit. Alternates between an on (value of 1) or off (value of 0) output that can control multiple logistic or compute blocks, such as barriers or lamps, when supplied with any new input. Can also set other compute blocks states to active or inactive. To use, select the toggle, then right-click on the target block. The barriers below each open when their toggle is active and close when their toggle is inactive:

When active, detects how many items, filtered or otherwise, are present in a target block/buildings inventory, and outputs that number. To use, select the inventory sensor, designate a target building's offset by right-clicking (set to the first click by default), then right-click on the target block. In the world below, the top sensor opens the barrier when an item is in the silo and closes it when the silo is empty; the bottom sensor trips the toggle with each new item added or removed, opening and closing the barrier accordingly:



Note: the sensor can sometimes be tripped if an item passes through the block it is outputting to. This was difficult to replicate, so it's probably a rare occurrence, however it did happen when gathering screenshots.

When active, provides an on (1) or off (0) output to a block based on its set logic function and inputs. To use, select the bool block, then right-click on the target block:

• And Gate
  Outputs a 1 if all inputs are active; otherwise, outputs a 0:
  
  
  
• Or Gate
  Outputs a 1 if any of its inputs are active; otherwise, outputs a 0:
  
  
  
• Not Gate
  Outputs a 1 if any of its inputs are deactivated (i.e. a silo is emptied), and outputs a 0 if any of its inputs are activated (i.e. a silo receives an item):
  
  
  
• Nand Gate
  Outputs a 0 if all inputs are active; otherwise, outputs a 1:
  
  
  
• Nor Gate
  Outputs a 0 if any inputs are active; otherwise, outputs a 1:
  
  
  
• Xor Gate
  Outputs a 0 if all inputs are the same (i.e. all silos are empty or all silos have at least one item); otherwise, outputs a 1:
  

Similar to the inventory sensor, this block is triggered when an item, filtered or otherwise, enters or exits a tile, and gives an output of 1. Once triggered the output value will be constant, and the block must be reset, the means of which will be addressed later with the Logic Set Block. However an update will be sent with each item that passes. To use, set the target offset by right-clocking, then right-click on the target block.

A block that lights up whenever it has a positive input, and gives an output of 1. To use, set it as the output of another block, then, if necessary, right-click on the target block.

This block redirects its input as an output to another block without changing the targets activity or output. To use, set as the output of another block, then right-click on the target block. The circuit below is a basic detection system:



Here's how to make it, if you're following along:
First, the toggle on the lower left turns all blocks on or off, acting as a power switch (toggle to left set block, to And gate, and to agent trigger.)
The left set block runs into the upper toggle, which acts as a reset line for the trigger and lamp (toggle to lower set block and to lamp.)
The lower set block controls the agent trigger state, and has inputs from the reset toggle and the And gate.
The agent trigger detects items on the conveyor above it and sends output signals to the lamp and the upper set block.
The upper set block sets the reset toggle to on, meaning the system is primed for reset once the trigger is tripped.
The lamp only outputs to the And gate, acting as its second input.
The And gate outputs to the lamp while comparing the inputs from the lamp and power toggle, and both turns the lamp off when the power toggle is switched off and prevents the lamp from being switched on when the power toggle is switched on.

This block forces its target to send its output without modifying the block itself. In essence, the logic pusher makes the target block repeat its output without changing the state or the output. To use, set as the output of another block, then right-click on the target block. In the system below, a toggle is connected directly to a lamp, while a tripped agent trigger, also outputting to the lamp, is connected to a toggle via a logic pusher block. Even if the first toggle switches the lamp off, the second toggle forces the trigger to switch the lamp on again, even if nothing has tripped it:

A number display block that increments by 1 for every time it receives an input and outputs its stored value. To use, set as the output of another block, then right-click on the target block. In the setup below, the toggle to the left activates the counter while the toggle at the right end resets the counter:

A number display block that displays and stores the value of its input, and outputs that number. To use, set as the output of another block, then right-clock on the target block.


Note: this block does not store fractions or decimals. Saving the decimal part of a number requires the use of math blocks, which are covered next.

A block whose output is the result of a math operation on the value of its input to its stored value; for equation operations the output is 1 if true and 0 if false (i.e. 17 > 10 yields 1.) A value can be manually stored or automatically stored using a set block. To use, set as the output of another block, and right-click on the target number block. Below is storage readout using math blocks:



First, the inventories of all barns are added together and displayed in the center (the top pusher blocks are connected from their respective inventory sensors to the leftmost number block to force the system to update.)
Next, the circuit on the right activates lamps according to the sum's relation to the target value (200 in this case.)
Finally, the blocks at the bottom divide the sum into its respective digits and displays them on separate number blocks.

Note: the modulo function outputs the integer modulus (remainder) of a number after it is divided by the stored value. Thus, 145 divided by 10 is 14.5, whose modulo 10 is 4.5, or 4 (14.5 modulo 7 would be 0, since 7 divides 14 evenly with 0.5 remaining, which is truncated to 0.)

To save decimals, such as with 12 / 7, first multiply the numerator (top number) by some power of 10, like 1000. Performing the operation 12000 / 7 yields ~1714; by using the digit splitting technique shown above you can have some number blocks display the result as 1_714, where the 7, 1, and 4 are in the tenths, hundredths, and thousandths places, respectively.

A block that relays its input as an output, but only if the gate itself is activated by a logic set block. To use, set as the input of some desired output and of a logic set block, then right-click on the target block. The lamp below is dark since the gate through which an output is sent is closed:



Note: if supplied with 2 or more simultaneous inputs that aren't passed through a set block, the gate will relay all inputs, but in an unpredictable order. The block doesn't appear to favor inputs based on input value or the distance to, position of, or age of the input block.

A block that stores its input and, after a specified time delay, sends the value as an output, and can also be used as a clock to track factory production rates. To use, set as the output for the desired source block, then right-click on the target block. Below is a logic circuit that tracks items gathered per minute:



Thank you for your patience on this.

Only 1 toggle will be the input; connect this toggle to the pusher and the set block between it and the timer circuit, as well as of the timer blocks.
For the timer circuit connect the 4 outer tiles in a clockwise fashion, then the gate blocks into the center counter tile. Set the timers to 1, or 1 second.
Connect middle set block to the gate tiles.
Make the following chain: pusher > dummy toggle (leave off), dummy toggle > upper set block, set block > counter. This will reset the timer when you switch the circuit off.

The left circuit is as follows: agent trigger > counter, counter > x60 math block (conversion to minute), math block > division block, division block > number display (can be dissected as described in the math section.)
Now run the timer counter block into the adjacent set block, then the set block into the division math block.

Basically, the power toggle turns on the timers, which alternate powering each other on and off while activating the counter. The agent trigger line counts the items generated and defines this in terms of minutes. The division block then divides by the time and returns a rate.

Note: the timer block has a possible value of 0, which seems to match the frame rate of your computer (could be the tick rate, I'm not a tech guy), which will run faster if there's less going on to chew up cycles. I tried to make a timer that implemented this, however the rate was very unstable. It might still be useful, but this is beyond my expertise.

A block that relays its stored input if it is different from its current value, but not if it is unchanged.
To use, set as the output for the desired source block, then right-click on the target number block. Below is a timer that resets once the target time is reached:



Thank you for your patience.

Follow the timer circuit schematic in the previous section.
Create the following chain: Counter > math block (equals or greater/equal), math block > delta, delta > power toggle.
Finally run the set block from the reset line into the delta block.

The math block compares the timer with the target time in seconds (1 hour is 3600 seconds.) While this happens, the delta block is fed a series of 0's, which it stores but does not relay, since they are all the same input. Once the threshold is reached the delta block is fed a 1, which it sends to the power toggle, switching it and the circuit off.

Notice that the delta block is set at 1 for true, and if the timer is started up again it will be fed a 0, which will trip it again and disable the timer. For this we run in the reset line to change its value to 0 so that the series of 0's is unbroken upon restart.

I hope you were able to master both Logistic blocks and Compute blocks after reading this walk-through. If you have any constructive feedback or questions, feel free to address me below in the comments. Consider liking or adding to favorites if you found this helpful. :)

Also feel free to check out my guide on a compact 100 house hub for 0.144a.