Fix long distance pipelines being very janky #2938
Open
+82
−37
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What
Automatically refresh the long distance network once every second while an endpoint hasn't been found.
Automatically refresh on invalidation.
Decouple meta machine block entity from long distance pipelines (unique capability getters).
Send block update when connection is established to refresh nearby manipulators.
Prevent insertion from non-input sides.
Outcome
Fixes #2907
Potential Compatibility Issues
Addons that implemented custom long distance pipelines will need to provide a proper implementation of the capability getters.