Pokémon TCG Live 1.3.3 Update Discussion Thread
Comments
-
this is still beta right?
-
@Fr33Guy it still says global beta on the battle pass.
-
Please don't go there.
-
Needs a "Remember Log-in".
The card draw, or shuffle; still a bit bias, but slightly better than on old game.
Too Graphic Heavy! No way to switch-off Table Graphics; which really slow down Mobile devices, as of 07/03/2023, despite being told we could.
Log-off leaves you in a "limbo" (start) screen, instead of logging out altogether.
One heck of a nasty job loosing so many Top decks and really good cards because Pokémon didn't forewarn us about that in Migration. Despite the useful 2,000 bonus "Gems", I still haven't recovered my losses.
Some cards still don't show they can be used when they should: E.G. I just lost a round as 'Switch Cart' didn't light-up!
Cards like 'Blissy'. Aww, come on! You don't have to have any skills at all to play that card. Four Blissy and twenty energy, game over!!
On a +: Like the Daily Challenge encouragement to play 3 games without quitting. ;-) Also like that you can buy 1, 2, or 3 extra cards you need, providing you have the means.
-
@Professor_Bear I love how you refuse to spell "Blissey" correctly.
The makers of Live have no control over what cards are printed. But either way, Blissey V is a mediocre deck. You're playing a bad deck if you feel the card is broken.
-
Update on this:
- Update starts at 12pm and ends at 8pm CET.
- Battle Pass works.
-
The opponent permanently locks the match even if the timer ends it doesn't stop the match so you're forced to give up.
-
Hi there,
I have a problem when I try to log in to the game on my Windows PC.
It gives me a 10010 code error. Is this any "well-known error"? It only happens on my PC, I can enter using my android device, while I'm connected to the same WIFI network as the PC.
Is there any way to solve it?
-
Last updated prevents me from logging into the game on my PC. Says no internet connection every time. All the obvious tricks do not work. Any suggestions? Updated version March 31st, 2023, since then I keep getting the same error.
