|
|
#21
07-13-2005, 11:14 AM
|
|||
|
|||
Re: Screen Scraping Is The Only Way To Go
[ QUOTE ]
Pixel color pattern matching... Is the only professional way to go. [/ QUOTE ] Agreed. Not all sites write HH line by line (for example, UB does not, you can only get history after the hand). If Party does it line by line now, they can easily change it at any time. Intercepting data stream after it's decrypted by the client is interesting but most likely much harder to do than pixel matching, and every site does it differently, so it's starting from scratch if you want to do more than one. Pixel matching is the only way to go, and not really hard. 
|
|
#22
07-13-2005, 11:15 AM
|
|||
|
|||
|
Re: Determining Cards Programmatically
I've seen the files, certainly...I never denied that. I took a look at them long before I'd ever even seen PokerTracker. I'm merely curious how they're built in real time. Your not-so-subtle accusations are standing on pretty feeble legs if you actually read this entire thread.
Just because I have an interest in how something works, doesn't mean that I have any designs on actually attempting to construct it. Such is the bane of a computer programmer/logician. Everything becomes a "How would I do that?" proposition. I can assure you, I have no desire/intention of creating a PokerBot. Purely an extended exercise in the hypothetical.
|
|
#23
07-13-2005, 12:33 PM
|
|||
|
|||
|
Re: Screen Scraping Is The Only Way To Go
[ QUOTE ]
I haven't analyzed the Party window with Spy++...has anyone else? I'm curious if you can read the button text directly through the Windows API [/ QUOTE ] Yes I have... But I've been using Winspector... Which is considered by many to be better than Spy++ [/ QUOTE ] You Can Get Winspector Here You can read all the Party Client controls... Like SysListView32, etc... but not directly. You have to tap into the Client's Virtual Ram... And you're also bombing custom controls with external messages. This is probably detectable... not to mention complicated. Screen scrapping is a lot of initial boring pixel level work... But it can be robust... and it's the way to go. [ QUOTE ] The buttons were moved to the top... [/ QUOTE ] You don't care where the buttons are... You are scanning for their location continously. If the Bot gets confused... It just shuts down... and buzzes the operator... Who then takes over. Same thing with the "Bot Detector" ID boxes. Bot sees it... buzz... Man takes over. [ QUOTE ] All I'm saying is that, from a commercial software programmer's point of view, I certainly wouldn't feel comfortable leaving my house while a bot that's based on pixel mapping is playing hands on my bankroll. [/ QUOTE ] I'm a professional trader... And Automated Trading Systems are ubiquitous and legal. People make ** million dollar trades ** using ATS... And you're worried about Party $33s. Also.. The "run a Bot all nite and wake up to profits" line... Is an oversimplification designed to discredit automation. In reality... One would build Bots... That would relieve you of routine play... And leave the most complex 20% to you. You would run it like a trading operation... Where an ATS is manned by a professional trader. Say you play 50 33s/day... But you only have to play 20% of the time... And have real-time equity and ICM info on hand... That's 6 hours... like a normal workday. Seems doable. [ QUOTE ] assuming you were taking on the ridiculous NL bot task [/ QUOTE ] Well... The Poker Academy NL AveryBot was done by Brian Williams. He's an outsider... But it was good enough that U of A included it. Here's Brian's Web Site I'll bet Brian's best Bots... Can beat the 11s, 22s, and 33s. I've even figured out a way... To "reverse engineer" the AveryBot and plug it into Party... ** Without infringing on anyone's copyright. ** It's just that it's 100s of hours of work... And I have a full time trading business. This is my new hobby. Best of luck to everyone... rm+ [img]/images/graemlins/cool.gif[/img] [img]/images/graemlins/cool.gif[/img] [img]/images/graemlins/cool.gif[/img]
|
|
#24
07-17-2005, 10:47 AM
|
|||
|
|||
|
Re: Determining Cards Programmatically
I advise giving up on your quest to write a bot for Party which I have done and wasted 4 months of my time.
Actually, I got my bot up and running thinking I could sit back and rake in the dough. What happened? Party somehow detected my software usage and closed my account. This sucks!!! Just don't want you to go through the same odeal.
|
|
#25
07-17-2005, 02:38 PM
|
|||
|
|||
|
LYD Meltdown
Some guy making statements like...
"intercepting/decoding the data stream is a realistic possibility"... And comparing sophisticated asynchronous pixel level screen scraping... To poor programming style using GOTOs... ** Has no idea what he is talking about **. And you're speculating rather badly about building a Poker Bot... Then claiming some kind of esoteric intellectual curiousity. You're credibility is shot on all fronts. rm+ [img]/images/graemlins/cool.gif[/img] [img]/images/graemlins/cool.gif[/img] [img]/images/graemlins/cool.gif[/img]
|
|
#26
07-17-2005, 07:45 PM
|
|||
|
|||
|
Re: LYD Meltdown
Couldnt you use a program to detect what image files are being accessed by the party client? When you get your hole cards, two image files have to be loaded into the client, 3 for flop, turn, 1 river. That was the first thing that came to mind, not sure if such a program exists though to make that possible.
|
|
#27
07-17-2005, 09:40 PM
|
|||
|
|||
|
Re: LYD Meltdown
[ QUOTE ]
Couldnt you use a program to detect what image files are being accessed by the party client? When you get your hole cards, two image files have to be loaded into the client, 3 for flop, turn, 1 river. That was the first thing that came to mind, not sure if such a program exists though to make that possible. [/ QUOTE ] Not that I support the idea of creating a bot (I don't), but this seems like the best idea so far. Probably some arcane API call.
|
|
#29
07-18-2005, 03:57 AM
|
|||
|
|||
|
Re: Determining Cards Programmatically
[ QUOTE ]
hand histories are written in real time, they are appended line by line and can be accessed as they are written. In other words, I can read the hand history that is currently being written, as it is written, line by line, without having to wait for the file to be completed. All that is there though is the hand history the same as you would see in poker tracker etc... nothing more One Street at a Time wdbaker Denver, Co [/ QUOTE ] Why are you guys still working on this, its all ready been done as explained above, that's how they do it. Realtime as the file is written, as soon as I see my cards on the table I also see them as written to the file... Don't need to screen scrape at least for Party skins One Street at a Time wdbaker Denver, Co
|
|
#30
07-18-2005, 01:50 PM
|
|||
|
|||
|
Re: Determining Cards Programmatically
[ QUOTE ]
That's why it was an impression, not a statement of fact. Frankly, I think a system wide filehook that determines when the images were accessed would even be more accurate in the long run, and even that's a bad idea. [/ QUOTE ] It's not just a bad idea, it's a terrible idea due to the fact there *will* be collisions with multiple windows. Assuming realtime hand histories aren't available the best is to "scrape" window data and do a very easy pattern recognition against known card images, that way you know what came from where.
|
 |
|
|
Linear Mode
