[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [pbmserv-dev] what we need...



In all cases I can think of where I have had to do a double undo it was because I missed the original request.  Partially this is because the messages look similar to a normal move message.  Now if the subject line said "UNDO" in capital letters...

I recall that proposals for a draw also sometimes are hard to pick out especially in multiplayer games because they have the name of the person whose turn it is and in multiplayer games I often get into the habit of reading only those messages with my name...

Cheers,

Lyman

----- Original Message ----
From: Yves Rutschle <pbm@rutschle.net>
To: pbmserv-dev@gamerz.net
Sent: Wednesday, May 28, 2008 12:46:10 PM
Subject: Re: [pbmserv-dev] what we need...

On Wed, May 28, 2008 at 12:01:26PM -0400, Richard Rognlie wrote:
> In this case, it was a non-issue.   dzander had me dead to rights
> I would have just been wiggling at the end of the rope.
> 
> But it's a good idea...  make the move code check for
> 
>         "is an undo pending?"
> 
> before accepting a move, vs. the current code which doesn't check at all.
> (taking the stance that a move is an implicit "reject")

Maybe it'd be worth going the extra mile to also solve the
'dual undo' problem (I move, you move, I realise my move was
wrong, I ask you undo, you undo, I accept, I undo, you
accept, I re-do my move... that's a lot of work for SMTP
servers ;) ): How about a "backto" command to go back to any
specific move in the game:

chess x backto 10w

On board x, go back to move 10, white to move.

Y.


To unsubscribe, send a message to esquire@gamerz.net with
    unsubscribe pbmserv-dev@gamerz.net
as the BODY of the message.  The SUBJECT is ignored.