A Tiny Mistake in the Opening Database on chess.com
Sort:
Thanks for reporting this. I will take your discovery to the proper authorities for evaluation. It’s members like you who make chess.com so grate. Keep up the good work!
Dec 18, 2023
0
#4
putshort wrote:
Thanks for reporting this. I will take your discovery to the proper authorities for evaluation. It’s members like you who make chess.com so grate. Keep up the good work!
Grate? SMH! You do that to cheese, not chess!
ThrillerFan wrote:
putshort wrote:
Thanks for reporting this. I will take your discovery to the proper authorities for evaluation. It’s members like you who make chess.com so grate. Keep up the good work!
Grate? SMH! You do that to cheese, not chess!
That's a grate comment! 
Sep 28, 2024
0
#6
Fear0fChess wrote:
ThrillerFan wrote:
putshort wrote:
Thanks for reporting this. I will take your discovery to the proper authorities for evaluation. It’s members like you who make chess.com so grate. Keep up the good work!
Grate? SMH! You do that to cheese, not chess!
That's a grate comments English
Sep 28, 2024
0
#7
To populate the database they probably just parse valid PGN notation and store the results, since there's no consistency in how people are notating this position the database has this issue. Could be fixed by adding some logic for normalizing the input, but it's a pretty rare edge case.
Ne2 and Nge2 are the same move in the position below, but the database has both for no good reason. Also, since Nce2 is not possible anyway, doesn't it make more sense to use just Ne2?