-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Priority Moves used in Psychic Terrain Display Incorrect Battle Text #5081
Comments
Does this occur in singles? |
This might not just be visual, if the grounded check is done on the user and not the opponent
|
Yes. From what I've observed it occurs in any battle type so long as there is psychic terrain. |
src/data/terrain.ts isMoveTerrainCancelled(user: Pokemon, targets: BattlerIndex[], move: Move): boolean {
switch (this.terrainType) {
case TerrainType.PSYCHIC:
if (!move.hasAttr(ProtectAttr)) {
// Cancels move if the move has positive priority and targets a Pokemon grounded on the Psychic Terrain
return move.getPriority(user) > 0 && user.getOpponents().some(o => targets.includes(o.getBattlerIndex()) && o.isGrounded());
}
}
return false; this block implies that the check for grounded happens correctly |
Visual OnlyPokeRogue.and.10.more.pages.-.Personal.-.Microsoft.Edge.2025-01-04.17-47-54.mp4Occurs in SinglesPokeRogue.and.10.more.pages.-.Personal.-.Microsoft.Edge.2025-01-04.17-48-38.mp4 |
…oves on Psychic Terrain
Describe the bug
Whenever a priority move is used in Psychic Terrain the text that displays afterwards says the Pokémon that used the priority move is protected by Psychic Terrain rather than the Pokémon being attacked.
Reproduction
Use any priority move in Psychic Terrain.
Expected behavior
In the example below the text reads "Wild Ariados is protected by the Psychic Terrain" after using Sucker Punch. I would expect the text to read either "Delphox is protected by the Psychic Terrain" or "Gallade is protected by the Psychic Terrain".
Screenshots / Videos
Psychic.Terrain.Text.Bug.mp4
Session export file
No response
User data export file
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: