Check out Grant Acedrex, our featured variant for April, 2024.

Enter Your Reply

The Comment You're Replying To

George Duke wrote on Mon, Mar 14, 2005 05:49 PM UTC:

'JKL,LargeCV': The pieces tend to just clog in mass of defense. Rook and Queen are different from Xiangqi Cannon, as Bishop and Queen are different from 'Canon'. I.e., Cannon/Canon replace the one they capture after a leap, whereas Jumping.Q/R/B capture the one they leap and move on. T.R. Dawson's older Grasshopper has modified jump along radial lines, leaping one piece one step along the Queen-lines and staying put either in move or replacement capture. These examples show the trouble with hopping along B and R paths; there is no absolute saddle point as to the best modality. Extension to multiple captures turns this Queen into excellent Rococo's Long Leaper. These jumping pieces mimic in varying degree the other 64-sq.(and also 100-) game's one (convertible) piece-type's jump-captures, and must have been re-invented(and discarded) from time to time. Some primary school teacher surely has had occasion to say: 'Wrong game, Roger. That's Checkers. This year we learn Chess.'

Edit Form

Comment on the page Jumping Chess

Name or UserID: Password: if signing in with UserIDRating: Comment or question:
Format:

Conduct Guidelines

This is a Chess variants website, not a general forum.: Please limit your comments to Chess variants or the operation of this site.
Keep this website a safe space for Chess variant hobbyists of all stripes.: Because we want people to feel comfortable here no matter what their political or religious beliefs might be, we ask you to avoid discussing politics, religion, or other controversial subjects here. No matter how passionately you feel about any of these subjects, just take it someplace else.

Quick Markdown Guide

By default, new comments may be entered as Markdown, simple markup syntax designed to be readable and not look like markup. Comments stored as Markdown will be converted to HTML by Parsedown before displaying them. This follows the Github Flavored Markdown Spec with support for Markdown Extra. For a good overview of Markdown in general, check out the Markdown Guide. Here is a quick comparison of some commonly used Markdown with the rendered result:

# Top level header: `<H1>`

> Block quote 
>
> Second paragraph in block quote

First Paragraph of response. *Italics*, **bold**, and ***bold italics***.

Second Paragraph after blank line. Here is some <U>HTML code</U> mixed in with the Markdown, and here is the same `<U>HTML code</U>` enclosed by backticks.

## Secondary Header: `<H2>`

* Unordered list item
* Second unordered list item
+ New unordered list
    * Nested list item
- An URL by itself:
    + https://www.chessvariants.com
- A text link:
    - [The Chess Variant Pages](https://www.chessvariants.com)

### Third Level header `<H3>`
	
1. An ordered list item.
1. A second ordered list item with the same number.
2. A third ordered list item.

~~~
Here is some preformatted text.
  This line begins with some indentation.
    This begins with even more indentation.
And this line has no indentation.
~~~

![Alt text for a graphic image](/graphics.dir/cvp-logo-draft8.png)

A definition list
: A list of terms, each with one or more definitions following it.
: An HTML construct using the tags `<DL>`, `<DT>` and `<DD>`.

A term
: Its definition after a colon.
: A second definition.
: A third definition.

Another term following a blank line
: The definition of that term.

Top level header: `<H1>`

Block quote

Second paragraph in block quote

First Paragraph of response. Italics, bold, and bold italics.

Second Paragraph after blank line. Here is some HTML code mixed in with the Markdown, and here is the same <U>HTML code</U> enclosed by backticks.

Secondary Header: `<H2>`

Unordered list item
Second unordered list item

New unordered list
- Nested list item

An URL by itself:
- https://www.chessvariants.com
A text link:
- The Chess Variant Pages

Third Level header `<H3>`

An ordered list item.
A second ordered list item with the same number.
A third ordered list item.

Here is some preformatted text.
  This line begins with some indentation.
    This begins with even more indentation.
And this line has no indentation.

A definition list: A list of terms, each with one or more definitions following it.; An HTML construct using the tags <DL>, <DT> and <DD>.
A term: Its definition after a colon.; A second definition.; A third definition.
Another term following a blank line: The definition of that term.

Categories and Details

Credits

By Peter Aronson.

Comments

Jumping Chess. Pieces capture by jumping. Board has extra edge squares making it 10x10. (10x10, Cells: 100)

H. G. Muller wrote on Sat, Dec 12, 2020 03:49 PM UTC in reply to Greg Strong from Fri Dec 11 08:36 PM:

Ah yes, I did not pay any attention to that since Fergus responded to my question. Everything should work, except that the highlingting doesn't suppress moves of pieces when there is an edge-capture to make. My idea for that was to add some Post-Game code to post-edit the list of legal moves by throwing away all moves that are not edge captures. If the list is empty, thenthe original list was OK, if it is not, the cleansed list becomes the new list.

There still is one other thing I don't like in the code, though. The include code now calls a routine BadZone to vet the pseudo-legal moves it generates, when 'zonal' is set to 1. This routine gets all squares of the move passed (origin, destination, locust square, drop square, and even dropped type). Currently it is blind to any 'hop squares', though. While there also exist variants (Janggi!) where a hopper cannot hop over some piece types. The hop square is not part of the move description, though. For that reason the code can handle moves with arbitrarily many hops (while the number of locust victims is limited to 1).

If I ever change the inteface between BadZone and the rest of the code, it would break all presets that relied on this interface. (Because the BadZone definitions are in the presets, and the change would be in the included file.) So perhaps I should better fix this first.

Greg Strong wrote on Fri, Dec 11, 2020 08:36 PM UTC:

I forgot about the preset H.G. made:

https://www.chessvariants.com/play/pbm/play.php?game%3DJumping+Chess%26settings%3Djumping&submit=Edit

Is this ready for me to post? It looks like everything is correct except for highlighting moves that wouldn't be allowed when a mandatory edge capture is available. (It still doesn't let you actually make the illegal move, so that's good enough.)

🕸Fergus Duniho wrote on Sat, Oct 10, 2020 05:04 PM UTC in reply to H. G. Muller from 07:29 AM:

@Fergus - What would be the best way to manipulate the $legalmoves array, if I want to remove some moves that in hindsight must not be highlighted after all? Would the following code work?

set tmp $legalmoves;
setsytem legalmoves array; // clear the legal list
for m #tmp:
 if fn SomeTest #m:
   setlegal m;
 endif;
next;

You made a typo. setsytem should be setsystem. With that fixed, it looks like it would work. Since the documentation did not mention that it would work, I updated the documentation. But it will work only for legal moves described as arrays of coordinates for $legalmoves. It will not work for legal moves entered as strings.

H. G. Muller wrote on Sat, Oct 10, 2020 03:49 PM UTC:

Zone confinement now also works for the highlighting, with the aid of the 'user-supplied' BadZone function. And I have implemented non-final-leg e.p. capture in the betza.txt include file now, so that works too.

Only remaining imperfection is that when an edge capture is mandatory it still highlights other moves.

H. G. Muller wrote on Sat, Oct 10, 2020 07:29 AM UTC:

OK, that should simplify highlighting of legal moves. But the rule that (some) captures are mandatory actually is another global rule that creates a difference between legal and pseudo-legal. In Losers Chess this rule has lower priority than the checking rule, here it seems to have higher priority, even when the checking rule would be employed. Pseudo-legal highlighting will be easy here. It will still require me to put a 'hook' into the general code with which a user can interface his own code for the zone confinement; I will make this a function call that passes the full move (fromSqr, toSqr, locustSqr, dropSqr and droppedPiece), which returns whether the move is pseudo-legal, but for efficiency will only be called when a global flag 'zonal' is set.) Besides confinement, such a user-supplied function can also be used for enforcing restrictions what peiec types can capture each other.

