The appearance of "pass"

[sosolyos]

Hello, I'm encountering some issues with this project during actual gameplay that I'd like to consult about. When I make a move and then ask the algorithm for the next step, the system outputs a "pass". In my understanding of Hex rules, there is no need for a "pass" to occur. So, I'd like to ask what is the logic behind this "pass", and if I want to eliminate the pass decision step (to make it normally choose the best step), which file should I modify and how? What would be the consequences of removing the "pass"? Thank you.

[selinger]

It's a feature of KataHex that it will pass when it considers a position to be hopeless. Because KataHex is derived from KataGo, and passing is permitted in Go, there is no easy way to change that without altering the model. In any case, this issue comes from upstream KataHex https://github.com/hzyhhzy/KataGo/releases/tag/Hex_20240908

I personally rarely use genmove. I just use it for analysis (the calculator button, or shortcut "s"). In that mode, it just ranks the possible moves and does not consider passing.