Skip to content
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

Don't forcibly resign the Tsar if the resignation will cause the game to be paused #98

Open
zuzak opened this issue Mar 13, 2015 · 7 comments

Comments

@zuzak
Copy link
Contributor

zuzak commented Mar 13, 2015

If the game is going to be paused anyway, we may as well indefinitely extend the "decision round" and give the Tsar longer to decide, so that we don't waste the hand.

Vaguely related to #95.

@grifferz
Copy link
Owner

But players can't join once the game is waiting for the Tsar to pick a winner, so this would potentially stall the game forever if the Tsar never returns.

@zuzak
Copy link
Contributor Author

zuzak commented Mar 13, 2015

Blocked by #39.
On 13 Mar 2015 19:51, "grifferz" [email protected] wrote:

But players can't join once the game is waiting for the Tsar to pick a
winner, so this would potentially stall the game forever if the Tsar never
returns.


Reply to this email directly or view it on GitHub
#98 (comment).

@grifferz
Copy link
Owner

But #39 doesn't help either because all that asks for is that the new player be dealt in to the next hand. If the Tsar is never to be resigned then how do you deal with a Tsar that never returns?

@zuzak
Copy link
Contributor Author

zuzak commented Mar 13, 2015 via email

@grifferz
Copy link
Owner

Doesn't that result in exactly the same outcome, but more complicated?

Scenario 1: New player will join before turnclock expires

  1. Hand is completed but Tsar is absent.
  2. New player tries to join but can't because hand is complete.
  3. Tsar is resigned, hand is a bust, no one wins, game is paused.
  4. New player joins and game resumes.

Scenario 2: New player will join after turnclock expires

  1. Hand is completed but Tsar is absent.
  2. Tsar is resigned, hand is a bust, no one wins, game is paused.
  3. New player joins and game resumes.

Scenario 3: Like (1) but with this proposal implemented

  1. Hand is completed but Tsar is absent.
  2. New player tries to join and is told they will be dealt into the next hand.
  3. Tsar is resigned, hand is a bust, no one wins, game proceeds with new player.

Scenario 4: Like (2) but with this proposal implemented

  1. Hand is completed but Tsar is absent.
  2. Tsar would normally be resigned but because this would pause the game instead they are given longer.
  3. New player joins and is told they'll be dealt in to next hand.
  4. Tsar is resigned, hand is a bust, no one wins, game proceeds with new player.

It seems to me that in all cases the hand is a bust and waits for a new player to get it going again, and the only useful difference is automatically dealing a new player in to the next hand, which is issue #39.

@zuzak
Copy link
Contributor Author

zuzak commented Mar 14, 2015 via email

@grifferz
Copy link
Owner

Hmm, OK, I see your point. This does only seem to be an issue for the smaller game in #debug though. Perhaps we will see it as more of an issue when/if people start to get bored of the game.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants