I'm wondering if there is some change in defaults that I missed which would make the betzaNew.js diagram able to swap with a King?
This is now fixed too. The problem was that the code that rejected capture of your own King did not account for the possibility that the captured piece would be unloaded. This rejection would also cause incomplete execution of the move when it was nevertheless played.
I now made it ignore friendly King capture when the origin is also mentioned as an unload square. This is just a temporary fix, as it would still forbid displacement of a friendly King to another square.
Of course there still is the problem of how you could benefit from this fix, as the server will only show the no-longer existing version of betzaNew.js to its users. A trick that worked for me is to add the suffix ?t=XXX to the link to betzaNew.js, with XXX a string that was never used before.
This is now fixed too. The problem was that the code that rejected capture of your own King did not account for the possibility that the captured piece would be unloaded. This rejection would also cause incomplete execution of the move when it was nevertheless played.
I now made it ignore friendly King capture when the origin is also mentioned as an unload square. This is just a temporary fix, as it would still forbid displacement of a friendly King to another square.
Of course there still is the problem of how you could benefit from this fix, as the server will only show the no-longer existing version of betzaNew.js to its users. A trick that worked for me is to add the suffix ?t=XXX to the link to betzaNew.js, with XXX a string that was never used before.