Official Thread to Identify Ban Patterns

[Spaceguy911 2]

The idea here is that once you are banned, share your "lastrun.log" found in ExiledBotFolder/Log/

 

My theory is that admins sit in town and watch you.  I feel the easy (well I don't know if it's easy because I'm not a coder) fix would be to somehow go to hideout immediately after you tp to town after a run.  Some things to include if you'd like to participate in this science:

 

When you were banned (can tell from your log):

 

How long was your current botting session before you were banned (can tell from your log):

 

What was the last thing your bot was doing as you got banned (you guessed it, log):

 

Have you received bans on that IP before?:

 

Any other information you may think is pertinent:

 

 

Please post the pertinent end information from your lastrun.log in code

like this

[Spaceguy911 2]

So I'll start:

When you were banned (can tell from your log):

                       11:56 PM EST Saturday -- Would be roughly 4:56 PM Sunday NZ time.

 

How long was your current botting session before you were banned (can tell from your log):

                       I was botting for about 40 minutes and ran about 13 runs.

 

What was the last thing your bot was doing as you got banned (you guessed it, log):

                       Bot came up from town after run completion, identified items, moved to a position, disconnect.

 

Have you received bans on that IP before?:

                       This was a first

 

Any other information you may think is pertinent:

                       N/A

2014-09-27 23:56:18 [info] -> Idling...
2014-09-27 23:56:18 [info] -> Exploring to position(4586.106934, 8512.236328, -347.845001). State Priority: 2
2014-09-27 23:56:18 [info] -> Exploring to position(4580.979004, 8508.017578, -347.777283). State Priority: 2
2014-09-27 23:56:18 [info] -> Exploring to position(4511.925293, 8478.188477, -347.765076). State Priority: 2
2014-09-27 23:56:18 [info] -> Exploring to position(4487.485840, 8455.181641, -347.763733). State Priority: 2
2014-09-27 23:56:18 [info] -> Exploring to position(4421.392578, 8425.315430, -347.763489). State Priority: 2
2014-09-27 23:56:19 [info] -> Exploring to position(4399.528320, 8383.254883, -347.763489). State Priority: 2
2014-09-27 23:56:19 [info] -> Exploring to position(4397.866211, 8359.344727, -347.763489). State Priority: 2
2014-09-27 23:56:19 [info] -> Exploring to position(4392.569824, 8324.228516, -347.763489). State Priority: 2
2014-09-27 23:56:19 [info] -> Exploring to position(4390.621582, 8307.065430, -347.763489). State Priority: 2
2014-09-27 23:56:19 [info] -> Exploring to position(4395.583984, 8292.807617, -347.763489). State Priority: 2
2014-09-27 23:56:19 [info] -> Exploring to position(4359.197754, 8265.926758, -347.763489). State Priority: 2
2014-09-27 23:56:19 [info] -> Exploring to position(4311.055176, 8238.178711, -347.763489). State Priority: 2
2014-09-27 23:56:19 [info] -> Exploring to position(4267.186035, 8216.809570, -347.763489). State Priority: 2
2014-09-27 23:56:19 [info] -> Exploring to position(4144.772949, 8164.989746, -347.763489). State Priority: 2
2014-09-27 23:56:19 [info] -> Exploring to position(4097.444336, 8134.399902, -347.763489). State Priority: 2
2014-09-27 23:56:20 [info] -> Exploring to position(4091.464844, 8104.231445, -347.763489). State Priority: 2
2014-09-27 23:56:20 [info] -> Exploring to position(4084.993652, 8058.119141, -347.763489). State Priority: 2
2014-09-27 23:56:20 [info] -> Exploring to position(4091.906738, 8040.682617, -347.763489). State Priority: 2
2014-09-27 23:56:20 [info] -> Exploring to position(4091.242676, 8020.372070, -347.763489). State Priority: 2
2014-09-27 23:56:20 [info] -> Exploring to position(4093.772461, 7985.292969, -347.763489). State Priority: 2
2014-09-27 23:56:20 [info] -> Exploring to position(4078.718750, 7969.783203, -347.763489). State Priority: 2
2014-09-27 23:56:20 [info] -> Exploring to position(4084.730713, 7941.499023, -347.763489). State Priority: 2
2014-09-27 23:56:20 [info] -> Exploring to position(4084.814209, 7868.273438, -347.763489). State Priority: 2
2014-09-27 23:56:20 [info] -> Exploring to position(4091.879883, 7824.679199, -347.763489). State Priority: 2
2014-09-27 23:56:20 [info] -> Exploring to position(4094.035156, 7779.374023, -347.763489). State Priority: 2
2014-09-27 23:56:21 [info] -> Idling...
2014-09-27 23:56:21 [info] -> Map explored !!
2014-09-27 23:56:21 [info] -> Restart state because area is cleared
2014-09-27 23:56:21 [info] -> Creating tp...
2014-09-27 23:56:22 [info] -> Map explored !!
2014-09-27 23:56:22 [info] -> Distance computed for tp use: 0.000000
2014-09-27 23:56:22 [info] -> Restart state because area is cleared
2014-09-27 23:56:22 [info] -> Moving to position(4125.000000, 7798.913086). State Priority: 15
2014-09-27 23:56:23 [info] -> Distance computed for tp use: 0.000000
2014-09-27 23:56:23 [info] -> Restart state because area is cleared
2014-09-27 23:56:23 [info] -> Moving to position(4125.000000, 7798.913086). State Priority: 15
2014-09-27 23:56:23 [info] -> Using currency on item...
2014-09-27 23:56:26 [info] -> Using currency on item...
2014-09-27 23:56:29 [info] -> Using currency on item...
2014-09-27 23:56:31 [info] -> Using currency on item...
2014-09-27 23:56:32 [info] -> Moving to position(2113.319824, 2234.283203). State Priority: 7
2014-09-27 23:56:32 [info] -> Moving to position(2112.355957, 2307.645264). State Priority: 7
2014-09-27 23:56:32 [info] -> Moving to position(2104.555664, 2395.049805). State Priority: 7
2014-09-27 23:56:33 [info] -> Moving to position(2106.336914, 2506.626221). State Priority: 7
2014-09-27 23:56:33 [info] -> Moving to position(2088.758301, 2629.505127). State Priority: 7
2014-09-27 23:56:33 [info] -> Moving to position(2091.087402, 2766.445801). State Priority: 7
2014-09-27 23:56:34 [info] -> Moving to position(2028.314209, 2913.570801). State Priority: 7
2014-09-27 23:56:34 [info] -> Moving to position(2047.355713, 3043.113770). State Priority: 7
2014-09-27 23:56:34 [info] -> Moving to position(1827.229736, 3178.808350). State Priority: 7
2014-09-27 23:56:35 [info] -> Moving to position(1588.615479, 3295.378174). State Priority: 7
2014-09-27 23:56:35 [info] -> Moving to position(1568.138794, 3383.322266). State Priority: 7
2014-09-27 23:56:35 [info] -> Moving to position(1570.614258, 3440.114014). State Priority: 7
2014-09-27 23:56:35 [info] -> Moving to position(1566.942749, 3532.242188). State Priority: 7
2014-09-27 23:56:36 [info] -> Moving to position(1592.401489, 3673.810547). State Priority: 7
2014-09-27 23:56:42 [info] -> Logging into the game
2014-09-27 23:56:44 [info] -> Logging into the game
2014-09-27 23:56:45 [info] -> Logging into the game
...

Edited September 28, 2014 by Spaceguy911

[RaZe 148]

The science behind this is really unknown meanwhile most of us that has been banned has been guessing on why;

 

Botting 24/7 for days/weeks/months, not human possible. http://poestatistics.com/ Check ur bot versus legit characters on poestatitics and see how unrealistic and easy bot's actually are to spot for GGG.

 

And the second one beeing spotted in town / reported by legit players.

 

They seem to be quickest at banning new accounts with new characters, it's like they dont want people to go from lvl 1 - 70 in less then 24 hours on a fresh account.

 

I agree that botting from hideouts is a good idea, but also bot should take some random breaks to get the action's per minute count down a bit. If no hideout atleast some random movement in town would be nice. Still believe it all comes down to actions per minute + the weird xp/hour online time they can see on poestatitics.

 

Oh and there's already alot of ban reports and theorycrafting  here and other forums, you will never get the answer you're searching for unless you get employed by GGG and tell us how they do it.

But yeah everyone has an idea on how & why we get banned.

 

I've been banned in town, invited to group and bot somehow accepted it so obviously got reported aswell, i've danced with hargan and botted 24/7 and lost 5 bots so far. Oh an admin also messaged me and I replied, took like 2 days until I got banned after that aswell.

 

It's safe to say that most botters will get banned a couple of times, but then again you will find ways urself to be more safe. Like having several accounts that you switch between + be active in trade channel & join some public groups and do maps with them is stuff that helps for sure 100%.

Edited September 29, 2014 by Ash

[Spaceguy911 2]

Really well said Ash.

 

I agree that random town movements would be key.  Also, yes I feel that APM (Actions Per Minute) is a huge tell.  Character is making 200 bot runs over 8 hours, each run is around 6 minutes (just random numbers), that would be a tell...  Humans aren't reaaally doing that.  Humans take breaks, humans do some trading in between.  Even the most disciplined grinders won't be in the docks or catas that long.  Maps is a slightly different story...

 

Yes -- Mixing in some legit playing seems a great strategy.

[heisenburger 7]

As long as GGG finds out you're running multiple characters from the same hardware or location, you'll most likely get banned.

 

Make sure you understand what it takes to give every one of your characters a unique identify before you work on randomizing movements. If GGG really does watch for random movements, most of us would have been banned long ago.

Edited September 29, 2014 by heisenburger