Why poker?
Poker is a game of incomplete information and uncertainty. A strong bot must reason about probability, expected value, risk, and opponents whose cards it cannot see—the same kinds of decisions that appear throughout quantitative work.
AlgoPoker is a computerized poker tournament. Competitor teams program completely autonomous poker bots that play against one another in Six-Max no-limit Texas Hold’em tournaments.
Building a competitive bot brings together mathematics, computer science, economics, and game theory. Your program must make decisions with incomplete information, manage risk, adapt to changing stack sizes, and respond to five independent opponents.
Use the local scrimmage app to run large batches against built-in or custom strategies, inspect the latest hand, and iterate without waiting for cloud infrastructure. Upload finished versions when you are ready to submit. Mini tournaments will be run periodically and will post ELO ratings for each team's poker bot.
Poker is a game of incomplete information and uncertainty. A strong bot must reason about probability, expected value, risk, and opponents whose cards it cannot see—the same kinds of decisions that appear throughout quantitative work.
Yes. Competitors build fully autonomous bots in Python, C++, or Rust. Each bot reads the current game state and returns a legal fold, check, call, or raise.
A basic rule-based bot is enough to begin. More advanced entries can use probability models, simulation, opponent tracking, search, or machine learning. The testing tools are designed to make iteration approachable at every level.
Bots compete in six-player no-limit Texas Hold’em tournaments. Every bot begins with an equal stack, blinds rise as hands are played, and the last bot with chips wins.
Clone the open-source engine and run the local scrimmage app. It accepts Python, C++, and Rust bots, runs large batches on your machine, and shows the latest hand without spending AWS credits.
Yes. After signing in with a Georgia Tech email, every team submission is retained in the competition page’s version history.