You are on the backup site for Chessvariants.com. Any posts, moves, or other changes you make here will not be permanent, because the pages and database from the main site will be backed up here every midnight EST. Additionally, things may not be working right, because this site is also a testbed for newer system software. So, if you are not here to test, develop, or merely read this site, you may want to change .org to .com in the navigation bar and go to the main site.



The Chess Variant Pages




[ Help | Earliest Comments | Latest Comments ]
[ List All Subjects of Discussion | Create New Subject of Discussion ]
[ List Latest Comments Only For Pages | Games | Rated Pages | Rated Games | Subjects of Discussion ]

Comments by H. G. Muller

Later Reverse Order EarlierEarliest
Home page of The Chess Variant Pages. Missing description[All Comments] [Add Comment or Rating]
H. G. Muller wrote on 2021-11-25 UTC

This is a preset where the piece images are redefined through assignment to the system variable $pieces, at the end of the Pre-Game section. Apparently the image displayed on the page is generated before this assignment is processed.


H. G. Muller wrote on 2021-11-24 UTC

OK, I changed the shuffle.txt file accordingly. Perhaps Aurelian can try whether the problem is now solved.

Pretty amazing that this did not appear to cause any problems in Play mode.


H. G. Muller wrote on 2021-11-24 UTC

Yes, it is from the GAME code. But is seems the GAME code is right about this: Daniel says below that the initial position is all wrong, and indeed contains no royal.

This is a shuffle game, so it calls the general shuffle code in the Pre-Game section. This performs the shuffling, and stores the result in a constant. So that later invocations of the preset will use that same shuffle. A new shuffle is only made when the constant is not defined. This works fine in Play mode.

Can it be that the constant for remembering the initial position gets corrupted when an invitation is accepted?

For reference, below is the basic principle of the shuffling, by the routine ShuffleSetup called from the Pre-Game code:

sub ShuffleSetup:
  // performs the shuffles described in the above arrays
  if isconst startshuffle:        // shuffle has already been determined
    setsystem space startshuffle; // retrieve it
  else:                           // new game; must shuffle
    ... // shuffle the initial setup in $space
    setconst startshuffle $space;        // save the shuffle for persistent use
  endif;
endsub;

 


H. G. Muller wrote on 2021-11-23 UTC

Doesn't the fact that the code work perfectly in Play mode prove that the problem is not in this code, then?

I have no way to debug other code than what the one the user can provide. As far as I understand GC the only way that after accepting an invitation GC declares a loss would be when the GAME-code executes a resign command without getting any input. I am pretty sure my code doesn't do that. It definitely does not do that when you press Play in the preset menu. How does what happens when pressing Play differ from accepting an invitation?


Chess with Different Queens. players choose their super pieces.[All Comments] [Add Comment or Rating]
H. G. Muller wrote on 2021-11-23 UTC

From the description (both here and of the Sliding General), shouldn't it be a three‐path lame dabbabah?

Well, the description was KtfsF, so I assumed a W as second step was out.

Another enhancement I had considered was to just add the Wazir move to the existing Griffon pattern.

That was the first thing that came to my mind as well, but I was afraid this would make it too strong. IIRC the value for the Griffon I measured was 8.2, and 4 extra moves easily up the value by 2 Pawns, even for a Rook. Just bending a trajectory in another shape is more like adding extra squares at the end of the trajectory: all the normal Griffon move now become more easily blocked. This should partly compensate the effect.


H. G. Muller wrote on 2021-11-23 UTC

The inequality here doesn't seem to be worse than that between Betza's classical CwDA armies, which can run up to 1.5 Pawn. An Archbishop is only about 0.75 Pawn weaker than a Queen. The KNAD is worth about 1.5 Pawn more than a Queen, but the distant moves here are all lame, which might weaken it more than that. The Griffon is the weakest of the bunch. A possible enhancement of it could be a W-then-R that turns a 90-degree corner, which has a similar move pattern, but also attacks the W squares.

Even if the strengths vary a lot, there is of course no need to play the strongest against the weakest. Or only reserve that for games between players of unequal strength, as a sort of handicap.

Note that the Betza notation used in the article (e.g. FtR) is non-standard, neither original Betza (t[F,R]) nor XBetza (FyafsF). As a consequence it is not entirely clear to me how the Lion moves. I suspect it is the compount of a King, a Xiangqi Elephant, a Xiangqi Horse and a two-path lame Dabbabah (XBetza KaFafsW).


Home page of The Chess Variant Pages. Missing description[All Comments] [Add Comment or Rating]
H. G. Muller wrote on 2021-11-23 UTC

Some additional info: the preset is automated through code generated by the Play-Test Applet, but in 'Play' mode this code appears to work fine. In particular there is no spurious declaration of game end by the Post-Game code sections. I don't know whether it is possible that the provided GAME-code would use a variable name that is also in use by Game Courier for other purposes, and confuses the system.


