Close the window
Saying the truth, mis-writing a move in correspondence chess can be fatal for the game.
But it depends, if the miswritten move is still valid or not fully valid. For example if the check mark (+) is missing, our opponent can reject the move, and can send it back to us for correction.
But if we have two knights, one can move to e4 and the other one can move to e5, mis-writing 12.Ne4 to 12.Ne5 can be fatal, and there is no way to proof we wanted to move the other knight.
This is a problem, that can be solved in server based correspondence chess, that this club offers.
By default the server is very indulgent in accepting moves, it accepts invalid moves if they are still unambiguous, adds check and capture marks, doesn't require the move number, etc. This is for reducing the number of rejected moves, but it results that some miswritten moves are not rejected, and are accepted as a different move.
Those players who manually compose their move messages, and therefore sometimes miswrite their moves may find the StrictMode setting useful.
If they turn it on, the server will accept only fully valid, complete moves exactly as shown in the next example:
Move 1234 12.Nd2-e4
In strict mode the server requires the move number, one dot as white and three dots as black, the piece letter (even at pawns), the from square, the capture mark or hyphen, the target square, and the check mark if needed. If any of these parts is missing, or the whole move is invalid the server rejects the move.
This way the chance that a miswritten move can be valid as an other move is lowered quite dramatically.
Available from Apr 13, 2005.