Change global vars to local where appropriate #4774
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
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.
closes #4717
Description of changes
This PR changes some of the vars that were accidentally set as global to locals. The main reason is to avoid concurrent AI from getting incorrect values for various vars when they are running functions.
Test setup for the changes
Confirm that all vars that have been changed to local are valid.
Observe AI games, Sorian is the most impacted AI from the changes. But it impacts the normal AI as well. There are some edge cases where two AI would call functions and have the local vars overwritten by a global in the same file.