Sort:  

Thanks for pointing that out... probably a node issue... but I'll check it out when I get to a PC again this evening.

Hi @robhimself1,

Good News/Bad News time.... the good news is that I found the problem, and will have a fix for it in a few hours.

Without boring you with too many technical details: In certain scenarios (that in the 3-odd months games has never happened), an error is triggered which prevented parts of the code from executing (you might notice that all the currently "OPEN" games don't have any bid-bot votes on them), and one of the parts not executed is recording the game in a database (for closing later on).
This means that the "close and roll dice" part of the bot doesn't know about the game, and the next game in the queue for closing was 2 or 3 games on which was only 5 or 6 hours old.

Long story short: I' believe I have a workaround which I will take live in the next couple of hours.

The Bad News:
Unfortunately I can't manually trigger those games to close (yet). I MIGHT craft a solution for this in the coming days, but if I can't get it done before the post itself actually closes on Steemit, then I will manually award some extra bot votes to a day's worth of games next week to make up for rewards generated by the missed games.

Aw, glad you got it figured out now though!