You didn't say what level the cube is at. If it's at 8, that's qualitatively different than if it's at 1, 2 or 4. But assuming it's at 1, 2 or 4, that's a bug IMO.
It seems like what Gnu's doing is:
1. Roll
2. Calculate equities for possible moves
3. Resign if appropriate, wait for response
4. Display dice
5. Move
When it should display the dice right after rolling. Although actually this wouldn't explain everything -- if Gnu needs some time to calculate the equities, it does in fact display the dice before it pauses to think. Maybe it's doing a quick 0-ply eval before deciding to resign and then displaying the dice and doing a full analysis if it chooses not to resign? I don't know, you'd have to ask a Gnu developer.
Quote:
Originally Posted by noncarborundum
But, of course, it makes one wonder in certain circumstances, other types of pre-roll decisions , like offers, takes, and drops, could also be dependent upon the AI's "knowledge" of the upcoming roll.
That's a wildly different situation. The resign thing could easily be a bug where it's just displaying the dice at a weird time. There's no reasonable way this taking and dropping thing could be a bug. It would be malicious coding in an open source code base. And the maliciousness would be easy enough to detect and prove by any user as Gnu would make different cube actions in the same position depending on what roll was coming.
Last edited by _Z_; 12-18-2015 at 02:31 PM.