3/3 US Banned: Hand Levelled, VM+VP* each, Randomized Delays, Champion Farming, <12hr

[zippysticks]

I'm assuming blizzard can see the public champion farming profiles and made a server side script if its own with something like detect if within MoveTo with pathPrecision="10", since all the public profiles has a static moveto pointer and a variable pathPrecision, they might make a script if you are hitting all of those moveto points within a certain radius repeatably in a specific order. It doesn't matter if your bot chases mobs and makes it look random, you will still eventually hit those moveto points and then move onto the next one cause that's what DB is told to do.

Edit: Guess that's where Random Dungeons come in, wonder if they can implement ExploreArea for specific lands only (like Festering Woods map or Fields of Misery map, and etc.), that way, you can just make a profile to hit any waypoint, and ExploreArea until fully explored, then move onto next waypoint of your choice. This will completely solve any static moveto.

 

[scarecrow]

Concerning the timing watch theory :

it's not that easy to implement. cause any code that will try to compute time taken between 2 actions is consuming time itself. So warden or server-sided watchdog would get a result that would vary a little for each computation. the only they can get is a range.

that's why it seems to me that a launch-game-time between 2 and (let's say ) 9 second (8 + 1 extra second) sounds like a signature of DB now. it's not a proof, but it surely raise a part of what we could suppose to be a complex flag raising algorithm

on the one hand this is an important thing, cause they probably have timestamps for game creation and game leaving in theirs databases, so it's an easy info to watch for if you're searching for botters. on the other hand, there is no way to avoiding it ( changing range time to launch game will only lead to another typical - so detectable -time range, and adding long pause lead to values they can easily ignore )

 

[Mammon]

I think that the town run is probably the most vurnable timerepeated spot, the champion farming in itself is by code more various due to all the different spawn locations etc.

All they need to do is check how fast a "townrun" takes and if it's selling the items in the same pace fashion every time and voila.... boom!

 

[hi1674]

There's also a posibility that the bot actually IS detected combined with certain plugins.

Like notificationclick and you actually does not have a mousekey input except for a virtual click.

 

[mephuser1000]

There's also a posibility that the bot actually IS detected combined with certain plugins.

Like notificationclick and you actually does not have a mousekey input except for a virtual click.

I didn't use notificationClickOK (worthless, buggy plugin) and I never touched ZK and I still got banned.

 

[jeff_skilling]

I highly doubt it is because of lack of randomization.

If it is that, why aren't Immortal users immune? My immortals have been hit just the same and everyone knows how randomly it hits core.


This is all luck of the draw, folks. I've had AGB sarks that are still running since day one, and AGB sarks that have been banned twice already.