Routed Firewall Pipe: Difference between revisions
m (→Usage: Add a link to crafting (I meant to do this in the previous edit, but I forgot).) |
CraftSpider (talk | contribs) m (CraftSpider moved page Routed Firewall pipe to Routed Firewall Pipe: Capitalization standard) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 20: | Line 20: | ||
{{Crafting | {{Crafting | ||
|A1=Nether Brick | B1=Magma Cream | C1=Nether Brick | |A1=Nether Brick | B1=Magma Cream | C1=Nether Brick | ||
|A2=Magma Cream| B2= Routed Junction | |A2=Magma Cream| B2= Routed Junction Pipe | C2=Magma Cream | ||
|A3=Nether Brick | B3=Magma Cream | C3=Nether Brick | |A3=Nether Brick | B3=Magma Cream | C3=Nether Brick | ||
|Output=Routed Firewall | |Output=Routed Firewall Pipe | ||
|foot=1 | |foot=1 | ||
}} | }} | ||
| Line 36: | Line 36: | ||
*[[Routed Pipe Networks#Pull Routing|Pull routing]] can be blocked to disable items that the filter doesn't allow from being requested. Items will not be able to be pulled from one side of the pipe, even if there is another router broadcasting it on the other side. If this filter blocks a crafter from getting to its required ingredients, it will fail. | *[[Routed Pipe Networks#Pull Routing|Pull routing]] can be blocked to disable items that the filter doesn't allow from being requested. Items will not be able to be pulled from one side of the pipe, even if there is another router broadcasting it on the other side. If this filter blocks a crafter from getting to its required ingredients, it will fail. | ||
*[[Routed Crafting | *[[Routed Crafting pipe|Crafting]] can be blocked to disable items from being requested to be crafted from the other side of the pipe. | ||
*Controller access is currently unused. In previous versions, pipe networks required access to a special block, called a routing network controller, and would pull power from it. However, routing network controllers were soon removed. | *Controller access is currently unused. In previous versions, pipe networks required access to a special block, called a routing network controller, and would pull power from it. However, routing network controllers were soon removed. | ||
Latest revision as of 23:35, 13 May 2017
| Type |
Multipart Block |
|---|---|
| Physics |
No |
| Transparency |
Yes |
| Luminance |
? |
| Blast resistance | |
| Tool |
Any tool |
| Renewable |
Yes |
| Stackable |
Yes (64) |
| Flammable |
No |
| Availability |
Survival |
| First appearance | |
| Drops |
Itself |
| Name |
routed_firewall_pipe |
Routed Firewall pipes are a type of routed pipe that allow filters to be set for what items or actions can be performed through the pipe.
Obtaining
Crafting
| Ingredients | Crafting recipe |
|---|---|
| Nether Brick + Magma Cream + Routed Junction Pipe |
   |
Usage
The Firewall pipe provides a way to block certain items or actions that can be performed or accessed through a pipe. When items are being routed, routing will take into account the limitations of certain paths and route around blocked paths.
Each firewall has a list of items to accept or reject. On top of that, there are 4 specific things that can be blocked:
- Push routing can be blocked to prevent items that the filter doesn't allow from being pushed to potential destinations through the pipe. Pipes looking to send items on one side of the firewall will not discover the pipe that accepts the item on the other side.
- Pull routing can be blocked to disable items that the filter doesn't allow from being requested. Items will not be able to be pulled from one side of the pipe, even if there is another router broadcasting it on the other side. If this filter blocks a crafter from getting to its required ingredients, it will fail.
- Crafting can be blocked to disable items from being requested to be crafted from the other side of the pipe.
- Controller access is currently unused. In previous versions, pipe networks required access to a special block, called a routing network controller, and would pull power from it. However, routing network controllers were soon removed.
Note that path filters alter the results shown in the requests GUI in realtime. (As in, if an item cannot be requested or crafted through a firewall and get to the requester, it will not be displayed.)
GUI
|
1) Filtered items - These ghost copied items make up the filter for the pipe. 2) Blacklist/whitelist - This button toggles filtering mode between blacklisting and whitelisting. 3) Push routing - Sets whether or not push routing is blocked through the pipe. 4) Pulling - Sets whether or not pulling items from broadcasters is blocked through the pipe. 5) Crafting - Sets whether or not items can be requested to be crafted from a crafter through the pipe. 6) Controller access - Currently unused, but would change access to a power source called a routing network controller in previous versions. |
History
| Version | Changes |
|---|---|
| v4.3.6 (beta) | Added the Routed Firewall pipe. |
| v4.3.8 (beta) | Fixed item filter not being ghosted. |
Issues
Issues pertaining to "Routed Firewall Pipe" are maintained on the ProjectRed Github page. Report issues there.
