Andrew Plotkin | 4 Jul 06:33

Re: Standing in the middle of a game

On Sun, 3 Jul 2005, Jason McIntosh wrote:

> I don't think we ever talked about what happens when a player tries to
> stand up while a game is active.

I mentioned it in a post at one point, I think.

> I see three ways to handle this:
> (1) The ref simply shoots down the idea. The player remains seated.
> And likes it.
> (2) The ref allows the player to stand. If this causes the player's
> seat to become unoccupied, the ref begins its user-departure
> countdown, exactly as if the player had abruptly left the table
> altogether.
> (3) As above, except that the ref _immediately_ suspends the game,
> resuming it when all seated players voice readiness, exactly as per
> the "suspend" timeout reaction defined on [[user departure]]. It will
> suspend the game even its its timeout reaction is set to "bot" or
> "throw", since overturning the table the instant a player stands seems
> obnoxious, and having a bot immediately leap into the seat only
> slightly less so.
>
> I think I like option (3) the best, since it involves stuff that the
> ref sometimes has to do anyway (in the case of a user-departure
> timeout), and doing a countdown while the player is (literally)
> standing right there seems weird. Standing is a very deliberate action
> (compared to a connection drop) and doesn't seem to fit the automated
> response of a wait-for-return timer. Letting the players resolve the
> situation seems more natural, to me.

(Continue reading)

Jason McIntosh | 4 Jul 20:12
Picon

Re: Standing in the middle of a game

On 7/4/05, Andrew Plotkin <erkyrath <at> eblong.com> wrote:
> On Sun, 3 Jul 2005, Jason McIntosh wrote:
> 
> > I don't think we ever talked about what happens when a player tries to
> > stand up while a game is active.
> 
> I mentioned it in a post at one point, I think.

Yeah, I came across the post when I was looking for the blackjack
discussion yesterday... whoops.

> What player decision are we trying to model by this action?

I was thinking something like "I need to leave the game; can someone
take over for me?"

But I thought of this before I realized that there'd have to be a
separate cli->ref suspend_game() call regardless. And it's occurring
to me now that the availability of this call would make this
server-side behavior completely unnecessary; a client could simulate
it by offering a command that send a suspend_game() request
immediately followed with a stand(me) request.

So... never mind. This behavior is supported by Frivolity as of last
night, but I'll just remove it when I get in there next. (And will
also add suspend_game() support.)

> Given what I say above, I will counter-suggest your option (1), where *no*
> seat-change is permitted after the game starts. (Except perhaps for the
> addition of a bot, in the "bot" path of user departure handling.) This
(Continue reading)


Gmane