I just tried to solo an Alakazam and got murdered. The weather was not pro psychic. Has a changed happened to boost T3s?
Also shorty tried to solo a Porygon and failed tho she succeeded in the past.
Maybe it was a conncection/lag problem? I've successfully soloed PC/FS Alakazam three times out of four pretty easily, but the other time, I failed on four successive attempts with the same team that was easily successful before. The time I failed, the connection seemed poor, and the battle seemed to consistently start late and end early.
To your original question, I did an Alakazam and a Machamp today, and they didn't seem any harder than normal.
Sometimes, if I am attempting to solo a T3 raid boss, and I dish out a ton of damage with a particular Pokémon, that damage is replenished right after that Pokémon has fainted. Additionally, my other Pokémon will have either already fainted or taken heavy damage, even though I haven't even brought them out yet. That happened to me once during an Alakazam raid earlier today. I'm not sure if it's a change to T3 bosses. It might just be a connection/lag issue.
The raid boss health goes back up because the server didn't register the hit cuz of lag, connection issues, or general overall high ping. On your screen your pokemon got the charge off but there is ping that takes time to send and recieve info. So on the server side the charge move didnt get to completely fire before u fainted. If the interp on ur phone is close to the server, ur gameplay would be very skippy and laggy. Everything would not look smooth and look very choppy but everything would show when it actually registered. Its like a double edge sword. If niantic made the interp register close to the server, gameplay would be very laggy and choppy. That would make 99 percent of trainers complain about lag and not so smooth gameplay. Sometimes that one extra charge move that didn't register could be the difference between failing and passing.
I hate when that happens to me, soloed alakazam a week or two ago and beat it with around 26 seconds left. I would of beat it with over 30 seconds left if the last crunch registered. I personally haven't failed a t3 solo in months(except ninetales I tried for 40 minutes. Gave up afterwards and never attempted again as it has a lot of luck involved) but I do hate it when the charge move doesn't register when my Pokemon faints. It feels like im doing the perfect time attack on a raid boss about to beat personal best records but then charge move doesn't register when I faint. It's annoying but I'm glad the dodge glitch doesn't happen when doing t3 solos. That would ruin solos altogether for me. Alakazam is the only t3 solo I like to do now a days. Everything else is way to easy. Alakazam is easy too but at least I don't have around 50 plus seconds left on the clock.
What Alakazam FM
Psycho Cut is decent, but Confusion is hard
But if you already win consistenly, then it is likey not the selection of team attacker but the connection issue is the culprit, even if you start with good time (175-176 is good for me) the lag can still occur and make the solo attempt much harder...
