Fix harmless errors on evac shelter computer #60831
Merged
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
github-actions
bot
added
[C++]
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.
Summary
None
Purpose of change
evaluteinteracting with computer terminal in evacuee shelter #60347Describe the solution
Inserted check and workaround process before the error arose.
Describe alternatives you've considered
Change the specification of
str_or_var<T>.Testing
Additional context
The process of starting with a evac shelter scenario and going to the refugee center is one of the most common playstyles.
I believe that beginners in particular will unconsciously select the evac scenario, because given that it appears at the top of the list of scenarios.
Therefore, I thought we should provide hot fixes to avoid such people being frightened by errors
as quickly as possible.