Compensation for error code 10011
Comments
-
After this maintenance, my main account still encounters error 10011. I wonder if anyone has successfully fixed it.
I've pointed out that it might be due to cached data causing this error message. Please, I urge the official team to focus on fixing it in this direction rather than ignoring players. This issue is genuinely severe, and I request prioritized attention.
1 -
If any official personnel are monitoring this discussion forum, could you please inform me when this issue is expected to be resolved?
The number of players unable to log in is increasing. The official team should prioritize addressing this serious issue.
2 -
It's indeed unusual for a game to leave a portion of players unable to log in, especially with no resolution from the official team since the game's launch. This issue seems more severe than in-game bugs, and for a formally released game, it falls below expectations. The situation appears worse compared to PTCGO.
Absolutely, prioritizing the resolution of player issues is crucial for successfully managing this game. Continuous updates lose their value if players still face login problems. It's essential to address these issues promptly to maintain a balanced approach to game management.
1 -
Update :
Today, I finally successfully logged into the game. After entering the game, I deleted all my decks, around 300 in total. Since then, I've been able to log in smoothly every time.
If you have too many decks, you might need to wait until early morning in the United States (I succeeded at 2:00 AM) when server traffic is lower to have a chance to log in. Although I kept encountering error 10011, sometimes I could load to 36/41 and eventually successfully logged in.
I hope other players facing the same issue can resolve it as smoothly as I did.
1 -
Update: sadly it did not work, its become clear that whatever changed with the new update,the wifi couldnt keep up with it, I tried the 2am strat in the uk sadly didn't work, might try first thing in the morning instead....still remaining somewhat hopeful the dev team is actually looking into this...
0