Could you provide larger images? The ones here are so small that it's hard to make out any of the text.Hey, I'm mentioning this here because it's really the best place to put this.
I've been having issues with the Team Builder, it keeps giving my Pokemon the wrong move.
I had naturally assumed that I was the one at fault, but I caught the issue happening to my Salazzle's moveset just a few moments ago.
It wasn't just with Dragon Pulse, it happened with Sludge Wave as well. The issue kept happening until I removed all my moves and replaced them, as you'll see.View attachment 219877View attachment 219878View attachment 219879View attachment 219880View attachment 219881View attachment 219882View attachment 219883
Not a bug. Burn is still there if the pokemon turns into a fire type by any method.It seems I've encountered a bug with Galarian Darmanitan. Don't have an image, but I've got a replay.
Turns 18-19, Galarian Zen Darmanitan is still burned and still takes damage from burn, despite it being a Fire type.
Sounds like you have corrupted team data, it will not do anything so you don't lose your existing teams. If you send me your team data I can check and potentially repair it.When I click "Restore teams from backups" and paste something, the save button doesn't do anything.
Apparently it does delete all existing teams. I didn't know this earlier because I tested it without existing teams. Here's one paste that causes the save button to delete all teams.Sounds like you have corrupted team data, it will not do anything so you don't lose your existing teams. If you send me your team data I can check and potentially repair it.
Thanks for the answer, I just tested it in in Pokemon Sword, they did update it. Before the update you were able to use No Retreat multiple times but now you have get Mean Look or something like that to be able to repeat it.Although no retreat fails if used a second time under normal circumstances, it is possible to use it more than once without failing if falinks is trapped before the first use, as stated by bulbapedia: “If the user has already been given the "Can't Escape" status by another move such as Mean Look, No Retreat will successfully grant its stat boosts but will not create an additional status line to trap the user again. In this case, using No Retreat multiple times will create multiple boosts.”
Of course, this is all guessing that patch 1.1 in sw/sh didn’t change this. This may also need testing before implemented in order to answer questions like “if falinks is freed after using no retreat, will the falinks become trapped by no retreat immediately or will that only happen if no retreat is used again?”
This wasn’t actually a response to your report, it was a new bug report entirely. I probably should have specified that in the report...Thanks for the answer, I just tested it in in Pokemon Sword, they did update it. Before the update you were able to use No Retreat multiple times but now you have get Mean Look or something like that to be able to repeat it.
What about Decorate not going through Max Guard? :)
Dragon Darts working against a Fairy Type.
Clefable switched into a Dragon Darts and it did damage. Used it again and it worked again. No type changes or anything.
The issue was clefable was holding a ring target yes.
I'm unsure right now, it currently deletes all teams? Ok that needs to be fixed.Apparently it does delete all existing teams. I didn't know this earlier because I tested it without existing teams. Here's one paste that causes the save button to delete all teams.Do valid pastes need to have the === [format name] team name === at the top?Grubbin
EVs: 252 HP
IVs: 0 Atk
Visual bug - when calculating server side its using 70 but tooltips are 10 for some reason. I'll add this to my existing max move tooltips patch.
Something that I have noticed about protection and fail checks is that protection has priority over failing. This can be seen with last resort, (as shown in the replay) counter, mirror coat, etc. Though this is kinda weird and VERY annoying when you use a contact move that should’ve failed, it’s just how the game works. I might be wrong about this and protection SHOULDN’T have priority over failing, but I think that’s how sw/sh work too.