Comments/Ratings for a Single Item
I prefer Marshal (one l, Freeling's usage notwithstanding) in part because there are a lot of piece-names that start with C and I often strive for unambiguous English notation. I also tend to use Archbishop instead of Cardinal for the same reason. I'm not sure there is a consensus for Chancellor or Marshal, but I would use neither name for any other piece-move. Both names seem to be strongly associated with the specific R+N combination.
You all make very good points. But I should point out that Gothic Chess also uses Chancellor. Perhaps we should indicate that the preferred name is Marshal(l), but Chancellor is also commonly used. Another point: should we have reserved names for certain pieces? Should we try to enforce the use of the names 'Marshal(l)' and 'Chancellor' exclusively for the Knight-Rook?
It seems to me that there are only two ways to name the B+N and R+N: either they are the Princess (B+N) and Empress (R+N) or they are whatever you want to call them in your CV. My reasons? There is a well-established group of dedicated problemists -- many active for decades -- who adopted the Princess/Empress convention long before this web site was started. While I'm not a problemist, I respect their efforts: adopting different names as the preferred choices seems arrogant, insulting and needlessly confusing. While I have no objection to a 'grandfather rule' that would allow existing CVs to keep whatever name the author chose, I think we should (gently?) nudge contributors toward the problemist's standard, since different names for the same off-the-shelf fairy chess pieces (Camels, Zebras, etc.)usually makes no sense.
With due respect to problemists, Chess problems are not Chess and Fairy Chess problems are not Chess Variants. Though, of course many individuals have a high level of interest in both problems and games, the overlap is by no means 100%. For myself, I have only a very mild interest in problems (though I can see why someone could find them fascinating). Similiarly, I have known problemist fanatics who have little interest in playing the game--to each his own. If there is to be an orthodoxy in the naming of variant pieces let it be based on usage in games rather than in problems--likewise, if there is to be an orthodoxy in the naming of problem pieces, let it be based on usage in problems rather than games. I don't really care what someone names a piece. What would be a nice touch on the game pages would be to put the piece's 'funny notation' after the name: Thus the inventor could use Chancellor (RN), Marshal (RN), Empress (RN), or Bogeyman (RN) and I know at a glance what piece is being refered to.
While it is convenient to have universally understood conventional names for common variant pieces, it will always be true that variant designers will want to use ad hoc names that fit the theme of their variant. Additionally, there *are* conventional names for the most usual first-order atomic moves (Ferz, Wazir, Alfil, Dababbah, Knight, Camel) and second-order moves (Rook, Bishop, Queen, King) built from them. Add the nearly universally understood use of 'rider' and 'leaper', and it is easy to describe most variant pieces. I am in agreement with Mike Nelson in supporting the universal use of Ralph Betza's funny notation in move descriptions, and I further believe that an effort to standardize the syntax of funny notation would be worthwhile. Once the syntax is consistent, so that a given move can be validly descibed in ony one way, the Piececlopedia could be upgraded to a database, where, e.g., one could enter a query for 'ADF' (but not 'AFD' or 'FAD') and get a list of all the names of pieces with that move and what variants they are used in. This seems like an enormous labor, but there is now so much material on the CVP that no one can be familiar with it all, and this will aid designers in discovering if their new variant has been anticipated by someone else.
I definitely OK with not insisting on a convention; my main objection is to any insistence on a new convention to replace the problemist's one of Princess/BN and Empress/RN. I also don't think there is any known convention among 'CV players', or anyone who could (at this time) speak for them. I would like it to be easier to find out what an author is talking about. As a partial solution, I think John Lawson's suggestion has merits.
I think the solution is education and encouragement, not some sort of unenforceable faux compulsion. To this end, I think that encouraging the use of a slightly tightened Betza notation on a widespread basis has clear merit. I also think that designers for their part would be well-served by some modest research before they jump to publication--and their games are in fact better served by forging their links to the family tree with good naming.
I don't think it is desirable or feasible to enforce standardized names. I believe it's best to respect the autonomy of individual game creators, allowing them to choose whatever names they prefer. But I also believe that game creators are best served by knowing the history of the pieces, so that they can make informed decisions about what to name a piece. I also believe it is good to provide reasons for and against certain names, allowing the game creator the freedom to judge whether or not the reasons are good ones. This allows game creators to freely make informed decisions, which is what's best. As it happens, this piece and the Bishop-Knight piece are probably the two pieces with the longest list of different piece names. This is because they are the most popular fairy pieces, but they have never been standard pieces. The standard pieces and the little-used pieces are generally known by fewer names, and it is easier to settle on common names for them. But these two pieces have been used in several unrelated games, possibly reinvented several times, and they have acquired a longer list of names.
There is no getting away from the problem of Empress for a piece weaker than the Queen, whose bishop move alone is more powerful than the bishop's own as it can be executed from a starting square of either colour. The first name that I saw was Chancellor, but having read the above I am won over to Marshall; the Mare element in the name preserves the femininity (in mediæval eyes) of a piece having the move of the home and refuge that the Rook represents. Besides, there is a much more suitable meaning for Empress: a 3d piece combining rook, bishop, and unicorn. This would reflect it being a Queen with an extra dmiension. Tying in with this could be Emperor for a 3d king that can also move one square triagonally, and Viceroy for a piece that can only move one-square triagonally (i.e. a triagonal version of the Wazir and Fers).
Here we have common, basic RookKnight mate white- RNc1 black- Kg8 Pf7,g7,h6 1.RNc8+ Kh7 2.RNf8#. Simple but important stuff that should be on a RookKnight webpage somewhere. This seems to be the most frequet reoccuring mate with this piece, by a wide margin.
A position from a Dvoretsky book where I changed a black knight into a RookKnight: White- Ka2 Bg8 Nh8 Pf3 Black- RNd3 Kf6 Pf4 1...RNb4+ 2.Ka3 RNa6+ 3.Kb3 RNb8+ 4.Kc4 RNxg8 and 5...RNxh8 next. Some fancy footwork by the RookKnight.
Chancellor Chess - Book contains several chess problems using the Chancellor (R+N) piece. We should update Piececlopedia articles to include links to any problems, or endgame positions, using the piece in the article. And, ideally, this site would have a monograph on chess variant endgame theory. Here is a brief note:
The endgame where White has King (h8) and Queen (h2) against Black's King (b1) and Pawn (c2) is drawn after 1.Qh7 Ka1 2.Qxc2 stalemate. Or White can keep on checking until the fifty move rule applies. There is simply no way to move the White King closer to the Black Pawn. But substituting a Chancellor for the Queen (h2) leads to 1.Cd2+ Kc1 2.Cb3+ Kd1 3.Cd3+ Ke2 4.Cd4+ winning the Pawn and the game. The Chancellor is a subtle and fascinating piece - I rarely design a chess variant without including it.
25 comments displayed
Permalink to the exact comments currently displayed.