Multiblock Logic for Multiple Recipemaps#263
Merged
TechLord22 merged 6 commits intomasterfrom Nov 26, 2021
Merged
Conversation
serenibyss
approved these changes
Nov 26, 2021
This file contains hidden or 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
2 participants
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.
This PR adds logic for allowing multiblocks to use more than one recipemap. TOP integration is also added, and all multiblocks with more than one recipemap are registered to all of their recipemaps' categories as catalysts. The implementation is very similar to the on in Gregicality, except implementing the selection logic is much simpler.
While the machine is running, switching the recipemap is disallowed, even when paused. When successfully switched, the multiblock will search for new recipes using the new recipemap.
Currently, a demo setup with the implosion compressor has been implemented. Before merging, this should be removed.