Author: Lex Loep
Date: 04:58:21 02/07/05
Go up one level in this thread
On February 07, 2005 at 06:11:51, Tony Werten wrote: >On February 06, 2005 at 15:56:46, Lex Loep wrote: > >>On February 06, 2005 at 15:21:03, Gian-Carlo Pascutto wrote: >> >>>On February 06, 2005 at 15:15:29, Peter Skinner wrote: >>> >>>>http://www.chessclub.com/help/new-features >>>> >>>>1-Oct-2004: Exploiting having high lag by moving before your seeing your >>>>opponent's move no longer works; you'll just get "It's not your turn". That >>>>trick was never reliable anyway, since you had to hope that your move would >>>>reach the server after your opponent's move did (as well as hoping that your >>>>move turned out to be legal, not to mention good). This change simplifies the >>>>client-server protocol with respect to timestamp and moves, and should stop a >>>>problem we've seen occasionally where time isn't deducted from the clock >>>>correctly. Clients with a true "premove" feature are not affected. >>>> >>>>Unfortunately they are not willing to fix it for the Chesspartner interface, as >>>>it reduces the chances of the lag cheating working. >>>> >>>>Someone on either end has to fix this... it is simply the moves are coming way >>>>to fast. Even the move delay option is not working. I have set it as high as >>>>50ms with no success. >>> >>>This makes no sense. ChessPartner *can't* move before it sees the opponents >>>move. It's not a human that can guess what the opponent is going to play... >>> >> >>Thats right, CP only sends the move AFTER it has received the opponents move, >>this can be simply proved by looking at the log files. Its ICC that then comes >>back with the "Not your turn error". >>To me its clear where the problem is. The delay is just an attempt to workaround >>the problem. > >Are you sure the correct timestamp is sent with the move ? I dont know, CP simply passes the move to the timestamp program and has no control over it. The timestamping process is a secret protocol. Lex > >Tony > >>Like mentioned before, I have never been able to reproduce the problem myself. >>It also seems to happen with a few people. Perhaps they have very fast PC's. >>Suggestion for now is to try a even higher delay, something like 500 ms. >> >>Lex >> >>>Either this is not the problem or ICC has severe bugs. >>> >> >> >> >>>-- >>>GCP
This page took 0 seconds to execute
Last modified: Thu, 15 Apr 21 08:11:13 -0700
Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.