Chess

Enjoy a fun and elegant way to play chess directly from the comfort of your own terminal! Play your friend or duke it out against the computer!

---

Run this Code

Play Chess in 3 simple steps! (You will need to have Ruby installed on your computer):

1. Run git clone https://github.com/msantam2/chess.git from the CLI.

2. Navigate to your Chess directory and run bundle install for a beautiful looking board as well as keyboard I/O. cd lib/ to enter into the lib/ directory.

3. Run ruby game.rb and you're off! Zoom in on the terminal for clearer and better gameplay! (cmd-shift-+).

---

Playing the Game

• (After running ruby game.rb) Follow the prompts to select your choice of gameplay.

• For all human players (robots excluded!) simply use the arrows on your keyboard to navigate the board. Once you are hovering over the piece you would like to move, press Enter. Next, navigate to the space you would like to move to and press Enter. If no valid moves exist for a certain piece, it cannot be selected. Be careful, once a piece is selected it cannot be de-selected!

• The cursor is represented by a blue background when navigating, and a selected piece with a green background. When hovering over one of your own pieces (or when one is selected), the possible moves are highlighted in yellow.

• To quit a game, press ctrl-C.

---

Technologies

Chess is built with pure Ruby code, exhibiting the principles of clean Object-Oriented Design. Each file contains only one class, implementing class inheritance where appropriate to ensure DRY code. The colorize gem is used to render a beautiful chess board, along with the io/console gem in cursorable.rb to read standard input (STDIN).

Implemention Details

Modules

Slideable and Stepable modules are mixed-in to each piece class to provide it with a moves method, according to its specific move behavior and whether it is fundamentally a stepping piece or a sliding piece.

This structure allows each piece class to have a simple move_directions method that specifies the directions it can move:

class Rook < Piece
  include Slideable

  def move_directions
    [:up, :down, :left, :right]
  end
end

Instances of Rook can slide in any non-diagonal direction.

class Knight < Piece
  include Stepable

  def move_directions
    [
      [:up, :up, :left],
      [:up, :up, :right],
      [:up, :right, :right],
      [:down, :right, :right],
      [:down, :down, :right],
      [:down, :down, :left],
      [:down, :left, :left],
      [:up, :left, :left]
    ]
  end
end

Instances of Knight can step in any direction with a combination of 3 successive steps.

Null Object Pattern

For empty spaces, a Null Object pattern is used to keep code DRY and easy-to-understand. The NullPiece is instantiated (only once in memory) with the following instance variables in order to integrate smoothly into the game logic (i.e. the game does not care what piece it is dealing with, only that is can always call .type and .color on each piece):

def initialize
  @type = :nullpiece
  @color = nil
end

When a piece is successfully captured, the NullPiece is set in its place:

def move_piece(start_pos, end_pos)
  piece = self[start_pos]
  end_piece = self[end_pos]

  self[start_pos] = NullPiece.instance
  self[end_pos] = piece

  end_piece
end

Winning Condition

A simple check is done after each player's turn to assess whether or not the game has been won:

def game_won
  @board.flatten.none? do |piece|
    piece.type == :king && piece.color == @current_player.color
  end
end

The game checks its @board immediately after the game has switched players to see if the current player's king remains (if it does not, it has been captured by the previous player and the game is over)

Computer AI

• Used ruby_deep_clone gem (which deep duplicates instance objects) to clone the board object, allowing for the evaluation of potential check/mate states.

new_board = DeepClone.clone(board)

Steps	Checkmate	Check	Neither
1	Select a random move - the computer knows it has already lost!	First things first: find moves that escape check.	The AI is not constrained by check/mate, but still must select from moves that avoid check/mate.
2		Filter these moves by seeing if any can force the opponent into check/mate. If AI can induce checkmate, this move is immediately chosen. If check, this move is a candidate for final choice.	Filter these moves by seeing if any can force the opponent into check/mate. If AI can induce checkmate, this move is immediately chosen. If check, this move is a candidate for final choice.
3		Further filter the moves that are still available by seeing which can capture an opponent's piece. Finally, the move that captures the highest value piece is returned.	Further filter the moves that are still available by seeing which can capture an opponent's piece. Finally, the move that captures the highest value piece is returned.

(the implemention of the above structure can be found in computer_player.rb)

To-Do

• Incorporate Castling and En Passant functionality into the game
• Even smarter AI! For example, the AI currently protects its King against check/mate, but it does not protect its other valuable pieces. Have the AI refuse to swap, say, its queen with the opponent's pawn. In sum, build the AI to analyze more consequences of a move rather than making any capture it can.
• Account for a stalemate (see https://en.wikipedia.org/wiki/Stalemate). If AI is the victim of a stalemate (in pseudo-checkmate status - see first image in wikipedia link) it should know it will lose and select a random move.