Feature Request: Support dynamic search width / playout limits by move number

[huangyao123png]

I'm training and testing KataGo selfplay engines. I want to suggest adding a feature to support dynamic adjustment of search width (playout limits) by move number. Motivation: In real gameplay, it's often useful to apply stronger search in the opening and early middle game, and reduce the search budget later on to save time or speed up selfplay training.

Example use case: I would like to configure the engine like this:

• From move 1 to 50: searchMaxPlayouts = 1000
• From move 51 to 90: searchMaxPlayouts = 800
• From move 91 onward: searchMaxPlayouts = 500 Introduce a config section like: yaml searchPlayoutSchedule:
  • move: 1 playouts: 1000
  • move: 51 playouts: 800
  • move: 91 playouts: 500

The engine can read the current move number and apply the matching playout limit.

Would this be possible to implement in future versions?