Being totally into Aurora's MSX2 games these days [], I decided I'd have a go at Ruby & Jade. But here's the thing, seeing the screen shot below, the game does not finish! And that whilst having beaten Jade! I tell you what went wrong. The stones at the top of the screen were positioned last - by both MSX and me [jade and ruby, respectively].
MSX's turn, whilst having two jade stones left: no action (!) while it should have positioned one of them.
My turn, whilst having the same stones left [only ruby]: I used the left one as both would end up yielding the same score.
MSX's turn, it placed the right one.
- STALEMATE -

Theoretically, we would both be left with a stone that could not be placed anymore. I accuse the AI of cheating, it skipped a turn whilst it should have selected a stone. Other than that, the stalemate situation was not implemented, I blame a lazy coder [*hii* Aurora ]
Is this a bug that can still be fixed?
What the hell is going on?

BTW, checking the stalemate condition is dead easy. It actually boils down to checking whether a player, being it the human or the CPU one, is able to put a stone into the game.

bit playerUnableToMove() {
    bit unableToMove = TRUE;
    int stone = 0;
    while (unableToMove && stone < 30) {
        if (stone.positionY + 1 == VACANT)
            unableToMove = FALSE;
        stone++;
    }

    return unableToMove;
}

Pseudo crap, of course.

Hm, as far as my - rather leaky - memory recalls, we did test and provide for this situation. As for the question whether I can still solve this bug: erh... that might be a bit difficult. I'd need to find the sources, try to understand them, then figure out how the heck I operated MCBC2 and what is needed to create a new version. I will look into it, but it won't be this weekend.

Other than that: that's a pretty piss poor score you've got there, mate!