Direct cargo connections #516
Merged
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.
Allows cargo blocks to be directly connected to each other
The routing logic was already there and did not modifying. So the only thing required to make this work in the end was the visual component, and also making sure that the right events were being fired when two cargo blocks were connected. I did this with a slight hack, which is to make cargo blocks entity holders and then add an entity to one of the cargo blocks whenever two cargo blocks are directly connected. This also require extra logic to keep the displays in sync. Whenever a display is created, the PylonCargoConnectEvent is fired, and when a display is destroyed the PylonCargoDisconnectEvent is fired.