1. 27 Jun, 2022 2 commits
  2. 25 Jun, 2022 1 commit
  3. 24 Jun, 2022 2 commits
  4. 14 Jun, 2022 2 commits
  5. 13 Jun, 2022 2 commits
  6. 09 Jun, 2022 1 commit
  7. 07 Jun, 2022 1 commit
  8. 04 Jun, 2022 3 commits
  9. 01 Jun, 2022 1 commit
  10. 28 May, 2022 2 commits
  11. 19 May, 2022 1 commit
  12. 18 May, 2022 1 commit
  13. 15 May, 2022 1 commit
  14. 12 May, 2022 1 commit
  15. 10 May, 2022 1 commit
  16. 07 May, 2022 1 commit
  17. 06 May, 2022 1 commit
  18. 02 May, 2022 2 commits
  19. 01 May, 2022 1 commit
  20. 15 Apr, 2022 2 commits
    • David Kaye's avatar
      Don't allow to perform castling if the non-moved rook was already · ce7a9b46
      David Kaye authored and Alexander Semke's avatar Alexander Semke committed
      captured and its position is occupied by another piece.
      
      BUG: 430403
      FIXED-IN: 22.08
      ce7a9b46
    • David Kaye's avatar
      Fixed incorrect promotion in the XBoard protocol. · d7880a9a
      David Kaye authored and Alexander Semke's avatar Alexander Semke committed
      To generate a move string including a pawn promotion, the Knights code starts out with a generic call to move.cpp to create a string.
      An example string returned is:
      e7e8=Q
      Then the string is modified in xboardprotocol.cpp to remove all capitals:
      e7e8=q
      This string is then sent to the chess engine.  But the xboard protocol documentation requires the string to be:
      e7e8q
      
      Early on in chess engine development there were multiple formats to communicate with chess engines.
      Some utilzed an = sign between move and promotion piece.  But the Xboard system slowly became the standard for communication.
      Some chess engines will also accept the = sign in Xboard mode to be historically compatable.
      Specifically, the following engines will accept the = sign and will run:
      GNUchess6, Crafty, Phalanx XXV and Gully2.
      
      Other (usually newer) engines require the correct Xboard protocol. They will stop play with an illegal move response if the move contains the = sign.
      Some examples are:
      Greko, Dreamer, Sloppy, Beowulf and Prophet4.
      
      With this fix the behavior is more correct and all of the above engines accept the pawn promotion move and continue to play.
      
      BUG: 447665
      FIXED-IN: 22.08
      d7880a9a
  21. 14 Apr, 2022 2 commits
  22. 12 Apr, 2022 1 commit
  23. 08 Apr, 2022 1 commit
  24. 01 Apr, 2022 1 commit
  25. 29 Mar, 2022 1 commit
  26. 23 Mar, 2022 1 commit
  27. 20 Mar, 2022 1 commit
  28. 12 Mar, 2022 3 commits