Check out Makruk (Thai Chess), our featured variant for March, 2025.


[ 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
Andernach Chess. Pieces change side when taking.[All Comments] [Add Comment or Rating]
Ed Friedlander wrote on Mon, Jan 15, 2007 12:55 PM UTC:
Does a pawn capturing an opposing unit on the eighth rank promote, or become a pawn of the opposite color? If the latter, is it then entitled to a double-move on the opposite-color's first rank and/or second rank?

Andreas Kaufmann wrote on Mon, Jan 15, 2007 09:50 PM UTC:
According to http://www.janko.at/Retros/Glossary/Andernach.htm the pawn
promotes first and then changes the color.

HaruN Y wrote on Thu, Jan 30 02:17 AM UTC:

Interactive diagram: pieces movable, right-click resets!

 
 8 
 7 
 6 
 5 
 4 
 3 
 2 
 1 
abcdefgh    

Click here to open/close a piece overview. Play it!

The captureMatrix parameter doesn't seem to work properly for black.


H. G. Muller wrote on Wed, Feb 12 09:32 AM UTC in reply to HaruN Y from Thu Jan 30 02:17 AM:

This Diagram appears to work (in isolation). There was a bug in the routine that displayed the capture matrix after 2x 'here', though, which could not handle promotion to foe when it translated the internal numeric codes back to a piece ID for display. I now fixed that bug.

Unfortunately fixes to betzaNew.js don't show up for users of this website; they will always use the old, buggy version that no longer exists on the server, even when they flush their browser cache (even after directly displaying the file in their browser), and append the ?nocache=true suffix. I found a work-around to this; I appended another item to the query string (which the server would discard anyway, but which fools all caching agents to think this file has never been loaded before). In this case &t=5. (I suppose I could have left out the nocache=true part, and just append ?t=5, as the former doesn't appear to have any effect anymore.) Of course this is a one-time cure; the next fix I make in betzaNew.js would still not become visible, unless you change the t=5 into something else that was never used before by you or anyone else.


4 comments displayed

Earlier Reverse Order Later

Permalink to the exact comments currently displayed.