You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a game finishes and kiosk receives the game over event, the game gets immediately exited to the "Game Over" screen in kiosk. This can be frustrating because a user then won't know if they won or lost the game, especially for games that don't have scores.
Here are two options for this:
Wait until a user presses a button to continue. The downside of this is that they might spam buttons and charge through the game over screens and can be a bit disorienting
Put a timeout for a couple of seconds when we receive the event before we trigger a "game over". This can work, but there could be some negative side effects if a user starts playing the game again and get abruptly taken out of the game playing experience. I experimented with this and having that timeout be two seconds could work well. To me, it seems like enough time to gather whether or not I've won and also doesn't give me enough time to try to play the game again. That said, this approach can still lead to varying experiences and that might be undesirable.
We'll likely want to discuss this more to decide the best direction here.
When a game finishes and kiosk receives the game over event, the game gets immediately exited to the "Game Over" screen in kiosk. This can be frustrating because a user then won't know if they won or lost the game, especially for games that don't have scores.
Here are two options for this:
We'll likely want to discuss this more to decide the best direction here.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A user should know whether or not they've won a game
The text was updated successfully, but these errors were encountered: