Junction dont send items if next block doesnt contain/use items (such as walls or nodes) #11472
+2
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.



Why is this needed?
As seen in the images by default junction does not send items to the last junction in a chain, but it does if there is a different block at the end, regardless if it can use items to begin with (such as walls or nodes), thus increasing cost (items get stuck in that direction, unable to escape ever).
Of course you can make junction to not "clog" ever (see graphite junction schematic), but keeping that behaviour was important since it doesn't need that buff (you are incentivized to use inv sorter for that).
Before:
After:
Build used for testing:

If your pull request is not translation or serverlist-related, read the list of requirements below and check each box: