Comments/Ratings for a Single Item
I rewrite the page understandingly Knight can capture up to 2 pieces, but he can capture a piece which stands in the corner of the board. All rangers can capture up to 6 pieces.
Pieces check differently from how they capture? But you write they can also capture the King?!? Or is it only the Knight that captures differently from how it checks?
I will write it in page. All pieces are checking on their moving and capturing’s lines, but Knight is checking on his moving squares, and is capturing by dissect.
Post a comment if you judge that your submission is ready.
It is ready now! Please, I have more cool ideas but I haven't place for them on chessvariants.com now. I can wait.
This game makes little sense to me. You can capture a king by going through him, but this is not check? And you can check a king with a piece that CANNOT capture him?
And if you can only capture by going through, the pieces on the back rank cannot be captured at all unless one of them moves. A piece in the corner can not be captured except by a knight and only if one of the other pieces by him has already moved.
Finally, I will say this idea is not new and has been done better. For example, see Jumping Chess.
You have many games waiting to be published, but the writing is very bad, so they would require a lot of editing. And I am doubtful that the ideas are worth publishing anyway.
No, my Fluidity have many difference from it [Jumping Chess].
It’s not like diffs between Carrera’s and Capablanca’s setups of Archbishop and Chancellor, it’s like diffs between Capablanca’s and Seirawan’s chess.
No, my Fluidity have many difference from it [Jumping Chess].
It’s not like diffs between Carrera’s and Capablanca’s setups of Archbishop and Chancellor, it’s like diffs between Capablanca’s and Seirawan’s chess.
I understand it is different. Jumping Chess is a good, playable game. This one is not.
If I understand this correctly the King is the only piece that can be captured by displacement. All other pieces can only be captured by jumping over them, and there is no limitation to the number of pieces you can capture this way. (Well, the limitation is put by the board size.) Only the final square has to be empty or contain a King. Knights are supposed to move along an L-shaped path, (long leg first), and are the only pieces that can jump over friendly pieces.
In principle the Interactive Diagram should be able to do this: In XBetza notation the sliders are just multiple mcaf steps, up to 6 times, followed by a final leg with mk mode. For the Knight there first are exactly two mpca steps before it turns sideways for the mk final leg, as it can also hop over obstacles.
For some reason the Diagram doesn't correctly perform these discriptions, though. I suppose there is a problem combining destructive (c and non-destructive (mp) modes on the same leg. For the Knight I could fix that at the cost of far higher complexity of the XBetza description (mpcafmpcasmkW should have been enough). This seems to be a Diagram bug that should be fixed.
[Edit] Oh, stupid of me. Because the sliders cannot jump friendly pieces, a much simpler description is possible. E.g. (caf)6mkB instead of (mcaf)6mkF. Because B is a slider the intermediate m steps are automatically bridged, and no combination of m and c modes is necessary. Apart from capture during castling everything now appears to work.
BTW, this is a nice demonstration of the Diagram's new move-entry system, with up to 7 pieces captured in one turn!
satellite=fluid
files=8
ranks=8
maxPromote=0
graphicsDir=/graphics.dir/alfaeriePNG/
squareSize=50
firstRank=1
lightShade=#FFFFCC
darkShade=#669966
holeColor=#663300
rimColor=#663300
coordColor=#D6DEAD
whitePrefix=w
blackPrefix=b
graphicsType=png
useMarkers=1
borders=0
enableAI=1
newClick=1
knight:N:mkNmpafmcpasmWcafmpasmWcafcasmW::b1,g1
bishop::(caf)6mBkB::c1,f1
rook::(caf)6mRkR::a1,h1
queen::(caf)6mQkQ::d1
king::mKisO2::e1
|
Fluidity ChessSeems white has a very easy forced win, though: 1. Qe2+. Since the Queen cannot be captured by displacement it is practically iron when in contact with the enemy King, and threatens that with displacement check. So it drives it very easily to the edge (or actually against the Rook files) for checkmate. |
Thank you for making the diagram so we can test. Unless I'm missing something, it looks like white wins in 3 moves.
No, it’s not easy win, black can easily block the path of check by 1.…Be7 or 1.…Qe7 after 1.Qe2
So it’s not required to add interactive diagram for THIS variant. But if it will be in online chess resource, thank you.
As I understand the rules, neither of these helps. 2. Qe8 capturing both king and the piece on e7.
He [i.e. the king] is royal, but can't be captured by displacement, he simply must avoid check.
Presumably this precludes Qe8
; as I understand it, the proposed defense thus prevent capture of the defending piece on e7
(which could also be a knight) by having the square after it not be vacant (it's occupied by the king) whilst blocking the check (which is “as in chess”) as a Chess rook would be unable to capture the king.
Iow one can't ‘displacement‐capture the king’ (for the purposes of calculating Check) and capture anything else in the same move (except with a knight).
This whole checking‐differently‐from‐capture business is rather confusing
OK, that makes sense. So it is not (caf)6mkB, but (caf)6mBkB, etc. I adapted the Diagram accordingly, putting k mode only on the direct (single-leg) move.
Of course the article should be adapted to make this clear.
What should I do to see this page published? I really don’t know it.
Please, I really don't understand what I should edit to get this published
I am not an editor but I think you could improve that page a bit.
The main feature in your game seems to be the capture mode and I confess that I don't understand it at all: "They capture even better: by dissecting — going through all opponent's pieces which are not on edges of their movement (behind the pieces are being captured by dissection must be at least one free space)" .
I believe that you know what you are talking about, but as a reader who never tried your game, I don't. "Even better" than what? What are "the edges" of a movement? Maybe you could illustrate with a diagram, and also revise the text to make it more - fluid.
The text at the beginning, "You’ll probably tell that it’s plagiarism beacause it’s hybrid of chess and draughts, but have you seen it with standard board, many captured pieces per turn, standard pieces and (probably) able to be on Lichess (free libre chess site with millions of players)? I did it for Lichess, but they don’t need it now (for 1 year minimally). I write it there."
This text has few typos, a strange grammar, and I wonder what it brings for understanding of the rules. At best it should be moved in the Notes section at the end of the page.
This is my advice.
Thank you by this advice.
(BTW if you want, I can request a Shako tournament with you someday. Site is Pychess (chess variants site written in Python), to play it, you have to create lichess.org (chess site with millions of players and open source code) account)
Ready
They capture by dissecting — going through all the opponent's pieces to the free square behind them.
Dissect does not mean what you think it does. The capturing ability you describe sounds similar to the Long Leaper from Ultima, though without the same restrictions. Some examples of what you're describing could help. Are multiple captures possible on one turn? If so, how exactly does it work?
I’ve edited this page, so rangers can capture up to 3 pieces.
Thank you for the diagram for calibrating this variant.
By the time, what you decide about this variant?..
I revised that article by some editing and adding diagrams for better explanation of the rules.
25 comments displayed
Permalink to the exact comments currently displayed.
The moves aren't completely clear to me; some examples would probably help.
The sliders must reach an empty square beyond a single captured piece, I think? The knights can capture up to three pieces, but always move 2 then 1? The kings don't capture at all?