Extended Betza Notation

[musketeerchess]

Hi Fabian, i checked the code. adding the Betza Notation is really a very clever idea. This eases a lot customizing unorthodox pieces for many chess variants. If i correctly understood the code, you only added the basic betza notation, but your code doesn't take into account the extended betza notation mentioned here https://www.chessvariants.com/page/MSbetza-notation-extended

Also i saw that when specifying the Leaper atoms, there are 2 duplicates. for example in the original atom table Camel move is C and Zebra move is a (3,2) leap. In your code these two C and Z are doubled with L (3,1) and J (3,2). Is that for a reason?

Is it possible to code with the betza notation in fairy stockfish pieces like this one?

Thanks Fabian

[ianfab]

In Fairy-SF Betza notation is essentially just a means for communicating the piece moves, it does not really define what is supported/possible in the engine, since that needs to be implemented separately. Therefore, only a limited subset of Betza notation is supported, as specified in the documentation, see

Fairy-Stockfish/src/variants.ini

Lines 100 to 107 in f3c982b

	# The movements of custom pieces can be defined using the Betza notation.
	# https://www.gnu.org/software/xboard/Betza.html
	# In Fairy-Stockfish only a subset of Betza notation can be used. The supported features are:
	# - all base moves/atoms (W, F, etc.)
	# - all directional modifiers (f, b, etc.)
	# - limited and unlimited distance sliders/riders for W/R, F/B, and N directions
	# - hoppers and grasshoppers for W/R and F/B directions, i.e., pR, pB, gR, and gB
	# - lame leapers (n) for N, A, Z, and D directions, i.e., nN, nA, nZ, and nD

[musketeerchess]

Hi Fabian, Thank you for your kind answer. Are you willing to extend Betza notation? What are your current top priorities? Hope you'll find sometime to help us concerning Musketeer Chess. The project advanced very well with various people trying to find a solution. But there are still a few key steps to improve the quality of computation. Le mer. 3 avr. 2024 à 20:44, Fabian Fichter ***@***.***> a écrit :

…

In Fairy-SF Betza notation is essentially just a means for communicating the piece moves, it does not really define what is supported/possible in the engine, since that needs to be implemented separately. Therefore, only a limited subset of Betza notation is supported, as specified in the documentation, see https://github.com/fairy-stockfish/Fairy-Stockfish/blob/f3c982bdb5a1882c45d9fab71b16f72de5191f19/src/variants.ini#L100-L107 — Reply to this email directly, view it on GitHub <#773 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIIE4HJ4MKGSVXP66YZLPS3Y3REZFAVCNFSM6AAAAABFP27MWWVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TAMBQHA2DI> . You are receiving this because you authored the thread.Message ID: <fairy-stockfish/Fairy-Stockfish/repo-discussions/773/comments/9000844@ github.com>

[seocwen]

I've recently been playing a lot of Ouroboros King on Steam, which seems to use a custom, kind of bad engine for fairy chess. It has a lot of pretty cool pieces that are fun to play with, like the manticore, and griffon, notated t[WB] and t[FR] respectively. Implementation-wise, I wonder if something like that could be coded as moving twice. I think there's at least one more piece using the t[??] notation in the historical variant Grant Acedrex (which is usually played 12x12, but a 12x10 variant would also be fun.