Unfortunately it is not very easy to include the bent riders. For one, their retrograde moves are not the same as their normal moves. The current program assumes they are, and uses the same move generator for both. It would also raise the design problem for how to indicate the bent slides.
The current move-definition pane does allow you to define limited-range sliders such as R2, btw. Just define a regular Rook by clicking the W squares twice, and then for each paths click the H square to cut off the slide there. Usually the ability to jump doesn't have much use at this stage of the game; both WD and R2 can force checkmate in the same number of moves. It is just the statistics that changes a bit.
So R2-then-B can certainly force checkmate, as R2 already can. B2Z reaches a subset of the B2-then-R destinations, and it is also able to force checkmate. So I expect the B2-then-R to do it even faster, as the fact that it cannot leap directly to the Z squares should hardly hinder it.
Unfortunately it is not very easy to include the bent riders. For one, their retrograde moves are not the same as their normal moves. The current program assumes they are, and uses the same move generator for both. It would also raise the design problem for how to indicate the bent slides.
The current move-definition pane does allow you to define limited-range sliders such as R2, btw. Just define a regular Rook by clicking the W squares twice, and then for each paths click the H square to cut off the slide there. Usually the ability to jump doesn't have much use at this stage of the game; both WD and R2 can force checkmate in the same number of moves. It is just the statistics that changes a bit.
So R2-then-B can certainly force checkmate, as R2 already can. B2Z reaches a subset of the B2-then-R destinations, and it is also able to force checkmate. So I expect the B2-then-R to do it even faster, as the fact that it cannot leap directly to the Z squares should hardly hinder it.