Difference between revisions of "Castling Rights"

From Chessprogramming wiki
Jump to: navigation, search
m (GerdIsenberg moved page Castling rights to Castling Rights without leaving a redirect)
Line 1: Line 1:
 
'''[[Main Page|Home]] * [[Chess]] * [[Chess Position|Position]] * Castling Rights'''
 
'''[[Main Page|Home]] * [[Chess]] * [[Chess Position|Position]] * Castling Rights'''
  
The '''Castling Rights''' specify whether both sides are principally able to [[Castling|castle]] king- or queen side, now or later during the game - whether the involved pieces have already moved or in case of the rooks, were captured. Castling rights do not specify, whether castling is actually possible, but a pre-condition for both wing castlings.  
+
The '''Castling Rights''' specify whether both sides are principally able to [[Castling|castle]] king- or queen side, now or later during the game - whether the involved pieces have already moved or in case of the rooks, were captured. Castling rights do not specify, whether castling is actually possible, but are a pre-condition for both wing castlings. Two [[Bit|bits]] per side are appropriate to store the castling rights, often one uses one [[Nibble|nibble]] to store the rights for both sides inside a [[Chess Position|position]] object, a kind a [[Array|array]] of four booleans.  
  
Two [[Bit|bits]] per side are appropriate to store the castling rights, often one uses one [[Nibble|nibble]] to store the rights for both sides inside a [[Chess Position|position]] object, a kind a [[Array|array]] of four booleans. In [[Make Move|make move]] one has to consider that king-moves reset both castling bits per side.  
+
=Irreversibility=
 
+
In [[Make Move|make move]] one has to consider that king-moves including castling itself reset both castling bits per side. Rook-moves from their original [[Squares|square]], or [[Captures|captures]] of rooks on their original squares reset the appropriate castling bits per wing and side. Changed castling rights should be considered in the [[Zobrist Hashing|zobrist key]] of the position, to reflect the irreversibility of the otherwise [[Reversible Moves|reversible move]], concerning [[Repetitions|repetitions]]. On the other hand, changed castling rights don't necessarily reset the [[Halfmove Clock|halfmove clock]] regarding the [[Fifty-move Rule|fifty-move rule]] <ref>[http://www.horst-wandersleben.de/Wette.htm Computerschach - Eine Wette, die ich gerne verloren habe] by [[Horst Wandersleben]] (German)</ref>.
Rook-moves from their original [[Squares|square]], or [[Captures|captures]] of rooks on their original squares reset the appropriate castling bits per wing and side. Changed castling rights should be considered in the [[Zobrist Hashing|zobrist key]] of the position, to reflect the irreversibility of the otherwise [[Reversible Moves|reversible move]], concerning [[Repetitions|repetitions]]. On the other hand, changed castling rights don't necessarily reset the [[Halfmove Clock|halfmove clock]] regarding the [[Fifty-move Rule|fifty-move rule]].
 
  
 
=See also=
 
=See also=
 
* [[Castling]]
 
* [[Castling]]
 
* [[Chess960]]
 
* [[Chess960]]
 +
* [[Irreversible Moves]]
 
* [[King Safety]]
 
* [[King Safety]]
 
* [[Unmake Move]]
 
* [[Unmake Move]]
Line 24: Line 24:
 
=External Links=
 
=External Links=
 
* [http://timkr.home.xs4all.nl/chess2/diary_3.htm Open chess diary 41-60 52. 20 February: Castling rights in photographs and on servers] by [https://en.wikipedia.org/wiki/Tim_Krabb%C3%A9 Tim Krabbé]
 
* [http://timkr.home.xs4all.nl/chess2/diary_3.htm Open chess diary 41-60 52. 20 February: Castling rights in photographs and on servers] by [https://en.wikipedia.org/wiki/Tim_Krabb%C3%A9 Tim Krabbé]
 +
* [http://www.horst-wandersleben.de/Wette.htm Computerschach - Eine Wette, die ich gerne verloren habe] by [[Horst Wandersleben]] (German) <ref>[[Dieter Bürssner]] found a game finished in a [[Fifty-move Rule|fifty-move rule]] draw, where [[Castling|castling]] occurred during the last fifty moves</ref>
 
* [http://mediocrechess.blogspot.de/2006/12/bug-another-little-bug-in-castling.html Mediocre Chess: [Bug] Another little bug in castling rights] by [[Jonatan Pettersson]], December 30, 2006
 
* [http://mediocrechess.blogspot.de/2006/12/bug-another-little-bug-in-castling.html Mediocre Chess: [Bug] Another little bug in castling rights] by [[Jonatan Pettersson]], December 30, 2006
  
 +
=References=
 +
<references />
 
'''[[Chess Position|Up one Level]]'''
 
'''[[Chess Position|Up one Level]]'''

Revision as of 10:14, 22 September 2018

Home * Chess * Position * Castling Rights

The Castling Rights specify whether both sides are principally able to castle king- or queen side, now or later during the game - whether the involved pieces have already moved or in case of the rooks, were captured. Castling rights do not specify, whether castling is actually possible, but are a pre-condition for both wing castlings. Two bits per side are appropriate to store the castling rights, often one uses one nibble to store the rights for both sides inside a position object, a kind a array of four booleans.

Irreversibility

In make move one has to consider that king-moves including castling itself reset both castling bits per side. Rook-moves from their original square, or captures of rooks on their original squares reset the appropriate castling bits per wing and side. Changed castling rights should be considered in the zobrist key of the position, to reflect the irreversibility of the otherwise reversible move, concerning repetitions. On the other hand, changed castling rights don't necessarily reset the halfmove clock regarding the fifty-move rule [1].

See also

Forum Posts

External Links

References

  1. Computerschach - Eine Wette, die ich gerne verloren habe by Horst Wandersleben (German)
  2. Dieter Bürssner found a game finished in a fifty-move rule draw, where castling occurred during the last fifty moves

Up one Level