Repair group fixes #3806
Merged
Repair group fixes #3806
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
Such as telling the droid to do something else while it was going to repair.
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.
This PR fixes the repair group feature in a few ways:
Interrupting a droid going back to repair (or base) would leave the group number red forever until it was brought back to full HP. This is due to
droidWasFullyRepairedBase()not being called when breaking the droid out of the retreat-like order, and that might not be a good idea as it restores the group from therepairGroup, as well as updates the groups UI.Saves and loads a droid's
repairGroup, and theproductToGroupfor factories.