Reducing too much

[Henk]

Because of all kind of reductions and pruning (for instance null move, LMR, futility), it may happen that some moves are reduced too much which might cause severe errors.

Sequences like Null Move -> LMR -> Null move -> LMR etc. easily result in large reductions.

Are there some rules which prevent the search algorithm from reducing too much? For instance no LMR within null move reduction, or no null move reduction within LMR, or no null move below some depth.

Of course reducing too little might be even worse.

[Daniel Shawul]

Bump! Only time i found your posts more useful than the EGTB spam

Well about the content, all i have to say is it is all heuristics. Try and retain what works for you