Fun fact, you can have a completely different game now by changing the language of the notation.
xkcd
A community for a webcomic of romance, sarcasm, math, and language.
For the curious: https://lichess.org/editor/r1b1k2r/1pp1nppp/8/p1b1p3/2PnpP1P/2K5/PP3q2/RNBQ1BNR_w_kq_-_0_1?color=white
For the less curious: it was mate in 16 for black, even before the knight moved. After the knight moved, it was mate in 1.
Don't get it, at all.
The writer played multiple games of chess against some conventional chess programs or AIs, and used a simple algorithm to determine their own moves:
For each move, the writer:
- Generated a list of all possible moves in the current position, and the moves were recorded in standard algebraic chess notation
- Sorted the list of possible moves in alphabetic order
- Used the move that was in the center of the sort order, but I have no idea what they did if the number of possible moves was even
This algorithm for choosing chess moves did not result in optimal play, and lost badly against the standard chess programs/AIs.
The illustrated position shows the algorithm generating a blunder or useless move for White (Ne2) that allows a checkmate victory for Black with their next move (... b4#), i.e. "Black Bishop moves to b4, checkmate."
Black's winning move is not shown, likely as a brainteaser for the readers.
The writer named their algorithm "AlphaMove" as a take on Google's famous chess playing AI from 2017 named "AlphaZero".
Except in the writer's case, the "Alpha" in their algorithm's name is short for "alphabetic", which makes the expanded name "Alphabetic(-sort)Move".
He mentioned that it rounded down when even, so I'm assuming it went forward one place.
Also, wouldn't checkmate be notated with #?
You're right, "#" for checkmate is in more common use than the "++"
Honestly, I understood that much, but I still don't get it.