FRLG grass_spin fix#1346
Merged
Mysticial merged 1 commit intoJul 27, 2026
Merged
Conversation
This file contains hidden or 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
2 participants
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.
The stand-in-place way to trigger grass encounters used to use the
BattleDialogDetectoras a backup check for entering a battle in case the black screen was missed for some reason, but due to its high tolerance and relatively few color checks it tends to trigger in other situations (white dialogues from repel ending, overworld areas with somewhat solid-color parts of the ground, fog in Pokemon Tower (?)).This switches it to the
AdvanceBattleDialogDetector, which will have fewer false positives.