Skip to content
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

Shadows for all 'mons interact badly with trainerslide messages #5565

Closed
hedara90 opened this issue Oct 22, 2024 · 5 comments · Fixed by #6040
Closed

Shadows for all 'mons interact badly with trainerslide messages #5565

hedara90 opened this issue Oct 22, 2024 · 5 comments · Fixed by #6040
Labels
bug Bug category: battle-mechanic Pertains to battle mechanics status: confirmed This bug has been confirmed to exist in the codebase
Milestone

Comments

@hedara90
Copy link
Collaborator

Description

Discovered by Mystic Gohan on discord.
Tested and verified by hedara.

abyss.mp4

The shadow of the active 'mon will move over to the trainer sprite during a trainerslide, usually in the wrong place for the trainer.

Version

upcoming (Edge)

Upcoming/master Version

No response

Discord contact info

hedara

@hedara90 hedara90 added bug Bug category: battle-mechanic Pertains to battle mechanics status: confirmed This bug has been confirmed to exist in the codebase labels Oct 22, 2024
@hedara90 hedara90 added this to the 1.10 milestone Oct 22, 2024
@AsparagusEduardo
Copy link
Collaborator

Do we want to keep the milestone for this issue? #5632 already added a warning for this, and I can imagine that it's a small enough issue that it's non-blocking for 1.10's release.

@kittenchilly
Copy link

Didn't we disable shadows by default because of this though?

@AsparagusEduardo
Copy link
Collaborator

That's why I'm asking if it's a good enough of a patch to free a release. I'm still working on the script to migrate the chages from 1.9 to 1.10 in gSpeciesInfo and the current PRs, so this doesn't need to be decided now.

@Pawkkie
Copy link
Collaborator

Pawkkie commented Nov 10, 2024

I would absolutely agree that it's not 1.10 blocking, we wanted to have 1.10 out more than a week ago and I don't think delaying it for anything that isn't explicitly gamebreaking at this point is worthwhile.

@Pawkkie Pawkkie modified the milestones: 1.10, 1.11 Nov 25, 2024
@Pawkkie
Copy link
Collaborator

Pawkkie commented Nov 25, 2024

Removing from 1.10 milestone after senate vote

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Bug category: battle-mechanic Pertains to battle mechanics status: confirmed This bug has been confirmed to exist in the codebase
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants