Quote:
Originally Posted by StopTheBot
I believe the solution may be fairly simple. Bots rely on being able to read images/pixels on a poker table. If you make the colours of/on cards and player
action indicators dynamic (changes in pixels between hands barely noticeable to a human) then the bot will no longer be able to read information from the table.
This relatively small software change could potentially completely eliminate the problem.
I am quite sure current bots don't use screen capturing to follow the game, and even if they would - it is almost trivial to write ocr/pattern detection that adapts to such visual changes.
I would rather reverse engineer the PS Client and write a modified version for professional botting. This way you have full input output control, you can easily circumvent their countermeasures (e.g. mouse movement detection) captcha popping up,debugging detection...
Having a glance at mac os x PS client - i am kind of disappointed, i would have at least expected some basic anti debugging mechanism and obfuscation.
Well, at least they haven't spelled all their function names like party poker does:
PGBots,investigationId,AlertBotDetectionFail,mBotA lertType,getOpenUrls..... seriously...
All that being said, you can make botting (much) harder, but at the and you can always and easily circumvent all of the countermeasures with use of screen capturing and virtual input device....
The only thing left is detection through statistical or behavioral abnormalities - but not only is this very error prone (and you would wan't to avoid false positives at all cost) - and bot rings will also adapt...eg i am sure the next network will not be running their bots 8 hour shifts 5 days a week... and try to not have too similar stats....maybe just play with each other to falsify stats...