Any software like that's gotta kind of know what it's looking for. I wrote my own software, so all my protections are in there. And yeah, it's booby-trapped up the wazoo as far as obvious stuff. It looks for things people might
try to do, like, I've got multiplayer blackjack with 3 seats per player, and you can grab a stack of chips at one seat and move them to another stack and merge them. The client doesn't let you grab someone else's stack of chips, obviously, but if someone wrote their own client that let them do it on their end, that's one of a couple dozen triggers that'd kick them out and freeze their account instantly. Other triggers are silent and just record oddities. Like, if the stack they tried to grab didn't belong to anyone, but it just didn't exist. The software would give them the benefit of the doubt that maybe they're on a really slow connection, where they were still seeing an old bet that belonged to them, but it still keeps track of that stuff.
But then there's just the "how the heck did
that happen" kind of situations. Like the guy who cleared multiple bonuses, playing 70,000+ hands of blackjack over a few weeks, at 10¢ a hand, with a 98.8%
RTP. After watching for a long time, I figured out he was sometimes, rarely, not playing basic strategy. Was it a bot playing bonus strategy? He never split, and he never sat at more than one seat. The first few days he never doubled down, and then he started doubling correctly, every single time. But he swore up and down he wasn't using a bot. And if the bot impersonated the client perfectly, then I'd have no way to know for sure. The only evidence of anything was that sometimes he'd get disconnected and after a few minutes the system would eat his bet. That's not supposed to happen if he's the only guy at a table. He should have gotten his bets back. The only way it could happen is if the main login part of the system thought he was still connected, but the game table thought he wasn't. That's possible evidence that he was running two clients -- the real one, and a fake one on the side that stripped the table data out of the real one, scrambled the bets, and put them back in the stream. The fake got confused and crashed or went silent on the table, but the real one stayed connected. Again, that's not hard enough evidence to convict the guy, so I just paid him out.
Bookmarks