Check out Glinski's Hexagonal Chess, our featured variant for May, 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 ]

Single Comment

Dealer's Chess. Armies are chosen by dealing special cards. (8x8, Cells: 64) [All Comments] [Add Comment or Rating]
🕸Fergus Duniho wrote on Wed, Nov 29, 2023 07:01 PM EST in reply to Bob Greenwade from 06:07 PM:

Can/should I treat the ID on the card as something different from the GAME code ID?

Piece labels and card IDs are in two separate namespaces. So, they don't have to coincide. However, it is sometimes practical to use the same names in two different namespaces. For example, I used to use function and subroutine names that matched piece labels, because this let me more quickly call the right function or subroutine without using a bunch of if-then statements. Since the cards in your game match only pieces, and each piece is going to require a unique notation, it does make sense to let them match up.

Since piece notation should be lowercase for one side and uppercase for the other, this restricts you from using mixed case piece notation. But since your cards do not represent pieces on one side or the other, you could still use mixed case IDs that otherwise match the piece notation but add some clarification on whether neighboring letters mean two different things or mean one thing together. For example, you might use C for the Camel, Cn for the Cannon, and CNZ (Camel+Knight+Zebra) for the Buffalo.

I recommend starting by coming up with a piece notation that makes sense and isn't too cryptic or confusing, then decide whether you want to use it for the IDs on your cards.