Greg Strong wrote on Fri, Apr 26, 2019 03:03 PM UTC:
That is indeed a clever workaround, but it is a fairly ugly hack. So I've started the painful process of having different piece -> notation mappings for each player. Hopefully it won't be too bad.
I have hit my first road block however. It seems that communication of promotion moves in CECP always uses the lower-case. The example given in the standard documentation is "e7e8q". Clearly, this is white's move, but the q is lower-case. This far, I have always been sending in lower case. How do we address this? If I go forward with this change blindly, it will send promotion q for black but Q for white - which totally makes sense, but I'm afraid it will break engines that aren't expecting it. An alternative, which seems ok (but please check my logic here) is to send the notation for the player which is moving, but forced to lower-case. This shouldn't break anything, and it seems it will still work with what you are proposing.
That is indeed a clever workaround, but it is a fairly ugly hack. So I've started the painful process of having different piece -> notation mappings for each player. Hopefully it won't be too bad.
I have hit my first road block however. It seems that communication of promotion moves in CECP always uses the lower-case. The example given in the standard documentation is "e7e8q". Clearly, this is white's move, but the q is lower-case. This far, I have always been sending in lower case. How do we address this? If I go forward with this change blindly, it will send promotion q for black but Q for white - which totally makes sense, but I'm afraid it will break engines that aren't expecting it. An alternative, which seems ok (but please check my logic here) is to send the notation for the player which is moving, but forced to lower-case. This shouldn't break anything, and it seems it will still work with what you are proposing.