I think I left a lot of info in this post, and honestly I am feeling like releasing a lot more, may be a baby bot for beginners. It is really usefull, for instance, when I have a bot in a flop/turn heads-up I could go all-in knowing the pot odds is going to make the villain bot to fold! May be I have also marked your bot, who knows. I also have ways to find out who are bots and who aren't. It is too much, I have to cut it every month into a new one with a postgrep script keeping just the last 5000 hands per player. My main database is so slow (Billions of hands). ![]() Have you found a better way? Eyy, may be we could share databases. But I needed to close and re-enter PT3 every 30 hands. I have about 10000 observed hands per day per level. Is there any command line input/output calculatem pro?ĭatamine was really easy too. Why did you use only VPIP? Don't you care about PR or AF factor in the AI module? You know all this info is available for query in PT3 database.Īnother question: Did you try to use a calculatem pro interface to get a "easy already made" AI? Did it work? I couldn't do it because of the delay between windows and the multitable factor. I want to make a tournament version that considers more factors like Harrington M, etc. I really think that tables have to be carefully chosen. I also have a list of whales to look for when choosing a table. I did something additional: I have a table statistics, that way I could know when to leave a table and enter another one. I would know two more hole cards of the deck, which gives me a huge advantage. In the future I want to put multiple instances of my bots talking with each other, that way I could calculate more accurate the outs. I did this part reading the pixels, but I don't like what I did, I really think there is a better way. Pot odds is the only function that needs to access the pokerstars GUI, but I guess if I use the chat window I don't need to recognize the numbers. And It really is easy and faster to program. But, isn't it more slow? How could you manage resizing? and multitable (well this I can imagine)? and diferent skins? With History files You don't need to worry about those last factors. ![]() I understand your way is more accurate because of players getting out and in. Why do you use pattern recognition for your position and the button? You could go to the history file to get that data. But getting the input data was really hard. The SQL part to access PT3 database was pretty easy. I am adding a random factor to be more unpredictable 20% of the times. My bot is young and my AI is pretty different from yours, mine doesn't use any points scale, It tries to imitate human processing, using groups of hole cards (Sklansky for instance) and other factors.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |