An efficient but effective artificial intelligence for Big 2

(tl;dr: You can play against an AI computer user I designed for an online Big 2 game here.  The bots are capable of calulcating the expectation for its score for every possible line of play very quickly, resulting in a rather worthy opponent for even the most seasoned Big 2 players).

The dynamics in Big 2 make programming AI for it an interesting problem.  The usual “game tree” approach when solving games like Chess or Reversi can still somewhat be applied.  However, like programming optimal AI for backgammon, there is an element of the unknown to be included.  We know the cards we hold in our hand, but how might they be distributed amongst the other concealed hands?

There are many other factors that human players have to their advantage.  They can spot and exploit players’ weaknesses and habits, bluff, and come to logical conclusions putting those two weapons together.

Emulating this behaviour and analyzing a fairly large “game tree” makes designing a fast, yet effective AI for Big 2 a challenge.  For AI that is controlled by the server (for obvious reasons it is server-side and not client-side), we have to be careful too to not take up many cycles per AI decision.  The assumption is that multiple computer players will be running at once, so for a multiplayer online gaming site, CPU cycles for AI should be minimal.

So instead of a game tree where we guess what cards will be played (and where they lie) and determine the optimal play by looking ahead, the approach taken is one giant heuristic: let’s calculate the expected value of a play simply from the cards we see and the cards we did not see up until the play.  Ultimately the goal of Big 2 is to get rid of all your cards, so we simplify the calculation by estimating how many cards will be shedded by playing a certain hand.

The process is simple: when it’s the computers turn, what are all the possible plays we have?  If a single was played, we can play another single, or pass.  If the computer is leading, then anything is possible, but passing.  Whichever the case, we have a small finite set of moves.  Now for each move, how will our hand look like after?  What will our possible plays be?  To answer this problem, we treat it as if the computer is leading a hand, and determine the set of all plays regardless if we are approached with a single, double, triple or poker hand.  Now, given the cards that are concealed in everyone else’s hand (and we know the exact set of cards, since the computer easily tracks what cards have already been played, we just don’t know how these cards are distributed — we could guess and assign probabilities, but for purposes of efficiency, we opt not to) let’s calculate how many cards we expect to shed by the end of the game.  If one of our plays in our “future” hand contains a poker hand, how likely is it going to beat all the other possible poker hands out there?  If it beats all the other possible poker hands (or a high percentage of them), how likely are we even going to be seeing a poker hand in play?  That factor is nil if the remaining players have 5 or less cards each.

Anyway, just by answering those questions above you have a relatively good gauge on expected value, and interestingly enough figuring out these probabilities is fast, by applying some good finite mathematics formulae.  One thing that human players do well is to have a game plan to run out their cards, waiting for a deuce to be played to promote one of their deuces, giving them an unbeatable exit plan.  To emulate this on the AI side, we simply do a small probability assignment ourselves: when we know a certain line of play has hands that can be unbeaten (or close to unbeaten), we can boost the probability to 1 (or close to 1) for a weaker hand that had no chance of being played unless the computer leads it itself.

So with the original probabilities calculated and the “fudging” of probabilities to emulate creating a “game plan” with a certain line of play, we have a rather decent AI for Big 2 that can give even the most seasoned players a challenge.  Although the computer still does funny stuff from time to time, it makes up for its shortcomings by doing pinpoint probability calculations quickly, and also has the inhuman ability to figure out exactly what cards are left, to accurately determine the strength of its hand.

So how does it play?  You be the judge!

4 thoughts on “An efficient but effective artificial intelligence for Big 2”
  1. This was a great read!
    I was wondering if i could get more information on your approach, i’m trying to create a sophisticated AI for Big 2 to fit in my app for my university dissertation and also wanted to OPT for a “thinking ahead approach” but wasn’t sure on what probabilities to calculate.

    I have a few questions:
    When you say “If one of our plays in our “future” hand contains a poker hand…”, does “future” refer to the current hand combination you are analyzing E.G a combination where you have pair 3 pair 4 and a poker hand is a possible future hand where pair 3 is a possible play in this hand.

    After the computer chooses the optimal hand how does he just try to beat the previous play? with his current hand and if his current hand does not allow him to do that does he just pass and then when it’s his go again he re-calculates his optimal hand?

    1. Hi Wei,

      By “future” hands, I’m referring to what our hand would look like if we played a certain card (or cards) to beat what’s currently on the table. So, say the player to the right puts down a pair of 3s, and our hand looks like:
      4 4 5 6 7 8 A A
      There are three plays we can make: 4 4, A A, or pass. What do our “future” hands look like after each play?
      Play 4 4: 5 6 7 8 A A
      Play A A: 4 4 5 6 7 8
      Pass: 4 4 5 6 7 8 A A
      My approach is to now calculate the expected number of cards we can shed following each play. Say the computer knows based on previous play that all the twos are gone AND the number of possible poker hands out there that can beat a 4 5 6 7 8 straight is close to zero. Clearly then, playing A A is the strongest play, because it has the highest expected shedding value (everyone will pass the A A, everyone will then pass the 4 5 6 7 8 straight, and the computer goes out with the 4, so this is clearly the play with the optimal expected value). My algorithm tries to simplify this probability calculation alot (for speed purposes), but you can essentially branch a game tree to figure out more exact probabilities (i.e. the likelihood certain cards/hands would be played by other players, in addition to the likelihood they would actually be holding those certain cards/hands), and thus calculate more exactly the expected shedding value of each play.

      I think that also answers part of your second question. For your third question regarding recalulating every go, yes, my algorithm does the expected value computation every time it’s its turn, since we would have new information (more cards played on the table means we can reassign probabilities of who holds what, and what play leads to the best “future” hand and plays that would likely shed the most cards based on the new probability distribution).

      Hope this helps!

  2. Hi Chris,

    I read your post and then played around a bit on hobub and was really impressed by how well your AI played. I’ve been looking into writing an AI for Big 2 based on MC Tree Search, but I’ve gotten stuck on an idea for another AI to evaluate/play against. Would you possibly consider sharing the source code (I hope that that’s not a ridiculous request, apologies if so) for your AI or talking to me about some more details? For instance, I’m confused as to to what depth you apply your probability calculations — when you calculate the expected shedding value of a play, do you somehow iterate that out over the entire horizon of the game? Or is it just for the next hand played?

    If you’d be willing to talk to me about it over email, I’d be really grateful. Thank you!

Leave a Reply

Your email address will not be published. Required fields are marked *