I am trying to do the split now, but in doing this I became aware of some bugs:
The routines cbShortRangeGraph and cbLongRangeGraph in the base model did not enforce brouhaha squares for special moves; moves with FLAG_SPECIAL should also be suppressed. Failing to do so allowed the Fire Dragon in Minjiku Shogi to enter an empty brouhaha square, as all its moves are special because of the burning, and eventually come from cbLongRangeGraph.
What is worse is that the way I implemented the brouhaha squares would suppress storing moves without any mode flags, (assuming that the brouhaha squares would have removed those that would normally be possible), while cbAdvancerGraph tries to generate the entire graph this way (in order to apply the flags later). I could rewrite the latter, but variant implementations we are not aware of might count on the old behavior of cbShort/LongRangeGraph. So I think it is better to change those, and store all-zero flags if this was explicitly requested in the call.
I am trying to do the split now, but in doing this I became aware of some bugs:
The routines cbShortRangeGraph and cbLongRangeGraph in the base model did not enforce brouhaha squares for special moves; moves with FLAG_SPECIAL should also be suppressed. Failing to do so allowed the Fire Dragon in Minjiku Shogi to enter an empty brouhaha square, as all its moves are special because of the burning, and eventually come from cbLongRangeGraph.
What is worse is that the way I implemented the brouhaha squares would suppress storing moves without any mode flags, (assuming that the brouhaha squares would have removed those that would normally be possible), while cbAdvancerGraph tries to generate the entire graph this way (in order to apply the flags later). I could rewrite the latter, but variant implementations we are not aware of might count on the old behavior of cbShort/LongRangeGraph. So I think it is better to change those, and store all-zero flags if this was explicitly requested in the call.