Poker-AI.org

As mentioned, I have planned on using screen scraping with Bring to get state from the poker client. But I made that choice because the alternatives I could find to screen scraping all seemed so difficult to implement, adapt to new sites and to maintain. But I don't know, maybe screen scraping is outdated and I should really use some other method. What is state of the art today?


When you say detecting is easy, do you mean by using a windows hook or with screen scraping? As I said previously, I haven't started researching this yet, so any info I can get here will be helpful.

Hi,

I wouldn't plan on running on stars if I was you.

If you spend a few years a developing state of the art setup - then maybe - but even then there is a good chance they will bust you.

There are much easier places.

-PeppaPig

@Seikez

I don't think a solid detection avoidance with regard to screen scraping is doable. If a site wants to detect a screen scraper, they've got a ton of easy way to do that (with manipulating pixels, colors etc.) that you just can't prepare for in advance. So the answer is to either avoid screen scraping altogether (and for example go with writing your own client altogether - way better approach imo since then you don't have to deal with the often buggy and crashy casino software at all) or to stick to sites which don't proactively search for botters.

Oh wow, how about that for a radically different approach from screen scraping! Great idea, might be the ideal solution. But that must mean the encrypted communication protocol between poker client and poker site has to be analyzed and recreated in my bot. You would have to be a real superhacker to do something like that. How do you do it? Please!

That is something I will definitely have a look at for bot ver2.0, sometime in the distant future. In the mean time, I think I will just follow the advice and avoid PS and other difficult sites.

They should be using some kind of network protocol, which should be reversable (should be fairly easy if the client is in Java/.NET, since then you can reverse the binary and just see what's going on). On top of that, they'll probably be using SSL, which, as it (the DLL) is on your machine, should be circumventable.

That sounds like a short quip for a long/hard process. How do you circumvent SSL?

One idea would be - if they're using a standard third-party DLL for SSL, the lib should be well-documented. You could then create a stub DLL which has the same public interface and which logs all traffic passed to it (before it's encrypted) and then sends it to the original DLL so that it gets encrypted.

Interesting. Wouldn't the change in DLL throw flag with casino, having a different hash tag?

for sure!

Running bots on PS/FTP is not much of an issue. All of the methods posted above are certainly doable but not the best way imo. The solution is not hard. I did it with limited skills and its been fool proof for the last year and a half. I used the same methods back in the day when Party Poker was king and bot detection first started becoming a problem. I will discuss the methods but not in the public forum. Just think outside of the box as the answer is pretty simple.

So, how do I get access to this forum?

During testing/development, yeah - but that's not important (can be done through VPN from a throaway account). Once you've developed your own client, you're controlling which warning are sent home though