Check out Janggi (Korean Chess), our featured variant for December, 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
Blizzard ChessA story, poem or other fictional work . What would Chess be like if it had been developed by the computer industry?[All Comments] [Add Comment or Rating]
Larry Smith wrote on Wed, Jun 29, 2005 03:10 PM UTC:Good ★★★★
Disturbingly funny. Its upgrade reasoning has an air of familiarity. ;-)

Larry Smith wrote on Wed, Jun 29, 2005 10:43 PM UTC:
If anyone is interested, I've worked up a Zillions implementation of this game. After about the tenth turn, the field will look like it got hit by a blizzard.

Peter Aronson wrote on Thu, Jun 30, 2005 12:18 AM UTC:
How did you deal with: <blockquote> <b>Patch 1.12</b> <p> Pawns have become too powerful, so we have altered the behavior of the Knight. From now on a Knight may capture a Pawn belonging to the opponent by jumping over it, as well as by landing upon it. This new ability may be used to allow a Knight to capture 2 pieces per turn. Jump Captures may only be performed on Pawns, and no other piece, and cannot be used to place the opponent's King in Check. </blockquote> Since the Knight's path is not defined? Also, if I understand the restriction 'cannot be used to place the opponent's King in Check', that forbids removing a Pawn to create discovered check -- isn't that kind of tricky to test for with Zillions? <p> I'd be interesting in looking at the ZRF . . .

Larry Smith wrote on Thu, Jun 30, 2005 02:40 AM UTC:
Good point about the discovered check with that particular rule.

I used a little programming trick to get this to work.  I'll send you the
implementation so that you can admire it.  But basically, I used the
Zillions engine itself to perform most of the function.

As to the shape of the Knight leap, I opted for the simple 'L' pattern. 
This means that Pawns orthogonally adjacent to the Knight's position are
captured using this rule.  This would continue to allow Pawns to threaten
the Knight un-opposed.  But if there is a big demand to include any
adjacent Pawn, I can implement this in a variant.

This implementation is still in need of some serious play-testing.

Larry Smith wrote on Thu, Jun 30, 2005 03:50 AM UTC:
Peter,

I tried to send you a copy of the implementation.  The e-mails are
returned as undeliverable.  Is your address listed on this site active?

Marc D wrote on Sat, Jul 2, 2005 11:29 AM UTC:
I wonder where to get the zrf file from

My mail adress is [email protected]

Marc

George Duke wrote on Sat, Aug 2, 2008 07:38 PM UTC:
Patch 1.01 d- and e-Pawns no longer move 2 squares. Patch 1.25 deals with asymmetry. Castling asymmetry. 4 possibilities now, Queen castles Queenside, Queen Kingside, King Queenside and King Kingside, all fixed as before.

7 comments displayed

Earlier ⇧Reverse Order⇩ Later

Permalink to the exact comments currently displayed.