Skip to content

LIMachi#98557

My feedback

5 results found

  1. 39 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)
    LIMachi#98557 supported this idea  · 
  2. 18 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)
    LIMachi#98557 supported this idea  · 
  3. 64 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)
    LIMachi#98557 supported this idea  · 
  4. 85 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)
    LIMachi#98557 supported this idea  · 
  5. 373 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)
    An error occurred while saving the comment
    LIMachi#98557 commented  · 

    23rd of december, still getting the network error on Historic Brawl... Probably won't be fixed before next year...

    An error occurred while saving the comment
    LIMachi#98557 commented  · 

    Patch 2022.22.10.4411.977745 -> the save/network bug is still there in brawl

    An error occurred while saving the comment
    LIMachi#98557 commented  · 

    This affect all wastes, not just full-art ones (as been 3 days, and 4+ different bug report on this site, hopefully one will be seen by the devs and will be fixed before next year)

    An error occurred while saving the comment
    LIMachi#98557 commented  · 

    3 days in, still not fixed

    An error occurred while saving the comment
    LIMachi#98557 commented  · 

    Another related bug (client side): the network error is not correctly handled client side, as the deck list (when opened again after the error) will show wastes visually, but queueing with the list will use the previous version of the deck (in my case, with mountains instead of wastes)

    An error occurred while saving the comment
    LIMachi#98557 commented  · 

    Based on some comments on redit and other forums, this might be due to wastes not being seen as "basic" lands (and so unlimited amount in any historic format) as using the auto include lands feature with a colorless commander is not consistent (if no lands are present in the deck, 40 wastes are added, but adding non basic lands after will randomly change the amount of wastes in the deck, most of the time removing all of them)

    LIMachi#98557 supported this idea  · 

Feedback and Knowledge Base