Building a Simple Chess AI

I’ve been wanting to build a chess AI for a few years now. I was excited by the idea of building a program that could make decisions ,and maybe in the future, learn from those decisions.

With the help of Lauri Hartikka’s tutorial “A step-by-step guide to building a simple chess AI “, I was finally able to build my own chess AI (My details below are simply an extension of his).

You can play it here: https://bay-chess-ai.herokuapp.com.

When playing, I would recommend opening your browser’s console so you can see the output as the computer thinks through each move.

Want To See How It’s Built?

In the rest of this article, I’ll walk you through the ideas behind the different iterations of the chess AI, and how I implemented them, so you can build your own. Where applicable, I’ve provided links to resources that helped me understand some of the theories behind the ideas I implemented.

Each iteration has increasing “intelligence”, which allows it to make better moves. I’ve included all iterations as functions within my code.

If you’d like to see the full code, you can view it here: https://github.com/byanofsky/chess-ai-2

The file which contains the code for calculating moves it located here: https://github.com/byanofsky/chess-ai-2/blob/master/public/js/movecalc.js

Setup

The goal of this project is to build the chess AI, not the board visuals or chess logic (what moves are allowed, when the game is over, etc).

Luckily, there are 2 libraries which handle both of these, and work well together.

chessboard.js handles creating the visuals (the chess board and pieces), as well as the interface for when a user makes a move (dragging pieces to a square).

chess.js is a library which, as its README states, “…is used for chess move generation/validation, piece placement/movement, and check/checkmate/stalemate detection – basically everything but the AI.”

For server-side code, it is just Node.js and Express. I’m not overly familiar with Node and Express at this time, so I tried to keep it as simple as possible. In the future, once I get more familiar, I’ll improve this.

I created 3 JavaScript files which handle different aspects of the chess AI:

  1. boardconfig.js – sets configuration for chessboard.js, and creates an instance of the board and chess game
  2. movecalc.js – contains the functions which calculate the move to make
  3. main.js – contains functions for initiating the computer to move

Now, let’s discuss the move calculation functions. I’ll discuss each iteration that I built.

Iteration 1: Random Moves

making-random-moves.gif
Making random moves

This first iteration really sucked, but was quick to implement.

The AI simply finds all possible moves it can make this turn, and randomly picks one to make.

The function I used here is actually available on the chessboard.js website as example code. You can view it here: http://chessboardjs.com/examples#5001

It also includes the code for integrating chess.js and chessboard.js, so it is a great starting point.

Iteration 2: Choose Best Move, Looking One Move Ahead

One move ahead.gif
Looking one move ahead

This next iteration starts adding some decision making to the chess AI.

It looks at all possible moves it can make this turn, and evaluates it’s position after each move. It then picks the move which leads to the best position.

To implement this iteration, we need 2 functions:

  1. One function to evaluate the position
  2. Another to evaluate the outcome of each possible move

Position Evaluation Function

In chess, you can ‘score’ a current position to see which player is ahead. This will then allow the AI to basically say, “Move A leads to a position of -100, but move B leads to a position of 50. So I’ll choose move B.”

There are many ways to calculate this, but for this chess AI, we’ll use a relatively simple function to figure this out:

Relative to the player for whom we want to evaluate the position, any of their own pieces will add to their score, and their opponent’s pieces will subtract.

So the return value will be the player’s position relative to its opponents.

