- Created Friday, June 20th 2014 @ 03:05:15
So, on this game on turn 11, a strange thing is happening: I get priority to make an action, the engine says that I call when, in fact, I'm trying to raise the amount of the big blind pre-flop. I'm debugging on my end, and I show that I'm, in fact, trying to raise, but the engine keeps returning saying that I can't and it switches the action to a call.
I'm at a loss for why, any ideas?
- Created Friday, June 20th 2014 @ 09:11:31
Thanks for pointing this out. It does seem like a bug, I'll read through the official rules once more to confirm.
- Updated Friday, June 20th 2014 @ 16:37:41
Here's another bug, although I think it's just a visual error:
Check my hand in Round 3 of this game. Looks like I'm holding an ace of clubs, but the engine says it's a jack of hearts.
Opponent is also holding the ace of clubs
Also a similar bug on round 7.
- Created Friday, June 20th 2014 @ 16:59:35
You were right, small typing error on my end. Should be fixed now
- Created Friday, June 20th 2014 @ 20:30:00
there is a similar error in this game:
In the round 3 there are 2 aces of clubs.
- Created Friday, June 20th 2014 @ 22:44:37
this time fixed for realz
- Created Friday, June 20th 2014 @ 23:09:03
I just saw one in my hand, one in the hand of my opponent and two on the table. It must be ace-of-clubs-day ;-)
- Updated Friday, July 11th 2014 @ 22:04:17
I think there's a pre-flop bug. Check this game, round 7.
I'm holding rockets and opponent makes first move. He calls, priority goes back to me to raise or check. Naturally, I raise. However, the engine says that the action isn't reopened and changes my raise to a call. Normally in poker, each player is able to have 1 action prior to the flop, but whoever is on the big blind is not getting that opportunity unless the small blind raises.
Is this a bug, or something specific to Omaha?
- Created Monday, July 14th 2014 @ 11:49:24
That's weird. Will look into both problems. The one you posted on June 20th is fixed by the way.
Thanks for all your help Troga.
- Created Tuesday, July 15th 2014 @ 14:24:56
The first bug should be fixed. Let me know if you ever come across this again, but I couldn't reproduce this anymore.
For the second bug: it is not a bug, this is correct. You cannot check pre-flop if you are the small blind, because you should either call, raise or fold. So the engine correctly changes this to a fold. The weird this is that both bots make the same mistake.
- Created Tuesday, July 15th 2014 @ 17:09:28
Thanks for looking into that Jim!
I took a further look into the second issue and I think that between turn 45 and 46 something happened where the engine stopped receiving input from either bot. When I ran through the turns, for example, turn 46, my bot sent "call 40" back on the first move, but the engine changed it to "check 0". I'm assuming this happened to my opponent's bot as well.
- Created Monday, July 21st 2014 @ 05:04:42
That second bug happened again. I checked the output and my bot was trying to raise and call -- it wasn't sending "Check 0". Looks like it happened Round 38 this time.
I know my bot is making a ton of calculations, but the evaluation methods I use are extremely fast, and it's not timing out anywhere, but against TAU and long games, suddenly there's no output. You could probably sandbox our two bots in a bunch of matches together to see what's going on.
- Created Monday, July 21st 2014 @ 09:32:44
Ah yes, I see now. That is because I set the time limit of a match to 2 minutes max. Apparently one of the bots -and from what you're saying probably TAU- is taking too long and then all actions are changed to 'check' until the game is over. Sadly at the moment it is not possible for me yet to only punish the bot that is causing the long game.