It has been useful to attempt this, because it made me discover that the Diagram code had suffered a regression: the Betza compiler used to flag which pieces are inversion-symmetric, so that the GAME-code generator in the wizard page could draw on this to decide whether separate table entries should be made for white and black pieces. This code had disappeared!

I am now thinking how the general GAME-code in the include file could be enhanced in order to interface with variant-specific code. Rule enforcing is in general easy, as when there are extra global rules that outlaw some pseudo-legal moves, you can just test for compliance to these independently of the normal code (e.g. before you call the latter), and 'die' if they are violated. But legal-move highlighting requires such a compliance test to be called from somewhere deep inside the standard code, after the MakeMove of of every pseudo-legal move. Normally the code only does a check test there, and pushes the moves to the legal list when it doesn't expose the King.

The problem with mandatory capture is that you have to know in advance whether such a capture is possible to judge whether a non-capture (or in this case also a non-mandatory capture). An obvious way to do that would be to first make a list of all moves that are legal ignoring the rule, and then test whether there is a mandatory one amongst these. If there is, all non-mandatory moves should be purged from the list. This could be done entirely after the standard code. If I would know how to revoke a previous setlegal command.

@Fergus - What would be the best way to manipulate the $legalmoves array, if I want to remove some moves that in hindsight must not be highlighted after all? Would the following code work?

set tmp $legalmoves;
setsytem legalmoves array; // clear the legal list
for m #tmp:
  if fn SomeTest #m:
    setlegal m;
  endif;
next;

I have another question about GAME-code syntax. In

if fn F X or B:

would this be read as if( B || F(X) ) or as if( F(B || X) )?

Number of ratings: 7, Average rating: Good, Number of comments: 30

List all comments and ratings for this item.

Add a comment or rating for this item.

The Chess Variant Pages is an amateur, hobbyist website that has been run by volunteers since it was founded in 1995. It focuses on documenting games based on, related to, or similar enough to Chess and on letting you play many of them.

Who What When Where Why Which How

Privacy

Operating expenses are covered through advertising and donations. Help out by making a PayPal donation or by shopping with these affiliate links:

https://www.chessvariants.com/index/editcomment.php
First Created: Thursday, February 10th, 2000
Last Modified: Friday, October 2nd, 2020
File Timestamp: Wed, 14 Jul 2021 21:37:27 +0000
[info] [links] [edit]

Enter Your Reply

Top level header: <H1>

Secondary Header: <H2>

Third Level header <H3>

Top level header: `<H1>`

Secondary Header: `<H2>`

Third Level header `<H3>`