scala-chess/scala-chess-core

implementation of chess using the wonderful language scala

scala-chess

implementation of chess using the wonderful language scala

scala-chess-core's Issues

Implement Castling (Rochade)

Rules:

• 1. The king and the chosen rook are on the player's first rank.[3]
• 2. Neither the king nor the chosen rook has previously moved.
• 3. There are no pieces between the king and the chosen rook.
• 4. The king is not currently in check.
• 5. The king does not pass through a square that is attacked by an enemy piece.[4]
• 6. The king does not end up in check. (True of any legal move.)

Add "En passant"

From wikipedia:
When a pawn advances two squares from its starting position and there is an opponent's pawn on an adjacent file next to its destination square, then the opponent's pawn can capture it en passant (in passing), and move to the square the pawn passed over. However, this can only be done on the very next move, otherwise the right to do so is forfeit. For example, if the black pawn has just advanced two squares from g7 (initial starting position) to g5, then the white pawn on f5 may take it via en passant on g6 (but only on White's next move).

Refactor Logic

Refactor Logic to Traits

Implementaion der Schachprotokolle WinBoard/XBoard sowie UCI

Hallo,
zwei populäre Protokolle , unter denen nahezu 1000 Schachprogramme laufen, sind:

WinBoard/XBoard (CECP) http://home.hccnet.nl/h.g.muller/engine-intf.html - http://home.hccnet.nl/h.g.muller/engine-intf.html

UCI http://www.shredderchess.de/download.html

Werden diese Schnittstellen auch von der ScalaChess Engine verwendet?

Gibt es einen Zusammenhang mit der graphischen Benutzeroberfläche https://github.com/scalachessgui/scalachessgui bzw, https://github.com/exoticorn/scalachess/ ?

Refactor Ations

Refactor Actions to Atomic Actions and Executable Actions

Fix pawn 2 square move

A Pawn can only move 2 squares forward if the square moved over is not occupied.

Implement check check

If a move results in a check it is not allowed