You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to dev_zero_guides/managing_items_with_pipes.md, there are four priorities of destinations:
passive suppliers
all itemsink modules plus basic pipes
terminus modules
default routes
However, by experimentation, this does not actually seem to be the case. In fact, an ItemSink module appears to have strictly higher priority than a Mod Based ItemSink Module, so priority (2) is at least two, and maybe more (once you consider all the different kinds of sinks), distinct priorities. This is good, because it allows you to establish one storage location for all items from a particular mod except for one or two items which you want to keep elsewhere; ItemSinks being higher priority than Mod Based ItemSink Modules means you can simply do the obvious thing (Mod Based ItemSink for the general case plus an ItemSink for the exception) and it works. However, the documentation appears to be wrong.
The text was updated successfully, but these errors were encountered:
correct. There are slight differences between the different item sink modules. It probably depends on how they are configured. I'll see if I can get a better explanation after having another look at the code.
According to
dev_zero_guides/managing_items_with_pipes.md
, there are four priorities of destinations:However, by experimentation, this does not actually seem to be the case. In fact, an ItemSink module appears to have strictly higher priority than a Mod Based ItemSink Module, so priority (2) is at least two, and maybe more (once you consider all the different kinds of sinks), distinct priorities. This is good, because it allows you to establish one storage location for all items from a particular mod except for one or two items which you want to keep elsewhere; ItemSinks being higher priority than Mod Based ItemSink Modules means you can simply do the obvious thing (Mod Based ItemSink for the general case plus an ItemSink for the exception) and it works. However, the documentation appears to be wrong.
The text was updated successfully, but these errors were encountered: