Comments by Snowmoondaphne
Hand piece is a direct translation of Shogi's Mochigoma(手駒).
So the hand piece is the same as Shogi's mochigoma.
Naturally, you can use any piece you capture as your hand piece.
H.G.Muller // I don't even know why... I found out it now
Kevin Pacey // Well, I guess my explanation was insufficient.
Every piece of your opponent you capture becomes your 'hand piece'. On your turn, you may place one of your hand pieces on an empty square of the board. (This is called 'drop'.)
However, in order to drop, you must not move any piece during your turn, and after dropping, you must pass the turn to your opponent.
And your hand piece Pawn cannot drop into the last (9th) rank, nor can it drop on a file that already has your Pawn. (It is possible to deliver a check or checkmate to an opponent by dropping a pawn.)
That said, the hand piece works the same as Shogi's mochigoma, except that the Pawn can make a checkmate with a drop.
H. G. Muller // If a piece in the enemy camp moves while staying at the enemy camp, it will also eventually reach the enemy camp. Therefore, it must be promoted.
If a player makes three forced defenses in the same sequence to block an opponent's attack, that player may lose. If this happens, it can be an unsatisfactory game for the player. However, in this game, there is only victory or defeat, there is no draw. And I think these rules make the game more aggressive.
(By the way, I have played the AI versus AI game several times with Fairy Stockfish, but I have not yet seen a case where I was defeated by three fold repetition.)
H.G. Muller //
That is not what 'reach' means in English. It means coming from the outside.
I got it. Added text related to it to the promotion rules.
If the player who perpetually checks loses there would also be no draw. Any loss could be described as unsatisfactory for the player who loses. The point, however, is that it is generally perceived as unsatisfactory for the neutral observer. And hence a defect of the game rules.
However, it is the identity of this game that draw does not exist, so there is no intention to modify the current three fold repetition rule. Also, I don't think this is a defect.
I assume the variants.ini you describe is the configuration file for Variant-Stockfish. (It might be a good idea to mention that... As it is readers have no clue what it means.) Since that file specified perpetually checking is a loss, ("perpetualCheckIllegal = true") it can hardly be a surprise that Stockfish does not do it. It just means you have it play according to different rules than you describe in your article.
Well, I'm sorry, but I didn't quite understand that. "It just means you have it play according to different rules than you describe in your article." What exactly does this sentence mean?
H. G. Muller // Umm, I played Mansindam on Fairy Stockfish over 30 times as AI vs AI. And all games so far have been decided by checkmate. (No case of winning by campmate, stalemate, or three fold repetition has been found yet.)
Did I misunderstand what you said?
Aurelian Florea //
https://github.com/ianfab/Fairy-Stockfish/releases/tag/fairy_sf_14
I downloaded Fairy Stockfish from assets here.
It might be quicker to ask on this channel how to use Fairy Stockfish.
https://github.com/ianfab/Fairy-Stockfish/blob/master/src/variants.ini
It might be good to take a look at this. Variants created by individuals are implemented by this definition.
And I use Fairy Stockfish via WinBoard (XBoard), I'll give you the file if you need it.
???
It is impossible to deliver the same check three times in Mansindam. This is because three fold repetition includes perpetual check. This is Mansindam's rule, I'm not sure what you're talking about.
(Or maybe I'm not good at English, so I didn't understand your saying well. If that's okay with you, please explain to me in a bit more detail.)
H. G. Muller // So in your example, does it mean that Black lose is normal, but White loses with Mansindam's variants.ini?
H. G. Muller // Umm, then how do you think Mansindam's variants.ini definition should be modified while maintaining the rules?
H. G. Muller // Yep I fixed that
The description of Knight's move was edited as follows :
-> Moves to the nearest square among squares that do not correspond to the same file, rank, and diagonal from its position.
Thank you very much, and thanks again for your kind reply!
I hope you have a nice day!
Some words have been corrected
- (e.g. Surrender -> Resignation)
And some pieces have been renamed to make them easier to read
- (e.g. 雲 ⇒ 云)
https://pychess-pr-657.herokuapp.com/
Mansindam has been temporarily added to Pychess!
All of Mansindam's original piece names have been decided !
Since this comment is for a page that has not been published yet, you must be signed in to read it.
Adam DeWitt //
Thank you for your kind reply!!
But I don't know how to apply interactive diagram inside the page. And I'm not sure exactly what the 'table' you are talking about is
Adam DeWitt // Thanks ! I did it !
25 comments displayed
Permalink to the exact comments currently displayed.