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.
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.