Opulent Chess. A derivative of Grand Chess with additional jumping pieces (Lion and Wizard). (10x10, Cells: 100) [All Comments] [Add Comment or Rating]
H. G. Muller wrote on 2021-11-22 UTC

Well, because of the acclamation then:

files=10 ranks=10 satellite=oppulent graphicsDir=/graphics.dir/alfaeriePNG35/ holdingsType=1 promoZone=3 maxPromote=1 squareSize=35 graphicsType=png lightShade=#FFFFCC startShade=#6A8D8B rimColor=#804646 coordColor=#FFFFFF borders=0 firstRank=1 useMarkers=1 promoChoice=*Q*C*A*R*L*N*B*W!P symmetry=mirror pawn::fmWfceFifmnD::a3-j3 wizard::FC:mage:b1,i1 bishop::::d2,g2 knight:N:NW:knightwazir:c2,h2 lion::HFD::b2,i2 rook::::a1,j1 archbishop::BN:cardinal2:j2 chancellor::RN:chancellor2:a2 queen::::e2 king::K::f2

Oppulent Chess


Variants playable against the diagram's AI. Index of variants that can be played against the interactive diagram.[All Comments] [Add Comment or Rating]
H. G. Muller wrote on 2021-11-22 UTC

OK, I added those to the list.

Some time ago I slimmed down the Quiescence Search of the diagram's AI, because in large variants with many powerful pieces it was still prone to search explosion. (It now unconditionally searches only Low x High captures that capture the last-moved piece, or punish moving away a (soft-)pinned piece; other captures need to consume part of any remaining depth budget.) Because of this diagrams that used impractically long thinking time might now perform acceptably. For instance, after this change I had no problems having the Diagram play Macadamia Shogi against Ai Ai. (But I still don't want to add Macadamia Shogi to the list, because it is not possible to enter the triple capture of the Lion Dog. Even though in practice there probably will never be an opportunity to make such a capture.)


kings cross. Missing description[All Comments] [Add Comment or Rating]
H. G. Muller wrote on 2021-11-21 UTC

I agree that in the current description it is not clear which piece is which.

I have some worries that this variant could be extremely drawish. A closed rank of (non-royal) kings or Shogi generals is unapproachable by opponent steppers, because they attack each square in front of the 3 times, and without support from longer-range pieces from behind the opponent cannot top that. So you run into stand-offs very easily.


About Game Courier. Web-based system for playing many different variants by email or in real-time.[All Comments] [Add Comment or Rating]
H. G. Muller wrote on 2021-11-20 UTC

I think you have to submit drawn as a move. In a rule-enforcing preset you have to make sure the preset would accept that GAME-code command.


bullet chess. Missing description[All Comments] [Add Comment or Rating]
H. G. Muller wrote on 2021-11-19 UTC

As Pritchard once wrote: "it only takes 10 seconds to invent a new chess variant, and unfortunately some people do". We can now extend this thesis with: "it takes only 10 seconds to submit a CVP article, and unfortunately some people do"...


Sin-yeon-sang-gi (新演象棋). I dramatized Sin-yeon-sang-hui (新演象戱), one of the variations of the Joseon Dynasty, in Xiangqi style.[All Comments] [Add Comment or Rating]
H. G. Muller wrote on 2021-11-19 UTC

When Cannon captures the Rhino, the text "I win!" appears. But it's not a checkmate situation at all. What error is this?

When you do not explicitly specify a royal piece through a parameter royal=N, the diagram assumes the last piece in the list is the royal one. In this case that is the Rhino. By default the diagram assumes extinction royalty. So when the diagram captures the second Rhino, it assumes it won the game.

Either re-order your piece lines in the diagram definition so that the King is last, or add a line royal=8.


Simple Mideast Chess. Game with simple rules, no promotion, no nonstandard move or capture, no asymetric pieces, and no check, checkmate or stalemate.[All Comments] [Add Comment or Rating]
H. G. Muller wrote on 2021-11-17 UTC

Rule 3 is also not a rule, but a consequence of rule 2. There also seems to be a problem with draw rule 3, because it could be hard to prove something is forcible. The 'insufficient mating material' rule in FIDE is based on existence of help mates, not of forcible mates. Of course mate doesn't end the game here, and letting your king be captured is possible in any material combination. With the rule as stated here there could easily be disputes in late end-games whether the advantage of a player is large enough to force king capture. (The player that is behind might prefer to claim a draw over actually defending it, when defense is very difficult.) I suggest either to replace the rule by that of FIDE, phrased as that no position can be reached from which capture of the king can be forced in a single move. Either that, or provide an exhaustive list of piece combinations that count as 'material draw'.

