The Chess Variant Pages

[ Help | Earliest Comments | Latest Comments ]
[ List All Subjects of Discussion | Create New Subject of Discussion ]
[ List Earliest Comments Only For Pages | Games | Rated Pages | Rated Games | Subjects of Discussion ]

Single Comment

Tjatoer!. A chess variant written in Python, designed to stress test engines.[All Comments] [Add Comment or Rating]
Halfen Ludith wrote on 2021-06-28 UTC

I agree that the pieces are so many that they're harder to learn, in earlier amendments I have made changes to the pieces' names before to eliminate all the piece names that are too commonplace like the Ferz to the Fürst, the Man to the Mullah, as another editor suggested (notice that I changed the piece name that is on the Piececlopedia to something that isn't on the Piececlopedia). but now I am asked to change the name of pieces that isn't on the Piececlopedia to the ones in the Piececlopedia. The basis on which I named the pieces is on the grounds of notation, purpose, and design.

Firstly, regarding notation, each piece's name's first letter (except for the regular chess knight) corresponds with its notation, and with 26 types of pieces, it fits nicely with the 26 letters of the English alphabet. I did some cross-checking with the Piececlopedia and found that even if I use the name of the piece commonly attributed with a move in the Piececlopedia, and even if I don't confine myself to the first letter of the piece, still, the letter J, S, V, W, X, and Y will not be represented. Thus some pieces must have double letters for their notation, like (A) for the amazon then (AR) for the archbishop, or have a notation of a letter that isn't on the piece name itself (in both cases, it will be more confusing don't you think?).

Secondly, regarding the purpose of the game, there is no doubt that a human needs a lot of effort to learn how to play this game, and I would be honored if anyone would take the time to learn how to play it, but for an engine (the reason I designed this variant in the first place is for engines to play it) it needs not to memorize the moves of the pieces nor its notation since a computer is just following what it is programmed to do.

Thirdly, there is the game theme and design. I named the piece to more or less correspond with its design (though some pieces correspond better than others, for example, the zorro used to be the zebra hence it is represented by a zebra). In the GitHub repository, I have provided more information on the design ideas of the pieces (how the pieces in the King's Court is designed with royalty in mind, like how the Fürst is represented by a royal West-Sumatran headpiece, how the Esquire is represented by the Isicholo, a Zulu African headdress, or how the Duchess is represented by the Kokoshnik, a Russian headdress) to change the names of the pieces means eliminating the significance of their design to their name, or to painstakingly redesign all the pieces to befit their new name from scratch will overhaul the overall theme of the game.

with that being said, as some sort of a workaround, I made a table to better understand the pieces' moves