since the problem has happened many times，I
think the mark phase need to be improved.
There are four possible cause to the problem:
1.the program defines all stones in chessbord as lived before players make judgements.
2.Those points which connect with both b and w
are defined as something like shared-libs.
3.There isn’t a function to check if all points are colored.
4.There isn’t a function to continue an over game when players disagree the result.
From my experience in other go website I think the program may be improved as follow.
- After three pass, make players point the died stones immediately before the program auto-mark those points.
- Add a button to continue an over game when players have disagreements.Then if it spend too much time in pointing died stones, program makes a timeout-restart. The first-pass side go first.
- Add a function to check if all points are colored.For the shared-libs they can be equal attributed.If the num of shared-libs is uneven number the first -pass side gets the last one.
For example
ThreePass
while( sum( point_b, point_w, stone_b,stone_w)~=361&& timeout~=1&& continue_button~=1)
Timer
Point_died_group
Color_point % care about the shared-libs
End
Define_winer
I’m hurry to think about it and I’m very sleepy now.So just regard it as a suggestion.Maybe there are many mistakes.