Author: Dieter Buerssner
Date: 07:55:05 03/10/05
Go up one level in this thread
On March 10, 2005 at 10:00:24, Kolss wrote: >If normal moves are coded as e.g. "e2e4", it would be nicest to have the same >for the castle moves. As in FRC, however, this can end up being ambiguous for >king moves (e.g. "f1g1" could be a normal king move or a castle move), this >could be prevented by coding the castle move as > >[king_from_square][rook_with_which_king_castles_square]. It has one tiny disadvantage: You need to know the board state (in general), to interprete a move. This is not needed for other from-to moves. Another idea. Just use 4 otherwise unused moves. e1h2 could mean white castles king side, e1a2, e8h7, e8a7 >By the way: How is a FRC castle executed on a virtual board on the screen (how >do you input the castle move)? I never heard anyone talk about that problem: if >f1g1 could be both a normal king move and a castle move, how is it recognized by >the GUI? Like promotion? Just give a menu/list of legal moves (often 4 in case of promotion, sometimes 2 in case of castling). Your suggestion seems also very well suited for inputting castling moves (but perhaps not suited as the only method, because a user may not be able to guess it and may be annoyed when he intuitively inputs a castling move and sees just his king moved). Cheers, Dieter
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.