Optional aga_Optional allow_Optional allow_Optional allow_Optional automatic_Optional black_Optional black_Optional boardOptional board_Optional clockOptional disable_Optional end_Optional errorsOptional free_Optional game_Optional game_Optional game_Optional group_Optional handicapOptional handicap_Optional heightOptional initial_Optional initial_Optional is_Optional isobranch_Optional komiOptional ladderOptional ladder_Optional latenciesOptional marksOptional move_Optional movesOptional needs_Optional ogsOptional ogs_Deprecated, I don't think we need this anymore, but need to be sure
Optional opponent_Optional original_Optional original_Optional outcomeOptional phaseOptional playerOptional player_Optional player_Optional playersOptional rankedOptional removalOptional removedRemoved stones in stone removal phase Passing an array of JGOFMove objects is preferred, the string format exists for historical backwards compatibility. It is an encoded move string, e.g. "aa" for A19
Optional rengoOptional rengo_Optional rengo_Optional review_Optional reviewsOptional rulesOptional scoreOptional score_Optional score_Optional score_Optional score_Optional score_Optional score_Optional stalling_Optional start_Optional strict_Optional superko_Optional throw_When loading initial state or moves, by default GobanEngine will try and handle bad data by just resorting to 'edit placing' moves. If this is true, then those errors are thrown instead.
Optional time_Optional time_Optional tournament_Optional white_Optional white_Optional white_Optional widthOptional winner
Intersections that need to be sealed before scoring should happen