Hi,
a quick win: now that the triggering is smarter, engine weakening can be chosen as limiting either depth (as before) or nodes.

In the first version, reaching a specific depth was rather easy to check from the info lines provided by the engine, but reaching a target nodes number was not reliable. The engine could decide to move early, after a lower number of nodes reached (maybe forecasting any further search would too much overstep the target, maybe considering the move obvious or without any decent alternative). Since I now use a smarter triggering, this tricky case with nodes limit is no more any issue.

The change in the code is very light; now you have to edit the Wrapper header to set either LIMIT_TYPE = "depth" or LIMIT_TYPE = "nodes", and that's pretty all. Then, as usual, enter values for the chosen limit and delay.

Attachment provided. Hope this helps,
Tibono
ps: with more tests I saw some engines don't understand uppercase values for "go depth" or "go nodes"; hence please set limits as fixed above, using lowercase for values. I'll re attach the fixed zip file in a following post.