Skip to content

Dark Dragon#13313

My feedback

3 results found

  1. 151 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Dark Dragon#13313 supported this idea  · 
  2. 55 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Dark Dragon#13313 supported this idea  · 
  3. unable to submit deck friendly play

    1,230 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Dark Dragon#13313 supported this idea  · 
    An error occurred while saving the comment
    Dark Dragon#13313 commented  · 

    Does anyone have a fix?

    An error occurred while saving the comment
    Dark Dragon#13313 commented  · 

    1. Give us the steps to reproduce the bug
    I get the error message "Network Error - unable to submit deck. Please try again later". This applies to any deck, any deck setting (historic, traditional, etc.) ONLY when I try to direct-match with friends. I am still able to match with randos.

    2. Note which platform you’re using (PC, Mac, Android, or iOS)
    Windows PC

    3. Enter the actual results you’re experiencing
    Not able to join a direct match with the above error being displayed.
    Direct challenge --> select deck --> challenge --> error code

    4. Enter the expected results of the feature
    Um, no error code? I should be able to direct-challenge friends

    5. Add any relevant screenshots/videos
    Attached screenshot of error thrown.

    6. If you found a workaround, please add workaround steps.
    No workarounds found

Feedback and Knowledge Base