Pre game mulligan overlay doesn't appear on the right row of decks.
Closed this issue · 7 comments
The pre game mulligan overlay seems to not appear on the right row of decks. Left row and center row work as they should, but it's missing from the right row. See the screenshot below
To Reproduce
Steps to reproduce the behavior:
- launch game
- Click on Hearthstone
- Observe the mulligan overlay
Game mode
Hearthstone constructed, standard/wild/twist
Expected behavior
Mulligan overlay should appear over the right row of deck slots.
Version
2.7.0
Additional context
fullscreen, 2560x1440 resolution, high quality. Intel based iMac. Tabbing out and returning to Hearthstone makes no difference.
Log file
Interesting that the log shows 2 requests were sent. The first one contained 9 deck strings but the second contained only 5 deck strings and that seems to match the screenshot. How many decks are on your next page?
The next deck page does have 5 decks.
The reason I have it set to wild in the screenshot is that most of the decks I have right now are wild decks and if I have the game set to standard, the mulligan overlay disappears on the decks that are greyed out. I assume this is expected behavior.
Here's the funny thing though, if you notice, the top 3 decks are all standard, if I have the game set to standard, the right deck is still missing the mulligan overlay. It really seems like there's an issue with the right side. It overlay just doesn't show up on that row.
What happens if you reorder the decks in the Collection window? For example, move Sludge up to the 2nd deck and then go back to the Play window — does it now show the mulligan guide and the one for Plague is missing?
What happens if you reorder the decks in the Collection window? For example, move Sludge up to the 2nd deck and then go back to the Play window — does it now show the mulligan guide and the one for Plague is missing?
Yep, that's exactly what happens. No matter the order, the overlay doesn't appear for any decks on the right row.
I believe this will be fixed in the next version
I can confirm this issue is now resolved in version 2.7.5.
Thank you!
Thanks for confirming, closing.