I now made a slight modification in the Diagram's AI (of betzaNew.js): the condition under which a move is always searched is changed from total gain > value of capturer (which in conquer could go on for ever, with a crash as result) to one where this only holds for moves that do not unload anything, and that moves that do unload something are only searched if they capture a piece of a type higher than their own. (This assumes pieces in the table are sorted by increasing value.) This thus discards the gain from the recruitment; in the old way RxR would gain you two Rooks, and would qualify; now it no longer qualifies, as R=R. It would still always search RxQ, but then two half-moves later not the reverse QxR, even though in the old way 2R might be more valuable than Q.
I hope this solves the problems with crashing in Conquer. (After refreshing your browser cache.) If not, let me know.
I now made a slight modification in the Diagram's AI (of betzaNew.js): the condition under which a move is always searched is changed from total gain > value of capturer (which in conquer could go on for ever, with a crash as result) to one where this only holds for moves that do not unload anything, and that moves that do unload something are only searched if they capture a piece of a type higher than their own. (This assumes pieces in the table are sorted by increasing value.) This thus discards the gain from the recruitment; in the old way RxR would gain you two Rooks, and would qualify; now it no longer qualifies, as R=R. It would still always search RxQ, but then two half-moves later not the reverse QxR, even though in the old way 2R might be more valuable than Q.
I hope this solves the problems with crashing in Conquer. (After refreshing your browser cache.) If not, let me know.