-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inbetween rounds/waiting for next player view #66
Comments
Not sure what you mean by this. In multi the players are always entering text or doing something and in hotseat it's the same someone is always busy filling in their guess/text. Only for multi is where I can forsee someone who sends their gif to the next person where they dont have anything to do, this is where the 10 seconds limit come into play, so they just wait for the timer to run out |
In hotseat it would be a screen that says something like "it's the next player's turn, click to continue" What do you mean by that limit? People have a time limit to enter their gif? |
You can do that in hotseat of course, but is it crucial? No, people will send the device over to the next person anyway and we can name the person who has to play each time on the screen so people know what's up. Again, hotseat shouldn't be and isn't the focus. There were two ways to keep the game moving: 10 second limit (or more/less) or constant refresh by user (dangerous, might hold up game if one person doesnt refresh). There are two cases (for multi):
The time limit is important so that everyone is moving along at the same time. |
In multiplayer: if it is not: |
I can see this being in hotseat. Basically a screen to make sure the new player actually gets situated before they start. It would be especially good if we're actually enforcing time limits. For multiplayer @JessicaNgo makes sense. Also if it's actually multiplayer, with everyone with their own active "game rounds" running, then the "multi_waiting.html" is especially important. In the chat I had mentioned that there's 2 things we can do with the waiting.html (assuming it refreshes itself every so often):
|
see #85 |
Part of #64 (This should've been part of hotseat too actually)
The text was updated successfully, but these errors were encountered: