panjd123 / turingnogo Goto Github PK

In the explanation of the rule,

如果一方落子后吃掉了对方的棋子，则落子一方判负（顾名不围棋）
对弈禁止自杀，落子自杀一方判负
注意：不可能平手，无处落子时只能认输或者自杀

There is an ambiguity on suiciding. According to the second sentence, it means to put a stone to be captured, then the last sentence should be modified to "无处落子时只能认输、自杀或吃掉对方的棋子".

In the current protocol used by TuringNoGo, the repeated READY_OP operation is used for confirmation. However, the Role field for the repeated READY_OP is currently marked as optional in the protocol specification. This optional designation may cause confusion for the client, as it may interpret the repeated READY_OP as an application rather than a confirmation.

To improve clarity and prevent misinterpretation, it is recommended to update the protocol specification to clearly indicate that the Role field should be left empty when sending a repeated READY_OP for confirmation.

This clarification will prevent confusion on the client's side and ensure that the repeated READY_OP is correctly understood as a confirmation, even in cases where the initial READY_OP was lost or ignored.

This protocol change is expected to have minimal impact and should not cause significant changes or difficulties for most clients. Many existing clients already follow the practice of leaving the Role field empty when repeating READY_OP for confirmation purposes, even though it is not explicitly specified in the current protocol. By formally incorporating this behavior into the protocol specification, we aim to enhance the robustness and reliability of TuringNoGo and standardize the practice across all clients and provide clear guidance for future implementations.