Friend Challenge Crashes
The Friend Challenge system seems to be broken. It takes multiple tries to get a friendly challenge to be successful. Some errors I've had include:
- When challenged, press accept challenge, pulls up select deck screen, select deck, press play, button becomes unclickable and challenge doesn't start
- When in deck select screen, press play, loop occurs with a pop up saying that if I leave the page the challenge will be canceled, and whether I press cancel or select deck, the pop up reappears until I log out and log back in
- Select deck and press play, takes a minute to load and when the game finally starts it produces an instant Draw
These issues have been occurring for me over the course of a week on PC and Android.
MrSkittles22#10332
shared this idea
-
FourTwenty#53956
commented
Ok the friend challenge issue where we can't issue friend or direct challenges.
I was attempting to look at my deck from the friend challenge menu and hit edit, it loaded a different deck. It led me to believe that maybe the game is trying to load decks in different locations on the screen. But if a deck is; for example; a deck i am working on but still lack all the wildcards i need to hit craft it has an error over the deck. Or if cards in a deck arent all legal for play type, they will "fail to submit deck". This being the case I think the issue lies in the deck selection screen not the challenge itself. I hope that helps you find d a fix because this issue has been going on for well over a year. I had this issue on pc and android. My friend I was trying to duel was on windows 10 pc and IOS. I don't have screenshots yet but I can repost them after work.
-
mrzoggy#12804
commented
When Challenging Friends from the main friend interface (lower left corner), if a Challenge is sent and the player moves away from the page, i.e. to Decks, then the challenge is no longer accessible and new challenges cannot be sent. There is no way to cancel the challenge at this point and the game must be restarted. Nothing seems to fix this particular issue and it presents itself on both Mac and Windows systems.