What about the value for each piece? There are many different ways you can assign these values (https://en.wikipedia.org/wiki/Chess_piece_relative_value), but I decided to go with Larry Kaufman’s suggested values for the middle game, multiplied by 100, so there are no floating numbers to deal with:

  • pawn = 100
  • knight = 350
  • bishop = 350
  • rook = 525
  • q = 1000
  • king = 10000

The function, shown below, takes the 2D array that is returned by chess.js’s function chess.board(). It loops through each piece and either adds the piece if its color matches with the player color passed to the function, or subtracts it.

This board evaluation function will be used in the rest of the iterations. As mentioned, it does have limitations. For instance, it does not take a piece’s position into account when scoring it (example: a bishop in the middle of the board is better than one in a corner).

Improving this evaluation function will also improve each iteration.

But for now, it is a good starting point.

Evaluate All Possible Moves

This function uses the position evaluation function to evaluate the position after every possible move.

We’ll build upon the random move function from the previous iteration.

Instead of randomly choosing the move from the list of possible moves, our program will make every move and evaluate the position. After it makes each move, it will undo the move. All the while, the function is tracking which move leads to the best position.

You’ll notice that I randomized the order of the possible moves. Without this randomization, if all moves lead to an equal outcome, it will choose the first move in the list (which is the first piece that can move in the upper left corner). This leads to the knight moving, then the rook moving back and forth until a piece comes close enough to capture.

Iteration 3: Looking Multiple Moves Ahead

While the last iteration now encourages the computer to capture pieces (it will pick moves that increase its relative position), it is still lacking. Because the chess AI is only looking one move ahead, it isn’t able to predict what its opponent will do after its move. So it isn’t able to determine if it should move a piece about to be captured, and will actually move a piece into a position to get captured.

So, in this third iteration, we’ll give the AI the ability to look more than one move ahead.

To implement this, we’ll use an algorithm called Minimax.

I’ll explain what Minimax is, and then show my implementation.

Minimax

I’ll provide a short overview of Minimax here, but I highly recommend the Wikipedia article on it: https://en.wikipedia.org/wiki/Minimax. You’ll even find a pseudocode example there.

Minimax is an algorithm we can use to evaluate all possible moves a player can make. We follow each move to a certain depth, which in this instance is how many moves ahead we want to look. Our evaluation will be relative to a player, and that player will be trying to get the best score possible (maximize their position). The opponent be doing the opposite: trying to minimize the original player’s value (which is, in essence, maximizing the opponent’s own value).

To further understand this concept, it helps to create a tree. In this instance, we are starting with the maximizing player, and looking 2 moves ahead:

FullSizeRender.jpg

Each square is a node when the maximizing player chooses a move, and a circle is a node when the minimizing player chooses a move.

We can follow the tree and see the outcomes for each possible move lead to these positions: 100, -100, 0, and 10.

Naturally, the maximizing player will want to reach an outcome of 100. But if the maximizing player chooses that route, the minimizing player will make a move that leads to -100 (hence why -100 trickles up).

Instead, if the maximizing player goes with the other move, the minimizing player will choose 0.

So the maximizing player will need to go with the move that leads to 0 since it leads to the greatest possible outcome.

Implementing Minimax

Just as we did with the iteration looking one move ahead, we’ll still loop through all possible moves, but the value of each move will not be the current board position, but the final board position as we trickle down the tree.

For this, we’ll need to use recursion.

Each recursive call, we decrease our depth by 1, until we get to a depth of 0, at which point we evaluate the position.

These values trickle up and allows the AI to pick a move that leads to the best position.

One thing to remember: we are evaluating from the viewpoint of one player. So when we enter a recursive call and are evaluating from the viewpoint of the opponent, the opponent is choosing a move that leads to the MINIMUM value.

Hence the if/else statement.

Iteration 4: Minimax with Alpha Beta Pruning

At this point, the chess AI is starting to make good moves. It will protect valuable pieces from being captured, and if it looks far enough ahead, it can start to formulate a strategy.

The only problem is the algorithm takes a long time.

That’s because of the number of branches it needs to evaluate.

Luckily, there is a way to remove branches that aren’t worth evaluating.

For this, we’ll use alpha beta pruning.

What Is Alpha Beta Pruning?

When I was researching alpha beta pruning, I found these notes to be the best resource possible: http://web.cs.ucla.edu/~rosen/161/notes/alphabeta.html

I highly recommend looking through these notes for a great example that walk through how it works.

But on a very high level, the idea is that we can eliminate branches when searching through the tree of moves, which makes our evaluating much faster. Take this tree as an example:

FullSizeRender 2.jpg

We start on the first branch, and come up with a 3, so that trickles up.

We then go down the second branch, and the first move the min player comes across is a 2.

But we run into a problem.

The max player already found a branch with a 3. So unless there is a value in the other branch greater than 3, the max player won’t choose it. So we need to find a value greater than 3. But because the min player is choosing and already found a 2, they only want to find a value less than 2.

So we are looking for:

x < 2 and x > 3

That doesn’t exist, so there is no point evaluating further down this branch.

In this example, there’s only 1 other branch, but in our chess game, this could be many more branches as we trickle down each move. Alpha beta pruning saves a lot of time!

Implementing Alpha Beta Pruning

This is just an extension of our Minimax implementation.

We simply add in variables to track alpha and beta.

We start with default alpha and beta values, but within each recursive call, we pass the alpha and beta values as they currently are.

And as these values trickle up, we use min and max functions to compare them to the values, and change the alpha/beta values.

Finally, if we find we are on a branch when alpha is greater than beta, we know we are on a branch that isn’t a candidate, and prune it.

Final Thoughts and Way To Improve

The final iteration here is actually a pretty good chess player. But it still has many limitations.

The biggest: it is still very slow. Having the computer look 4 or more moves ahead is still really slow. The AI could be much better if it could look more moves ahead, but it would take an ungodly amount of time.

One way I’ve considered to improve speed is to organize the possible moves. Right now, they are randomly organized before evaluating. But if they were organized with the best potential moves first (such as ones that capture pieces), alpha beta pruning would be able to eliminate more branches. But the sort function may take more time than is saved.

Another issue is the position evaluation function. Currently, it is based on how many pieces are remaining on the board. But it does not take the piece position into consideration. Lauri Hartikka does implement this in his tutorial, but which position is better for a piece must be determined by the programmer, not the computer. I’d like to find a way for the computer to figure this out.

Going forward, there are other algorithms I’d like to try to solve these issues, as well as attempt to incorporate some form of machine learning.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s