Favorite Card Back bug

Selected card back does not always appear when playing ranked ladder matches. Instead, the standard/generic, classic card back appears. Have tried switching from various card backs and the problem still exists.

1 Like

it will be helpful to include in your post what device you play from

have you restarted the game?
have you logged out and back in?
have you re-installed the game?

You may need to open the deck for the hero you wish to use your favorite card back with, go to the cardback screen, then left click and drag the cardback you want to use over / onto the currently assigned cardback.

Favorite cardbacks are just a default for newly created decks. They only automatically apply to newly created decks if those decks are created after the favorite cardback is designated.

They don’t automatically apply to decks which were created prior to the favorite cardback being designated. In these cases, they have to be specifically assigned to those decks (in the method mentioned above).

-Valas

It has happened to me recently too, it doesnt matter whether i play on pc or mobile, whenever i hop on the game my “favourite” card back always goes back to the basic one, I’ve checked in the collection every single time if thats the case just to make sure and it was.

1 Like

I have issue in all forms of gameplay on all platforms. The issue only started when free dancing lion cardback was “purchased”. After a bit of experimenting it appears that the reset glitch only happens if your favorite is either Dancing Lion or a newly shop bought cardback OR whatever your favorite was when Dancing Lion ( or maybe any new store cardback?) was acquired (my old favorite was NOT a recently purchased cardback, had it for a while…, Welcome Inn ) If I set any other cards as favorite then it doesn’t change back to the classic cardback but if I choose either Dancing Lion OR a new shop cardback OR my old favorite then it resets every relog back to the classic cardback.

1 Like

Anyone know if this issue has been fixed yet or anyone found a work around for the time being?

been having the same exact problem for the last couple of days

Been having the same issue, and it seems they’re aware of the issue but don’t care to get around to it.