Gameplay tips: Difference between revisions
m Add redundancy in manifold image description |
Filter comparison draft |
||
| Line 8: | Line 8: | ||
The reason this works is fairly simple: when a building is busy processing a shape or color, it will stall. The connected belt will eventually stall and balancers will output all items to the other side. Of course, the manifold approach is not a silver bullet: when using manifold designs, it is important to place the correct number of processor buildings to maximize efficiency. Additionally, the speed of balancers in such setups is limited to 1x, meaning it's impossible to use two inputs of the first balancer at the same time (assuming both input belts are full). | The reason this works is fairly simple: when a building is busy processing a shape or color, it will stall. The connected belt will eventually stall and balancers will output all items to the other side. Of course, the manifold approach is not a silver bullet: when using manifold designs, it is important to place the correct number of processor buildings to maximize efficiency. Additionally, the speed of balancers in such setups is limited to 1x, meaning it's impossible to use two inputs of the first balancer at the same time (assuming both input belts are full). | ||
== Built-in filter comparison == | |||
<!-- TODO: Add "main page"-like hatnote or block leading to filter page --> | |||
An easily overlooked feature of [[Filter|filters]] is their ability to directly test whether incoming items are equal to the connected [[Wires system#Signals|wire signal]]. Without this ability, a [[belt reader]] in combination with a [[Compare|comparator]] have to be used instead, significantly worsening reliability of filtering. Apart from exact equality comparison and boolean-triggered output selection, passing a null {{Signal|null|inline}} or conflict {{Signal|conflict|inline}} signal to the filter will block both outputs of the filter as if no wire was connected. | |||
Revision as of 23:27, 25 September 2026
Balanced vs. Manifold

Many players new to shapez often realize early on that providing a dedicated belt of resources to every single building becomes infeasible as production scales up. Using multiple balancers to join and split belts right next to extraction and processing units is a natural way to reduce the number of belts, however it is not always space-efficient and easily turns into spaghetti. This approach to routing is commonly called "balanced" or "parallel". Balanced routing can be helpful to significantly decrease item travel time in MAMs by avoiding slow alternation of balancer outputs, but doing it properly is extremely hard.
In most cases, using a manifold (aka serial) setup is easier and such a factory takes less space. A manifold is created by building a straight belt, then splitting off or merging into it as necessary by placing a balancer or one of its compact variants. One of the balancer outputs is then connected by a belt to the next balancer and so on.
The reason this works is fairly simple: when a building is busy processing a shape or color, it will stall. The connected belt will eventually stall and balancers will output all items to the other side. Of course, the manifold approach is not a silver bullet: when using manifold designs, it is important to place the correct number of processor buildings to maximize efficiency. Additionally, the speed of balancers in such setups is limited to 1x, meaning it's impossible to use two inputs of the first balancer at the same time (assuming both input belts are full).
Built-in filter comparison
An easily overlooked feature of filters is their ability to directly test whether incoming items are equal to the connected wire signal. Without this ability, a belt reader in combination with a comparator have to be used instead, significantly worsening reliability of filtering. Apart from exact equality comparison and boolean-triggered output selection, passing a null
or conflict
signal to the filter will block both outputs of the filter as if no wire was connected.