Client Type (ex. PC, Android, Webclient): Webclient Client Version (if known. Webclient has no version.): When did you first notice the bug?: Dec 20th Have you been able to reproduce the bug?: Yes Information (include relevant logs, replays, screenshots): First of all, this bug was discovered by user @uri , who requested me to report in his place since he was tired. It's basically a display bug, whenever a Pokémon acquires a status problem, the label shows up normally, BUT, if this status problem CHANGES or gets REMOVED, the initial status problem label will either stay there, or change to any other status problem that the Pokémon acquires afterwards. Picture 1: As you can see here, my Blissey was poisoned, and the poison label showed up, for now everything is alright, then I proceeded to use Heal Bell and cure Blissey from it's poison, effect-wise it worked, but the label remained there. Spoiler Picture 2: In this second Picture there was something that Uri forgot to put but I still remember, I poisoned his Snorlax so it could lose HP and therefore use rest, which is why his Snorlax is shown sleeping, after it woke up it used Body Slam and instantly Paralyzed Blissey, the poison label now changed to PAR. But Snorlax's label stayed as SLP despite it woke up. Spoiler Picture 3: In this last Picture we can see Snorlax using Sleep Talk to allow Blissey use heal bell and cure itself from Paralysis, note that the Sleep label on Snorlax is still there, and when Blissey succeeds to heal itself from paralysis, the PAR label stayed there. Spoiler (If applicable) Sources to confirm the presence of a bug (ex. Smogon):
Is there any similar issue on the pc client? Or is this webclient exclusive? Sounds like a signal isn't connecting, and if a similar problem is on the pc client then it sounds like a signal is missing.
Tested, there's no issue with the PC Client, the changes are shown normally. Tested with PC Client on PC Client battle and PC Client on Webclient battle, only the Webclient one shows this issue, so It seems to be Webclient exclusive.
This issue has already been reported on Github, but it doesn't hurt to keep this thread open until it is fixed I guess.