All reports
daybreak_displayed reports
#160894: "On the tablet I can’t see the description for challenge cards!"
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.
I play on a tablet, I like the raised difficulty of additional challenge cards, but the need to ‘hover’ over a challenge card to enable a description means I cannot access said descriptions on a tablet and have to guess/try to remember from the tabletop game, what the cards are. Surely a text box should be created by clicking on.
Many thanks• What is your browser?
Safari v17.1
Report history
10. Mar 2025 15:12 • Boomshanka247 • This suggestion has not been analyzed by delopers yet:
Use a tablet/phone instead of a laptop/PC
10. Mar 2025 15:20 • Kayvon • This suggestion has not been analyzed by delopers yet:
I tried it on a tablet this morning. It's working fine, though you do need to long press rather than hover.
It's also working fine for every other mobile player we've contacted. Mobile players constitute the majority of plays for Daybreak, making mobile players the rule rather than the exception. (In most comments, however, they still seem to feel they're a special exception despite this.)
If the behavior is different for you, it's important to understand what on your setup is different that you can't long-press the way everyone else can.
It's also working fine for every other mobile player we've contacted. Mobile players constitute the majority of plays for Daybreak, making mobile players the rule rather than the exception. (In most comments, however, they still seem to feel they're a special exception despite this.)
If the behavior is different for you, it's important to understand what on your setup is different that you can't long-press the way everyone else can.
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.