Also note there seem to be no provisions for draw by repetition or number of reversible moves.


Grand Apothecary Chess-Classic. Very large Board variant obtained trough tinkering with known games.[All Comments] [Add Comment or Rating]
H. G. Muller wrote on 2021-11-14 UTC

I think we will need Fergus' help for this. When I use the preset in Play mode it doesn't declare game end during the first few moves. I think that proves that the Post-Game code cannot be responsible for the observed termination.


H. G. Muller wrote on 2021-11-11 UTC

All I can say is that when I use the link you last gave (with FireFox, or the Android browser on my tablet), and select 'Play' from the menu, I get a different start position as what was initially shown. And when I then go back to the previous page, and press Play again, I get yet another setup. And it gets shuffled in the way that was specified. So the preset appears to be OK.

Perhaps others could try to see if they have the same experience.


H. G. Muller wrote on 2021-11-10 UTC

It does shuffle for me. What I meant is that you gave two links, to different presets, in this comments topic, and that these use different piece IDs.


Chu Shogi. Historic Japanese favorite, featuring a multi-capturing Lion. (12x12, Cells: 144) (Recognized!)[All Comments] [Add Comment or Rating]
H. G. Muller wrote on 2021-11-09 UTC

Sure, you are welcome to use them. As far as I am concerned, they are public domain. I am happy you like them.


H. G. Muller wrote on 2021-11-09 UTC

I did.


Gwangsanghui(광상희). A large, historical variant of Janggi, with two more generals that lead each flank and 6 more kinds of pieces.[All Comments] [Add Comment or Rating]
H. G. Muller wrote on 2021-11-09 UTC

How about 'Sniper'?


H. G. Muller wrote on 2021-11-07 UTC

'Ambush' seems a very applicable name for a piece that cannot move, and just has to sit still until it can jump on an unsuspecting bypasser. So I think the move description as capture-only is correct. It would not be a very strong piece, but that in itself is no argument. Who says that peices always have to be strong? And it might be more valuable than you think. It doesn't require a blunder of the opponent to involve the piece in tactics. The squares that it attacks are strongholds, where friendly pieces have one extra protector. Presumably the value of the Ambush would increase after its first capture, because this helps in developing it and increasing the number of attacked squares, both in number and in importance. So pieces on their target squares are protected against equal and even slightly less valuable attackers, as any trading loss would be offset by the increased usefulness of the Ambush after it recaptures.


Grand Apothecary Chess-Classic. Very large Board variant obtained trough tinkering with known games.[All Comments] [Add Comment or Rating]
H. G. Muller wrote on 2021-11-06 UTC

You had not given me that link before, so I was looking at another preset. In this new one you forgot the closing parenthesis (and semi-colon) of the shufflespecs array.


H. G. Muller wrote on 2021-11-04 UTC

Well, I did not see it in the preset (link you gave earlier in this comment thread).

And no, that is not supposed to work, because it seems to use other piece IDs than the preset.


H. G. Muller wrote on 2021-11-04 UTC

When you try what? I see no change in the preset.

BTW, the GAME-code generation should now also work properly when all pieces in a shuffle groep have a colon prefix.


H. G. Muller wrote on 2021-11-04 UTC

Ah, I did not really look at the Diagram, just at the preset. You can just add the fourth group to the shufflespecs array, as another triplet. You have to put one piece (e.g. Bishop) in the first element of the triplet, and all the others in the second.

I took your Diagram definition from the page source of your article, and pasted it into the Play-Test Applet to generate GAME code. Indeed it turned out that the two groups for which you wanted symmetric shuffling were not put into the shufflespecs array. The reason appears to be that you put the colon (:) to request symmetric shuffling on all pieces of the group. The GAME-code generation apparently cannot handle that. And I never noticed that, because I tend to mark all the pieces but one with a colon. The last piece then must be placed symmetrically as well, as the only open spaces that are left will be symmetrically positioned. If I removed the colon on one of the pieces in each group in the Diagram's shuffle parameter

      shuffle=:B:N:EF,QUT,DI,:LY

then the GAME code gets properly generated:

set shufflespecs (
  (F) // shuffleset
  (B N E) // symmetrized
   0
  (Q T U) // shuffleset
   0
   0
  (D I) // shuffleset
   0
   0
  (Y) // shuffleset
  (L) // symmetrized
   0
   0 // mirror to get black
);

(beware the Diagram uses other piece IDs than your preset!). I will fix the JavaScript for GAME-code generation in the Play-Test Applet such that it can also handle the case where all pieces in a shuffle group have a colon prefix. (As the Diagram itself doesn't seem to have any trouble with that.)


25 comments displayed

Later Reverse Order EarlierEarliest

Permalink to the exact comments currently displayed.