Candidate fix for #5417 NPE Freeze bot moves invalid or nonsense. #5430
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.
Fixes #5417
Moved
processGameEvent()
back intosetPhase()
where it was.setPhase()
gets called from places currently thatreceivePhase()
doesn't get called from. It looks like this was pulled out as a refactor but has un-intended side effects for the bots processing.Before making this tweak, I was able to easily reproduce the NPE by running a bot vs bot as described in #5417. After this change, the bot games end naturally after 15 to 25 rounds. Before this tweak, the same bot games would either end in a NPE or infinite mindless bot moves that would go into over 100 rounds.