All reports
cuttle_displayed reports
#156999: "Don't wait for blocking action when confirmed it is not possible"
implemented: This suggestion has been implemented
1
What is this report about?
What happened ? Please select from below
Suggestion: in my opinion, the following would greatly improve the game implementation
Detailed description
• Please explain your suggestion precisely and concisely so that it's as easy as possible to understand what you mean.
Suggestion to not have to wait for the option of the opponent to block when you can confirm they do not have any option to block. In the case if they have no cards, or if I have an 8 used as glasses to see they do not have a 2 in hand. Or if they can see my cards with an 8 used as , they should not need to wait for me if they know I do not have a 2 in hand.• What is your browser?
Safari v17.6
Report history
8. Feb 2025 16:53 • mrfixsimmons • This suggestion has not been analyzed by delopers yet:
Don't wait for 2's if they don't have one.
8. Feb 2025 21:40 • PatrickDNerd • Developers agree that it is a good idea and intend to work on it:
I have this implemented, but not in all of the cases you described.
I still need to be careful to _not_ enable this when anybody else at the table cannot see the other players' cards (including spectators).
I will make some more improvements to this feature!
I still need to be careful to _not_ enable this when anybody else at the table cannot see the other players' cards (including spectators).
I will make some more improvements to this feature!
9. Feb 2025 2:37 • PatrickDNerd • This suggestion has been implemented:
Okay, I think I have this done. I cleaned up the logic to know when a player's hand should be visible to the whole table (including spectators), and I included scenarios for players without any cards in their hand, so there should be fewer interruptions when playing One-Off effects when it is common table knowledge that it cannot be blocked.
Add something to this report
Please add here anything that seems relevant to reproduce this bug or understand your suggestion:
- Another table ID / move ID
- Did F5 solve the problem?
- Did the problem appears several time? Everytime? Randomly?
- If you have a screenshot of this bug (good practice), you can use Imgur.com to upload it and copy/paste the link here.
