Check out Atomic Chess, our featured variant for November, 2024.


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

Comments/Ratings for a Single Item

Earlier Reverse Order Later
CWDA & Joker[Subject Thread] [Add Response]
Aurelian Florea wrote on Thu, Sep 19 04:31 PM UTC:

One of my long term goals is to create a CWDA game that has jokers. It seems to me weird to have the joker imitate a piece from the enemy army. So I had thought at a transferrer. A piece that transfers the power from the enemy piece to it's counterpart from my army. So if such a piece should exist in the classic Betza's CWDA for example if the opponent moves a BEDE I get to move a charging rook (in a NN versus a CC). One trouble is that no programs implements this yet, firstly because that has not crossed anyone's mind. I can make my own program (I am progressing at my work for an apothecary chess program by the way) but this takes a bit of time. I'd like to try some basics. Anyone, any Idea how. Maybe the ID HG? It seems difficult to me though.

Anyway is the transferrer an interesting concept, or the joker should be enough even in this context?


H. G. Muller wrote on Thu, Sep 19 05:19 PM UTC in reply to Aurelian Florea from 04:31 PM:

Anyway is the transferrer an interesting concept, or the joker should be enough even in this context?

Well, I dislike Jokers to begin with, so perhaps I am not the right person to comment on this. In principle you can make this as complex as you want: not imitate the piece that was moved, but for each possible type define the type the Joker should move as independently. This way you could also define partical imitation: e.g. if you want to disallowe.p. capture and double push when imitating Pawns, you could define a (no-participating) Pawn without these moves, and ilet the Joker imitate that when a Pawn is moves.

This could be implented by having the user define an array to map (moved) piece types onto (imitated) piece types. In the code you would then simply replace "imitated = movedPiece" by "imitated = transfer[movedPiece]". By default the transfer array would map every type on itself.


Aurelian Florea wrote on Thu, Sep 19 05:23 PM UTC in reply to H. G. Muller from 05:19 PM:

You mean, this can be done in the ID? I mean without you putting in extra work.


H. G. Muller wrote on Thu, Sep 19 06:29 PM UTC in reply to Aurelian Florea from 05:23 PM:

No, it would require some extra programming. But not very much.


Aurelian Florea wrote on Thu, Sep 19 06:35 PM UTC in reply to H. G. Muller from 06:29 PM:

As you wish. Thanks for your input, though!


5 comments displayed

Earlier Reverse Order Later

Permalink to the exact comments currently displayed.