Comments/Ratings for a Single Item

How can I make an interactive diagram that can switch between greenwade and alfaerie graphics? Is there a way to change the image names associated with pieces dynamically?

There was indeed a fatal bug that would cause an immediate crash. I don't know how this crept into the betza.txt include file; I had seen that bug before, and fixed it, and when I tested Megalomachy it worked.Which would not have been possible with this bug. It must have reverted somehow, by the version I have on my PC and the version here on CVP being out of sync.

Anyway, I applied the fix again, and that seems to make it work. (I am not sure it would work if the King only makes a single step, though, as this is ambiguous.)

https://www.chessvariants.com/play/pbm/play.php?game=Megalomachy&settings=default

https://www.chessvariants.com/play/pbm/play.php?game=Waffle+Chess+with+Gryphon+and+Falcon&settings=default

Link?

I have noticed that both my megalomachy and frog chess with gryphon and falcon give an error related to fast castle. Probably it is not a coincidence!

I have made the modifications you have suggested, and now it works as expected.

I think you misinterpreted what is happening. The Heavy Cannon cannot jump an enemy Light Cannon. But it can jump friendly Cannons of both kinds. Which is how you configured it: the captureMatrix allows setting of enemy and friendly interactions separately, and you wrote the $ only in the position for the enemy interactions. The friendly interactions would come behind those on the same row. (But can usually be ignored, as friendly capture is rarely allowed. But friendly hopping is common, and if you want to ban that you will need to specify it.)

By writing an = at the end of a row spec in the captureMatrix it will use the same values for the friendly interactions as you have given for the enemy interactions in that row.

An unrelated thought:

I suppose the captureMatrix is a cleaner method for specifying friendly (or enemy) hopping than the dau (or cau) kludge in the XBetza notation. Just define the move with pa instead, and then forbid the enemy hopping in the captureMatrix. An Advancer could then be written as mQyafmcopabQ. (It doesn't work in generated GAME code, though, as this does not support the captureMatrix yet.)

Oh, yes!

I'm sorry!

In a moment!

Actually I think we still have a problem. The heavy cannon can jump (but it cannot capture) the light cannon. This can't be an capture matrix thing because $ should do them both!

Well, without a link to the offending Diagram there is little I can do to assist...

Actually I think we still have a problem. The heavy cannon can jump (but it cannot capture) the light cannon. This can't be an capture matrix thing because $ should do them both!

Oh, a silly trivial mistake on my part. Thanks!

The first position in each row is for the non-capture. So if the Cannons are number  12 and 13 in the table, the Cannon x Cannon indications would need to be in the 13th and 14th element of the row. So 12 'nothing special' positions in front of them.

There is no row for empty squares, as empty squares cannot be moved. So you would have to specify this in the 12th and 13th row of the matrix. But it seems you are doing it in the 13th and 14th.

Maybe it is better if I explain what I want to do.

So there are these two pieces (in position 12 and 13):

  lightcannon:X:mRcpR:cannon:a4,n4,,a11,n11
  heavycannon:Y:pRpafcpR:warmachine:a2,n2,,a13,n13

The rule I want to implement is that heavy cannons cannot jump, be jumped, captured or be captured by other cannons. My captureMatrix looks like this:

  captureMatrix=////////////11$$./11$$./

but probably I got it wrong.

Note the heavy cannon is a bit more than a korean cannon is as it can jump two platforms in order capture, but not move.

I think you have Missed my previous comment here, HG!

I was out of town for the computer-chess tournament in Zundert.

I don't know how to say that the source piece cannot hop to move, to capture, or capture said type. Meaning both ? and $.

I am not sure what you are asking. If you cannot hop to move or capture, you cannot hop at all, right?

$ indicates you can neither hop over, nor capture said type. If you can capture, but not hop, it would be indicated by ^. It is not possible in general to specify multiple effects for the same piece-combination in the captureMatrix, and in most cases this would not be meaningful anyway. (E.g. it makes no sense to specify what you promote to is the capture is forbidden.) The hop ban is special in this respect, as it does not refer to the occupant of the destination square, so that the move can involve 3 piece types. To cover the case of the Korean Cannon I introduced the $ symbol.

I think you have Missed my previous comment here, HG!

I don't know how to say that the source piece cannot hop to move, to capture, or capture said type. Meaning both ? and $.

Can someone suggest an example where the capture matrix is used?

Minjiku Shogi, Makromachy. For Golem Chess I described how it could be done in the Comments. (At that time I had already made an I.D. in the old way, uses a WeirdPromotion custom script.)

Can someone suggest an example where the capture matrix is used?

I tried something similar, and it does work as expected using betzaNew.js. But not with betza.js. Which does surprise me, as I had not expected it to be different in this respect, so I will look into that.

And make sure to set maxPromote=0 to disable the normal promotion by zone rather than by morph.

[Edit] It appears that multiple promotion sets were never implemented in betza.js.

I don't understand how to use morph for optional promotions. I have promoChoice=W/PH/PF/PQ/PS/VH/VF/VQ/VS and two pieces, P and V, with morph=*/5/6/7/8 and morph=*/1/2/3/4 but it won't work right. What I expect is that each piece would have one optional promotion on each of the 4 ranks before the last. Instead, they either get all the promotion options at the same time or none.

I have now done that too. But betzaNewer.js is experimental, and sooner or later will replace betzaNew.js and disappear itself (because it is fully compatible).

Let's not forget about betzaNewer.js (the one with the experimental Shogi promotion system).

It would be really nice if you could deselect a piece that you have just selected in the holdings.

OK, I now implemented this both in betza.js and betzaNew.js. (Every click in the holdings was treated as a first click, to prevent you could move pieces into the holdings, or between holdings squares. But a click on the already selected piece there indeed deserves to be an exception.)

@Fergus: I can no longer upload these .js scripts through the File Manager page of the Interactive Diagrams article. I get this error message:

Upload of /home/chessvariants/public_html/membergraphics/MSinteractive-diagrams/betza.js was allowed but failed! The cause of failure is unknown.

Upload through WinSCP still works.