Cards get "stuck" in hand#386

This week and last week (so since 13.0 was released), our games have had a few cards get “stuck” in our hands - you can drag the card out of the hand but when released, it gets pulled back into the hand. The only fix we’ve found is to have the host clone the card and delete the buggy one. But it has returned even for cards that previously worked fine.

Hi there if you can figure out a way to reproduce these issue let me know!

@Knil : Any suggestions on what to do/look at/gather when it happens next time to help? It is super random and obviously I can’t save a game in that state since cards in hands don’t save that way.

https://kb.tabletopsimulator.com/getting-started/troubleshooting/

Is this still happening?

Unfortunately, yes - we played last night after the latest update and it happened to us twice. We haven’t spotted a pattern yet and it only happens once or twice when we play.

Interesting it is only with the host, I have only looked at this in single player. Do you know if the bug occurs with the following steps:

1. Card with decal is in hand zone
2. The host toggles into decal tool
3. Another player moves the decalled card to the table
4. Host toggles back to hand tool

Which is to say, does it happen when host changes to the decal tool, changes away, or both?

@Tymber, what you’ve outlined there is how we get around the bug usually (it’s a co-op game where hands aren’t hidden). When someone (host or non-host) can’t discard a card I will open up the decal tool (as the host) and then discarding works fine. I’m not sure if just anyone opening the decal tool is sufficient to get the card out of the hand, or if it must be the host.

Is there some way to track progress on this other than looking here?

I know there’s probably not much I can do to prioritize this bug fix, but I had to cancel a pitch I had with a publisher last week due to this bug creating a poor experience for my design. Some publishers are exclusively taking pitches through TTS this year, and my design is unfortunately at the mercy of this bug fix happening.

Hi! Came across the same problem, so the bug is still there. Thanks everyone for the diagnosis and workarounds. Looking forward to a fix :)