One of the key things that any chess engine needs to be able to do, is take the input from the calling program with regards to en passant. With a […]
To castle, or not to castle, that is the question, picoEngine….
As you can see from the above screenshot, one of the engines possible moves is e8g8, which is for the black king to castle on the king’s side. This is […]
Castle, picoEngine?
After about an hour of accomplishing nothing, I finally gave up on what I was doing and fixed the UCI input for “movpos” when castling. So now, if given the […]
Promotion time picoEngine!
It’s really important to note that if a pawn gets promoted, it becomes the new piece, whatever that piece is. Either a knight, bishop, rook, or queen. While this was […]
picoEngine?! Where is the king?!
What good is king safety if the king refuses to capture it’s attacker? I guess I had programmed a cowardly lion… er… uh… king. Actually the real problem was that […]
Pawns, one step at a time, picoEngine….
Okay, it’s time to work on moves for the last piece: the pawn. Believe it or not, the pawn is the most difficult piece for me to program. It has […]
This is not checkers, picoEngine….
Then why does he say “king me?!” Today I worked on the king moves for picoEngine. Note that I did not include castling moves yet. Without the castle moves, the […]
Queen, picoEngine?
In my most recent commit, which you can check out in full at my GitLab, I added the ability for the queen to move to the picoEngine. This completes all […]
Bishops aren’t Bums…
Believe it or not, the bishops can now move! 3 of the 6 piece types now have the complete freedom of movement that they should have on the regular board! […]
Uh, picoEngine? I thought you said the king was safe?
Except he’s not. That’s right. I big technical oversight on my part allowed the king to not be safe at all! while (boardPositions[k] == ‘*’ && notI) { Needed to […]