Inn Action Selection shows all cards in a tiny format that is difficult to use

Previous topic - Next topic

JunkDealer

As seen in the attached image the selection of Action cards with the Inn is problematic.

I'm playing on a 32" TV at 1920 x 1280 resolution via Chrome in full screen with all options set to No in game.

The action cards in the discard pile are tiny and very difficult to use properly without right clicking first.  The Action/Buy/Coin status overlaps these cards.  They also show all cards in the discard pile even though you can only select actions.  Perhaps an option to hide non-action cards here so that they will be easier to see/pick.


tufftaeh

There's one trick that might help a little: You can click on the Actions/Buys/Coins bar to make it disappear.
Unfortunately, this doesn't make the tiny cards bigger...

Watno

We have found a workaround that might help you until this is fixed:
1) Start a bot match, resign from that.
2) Go to Options and tab and toggle "Move kingdom and play area".
3) Start a bot match and resign from that.
4) Go to options and toggle the setting again.

This made cards in reveal areas show up in the proper size in all of our test cases so far, so hopefully it will help you as well.

(A proper fix is still coming obviously)

JunkDealer


Witherweaver

For Inn, couldn't we have only the Actions displayed, with an option to view the entire Discard pile?  They could still be kept separate as the order is not important.  There could be a Configuration option to 'always show discard pile' if you think you'll want to see everything every time, and 'show Actions separate' could be a toggle as well.

JunkDealer

Quote from: Watno on 06 January 2017, 12:10:57 PM
We have found a workaround that might help you until this is fixed:
1) Start a bot match, resign from that.
2) Go to Options and tab and toggle "Move kingdom and play area".
3) Start a bot match and resign from that.
4) Go to options and toggle the setting again.

This made cards in reveal areas show up in the proper size in all of our test cases so far, so hopefully it will help you as well.

(A proper fix is still coming obviously)

This workaround didn't work for me.  Any other suggestions?