[Quantum RPG] Restore bridge repair upon examining the bridge #186
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
This change hints to the user to examine the bridge to learn if it's broken. Examining the bridge effectively restores its state from previous sessions. Prior to this change, the state of the bridge would not get persisted in the save file, and the user (with the engineer) would need to fix it whenever it loaded the game back. This approach provides slightly better continuity, and is implemented within the constraints of the current framework.
|
(Fixes #178) |
dstrain115
approved these changes
Mar 12, 2024
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 change hints to the user to examine the bridge to learn if it's broken. Examining the bridge effectively restores its state from previous sessions.
Prior to this change, the state of the bridge would not get persisted in the save file, and the user (with the engineer) would need to fix it whenever it loaded the game back.
This approach provides slightly better continuity, and is implemented within the constraints of the current framework.