Topics

Game# 116555225 between myself and littlebird.
Had 3 bauble in hand, went to play treasures, the bauble selections would not show on screen.
Refreshing browser (firefox 109.0), undoing, playing treasures in different order - nothing helped.
Earlier in the game there were no issues with bauble from either player.

screen shot attached.

Naturally I forgot to write down the game #, but in the last game I played it seems that with both Warlord & Archer (either one) in play, when it came time to buy, the autoplay treasure dialog box never showed up, leaving you to click each treasure one-by-one.

I appreciate the ability to test-play the new cards against a bot before another player, but it would be nice if Lord Rat would actually purchase/play any of the new cards against us - so far I've played 3 straight bot games where the AI completely ignored the new cards (never even made use of the free starting favor).

last two games played (37320508 andd 37322069), after the winning card was bought, there was a slight lag, then the game reloaded back to the very start as if it hadn't been played at all.

Not sure the proper place to ask this, so here goes.  Also not sure if this is a software issue related to the game interface, or a hardware issue on my device.

Whenever a card is played that has a select and/or topdeck and/or discard option (think Harbinger, Sentry, etc), and the discard/card selection window pops upon, I have lost the ability to select/choose a card (mark with the X) using the regular touch screen interface.  No issues with the touch screen elsewhere in the game while this is happening: can still click on the action buttons (such as "do not discard/topdeck"), can still click in the chat and communicate using touch screen keyboard, can still "right click" by holding down on a card for a few seconds to pop up it's details, can still hover over player name and see cards on tavern mat, etc.  Only way to rectify, when a card choice is mandatory, is to either attach my keyboard and use the mouse/touchpad, or to temporarily disconnect and reconnect from a different device (laptop) prior to being timed out. 

Hope this all makes sense.  This is a fairly recent phenomenon, probably started within the last couple of weeks.

Using a Surface Pro 4 running Win10 Pro, up to date, and using Chrome.  Didn't pay too much attention to it at first, figured it was a Surface glitch & rebooted.  I've since replicated this problem in Firefox.  Any input is appreciated, thanks.