What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

1/1 Another one bite the dust.

A

AutoconTroll

New Member
Joined
Jun 1, 2013
Messages
11
Reaction score
0
Botting almost 2 months straight 12h Library with my Righteous Fire and today got the banhammer.
Maybe its cause the bot tried to log in so many times and failed but I cant really blame the bot.
In the logs appears to be trying to Log in from 5:41Am to 7:21Am end.
By far I made tons of chaos and fuses, 1 Divine drop and not even close to 500Exs.

Thanks Pushedx and the others keeping the bot right there.
 
If you think there's an issue with the login code, please attach a full log from the session that you mentioned spent a long time logging in, as well as tell me your settings for MaxLoginAttempts, DelayBeforeLoginAttempt, and LoginAttemptDelay. By default, the bot should only try logging in 5 times, and then will stop. If your having network issues and trying to login, the bot will wait 30s in addition between login attempts as well.
 
maybe it got banned @5:41 AM...... and you stopped the bot @7:21AM ?

I don't understand the last sentence as well, please clarify...
 
Thanks!

There is a bug, but it's not with the actual login process. There's no way for you to have been banned from this bug, because the logic is coded to not login and simply return an error.

However, the bot did not stop because the return value, MaxLoginAttempts, was not processed, so it just sat there logging the same error message over and over, but it wasn't actually trying to login.

What I guess happened was this:
1. You got banned and DCed.
2. The bot tried to login, but was unable to, because you were banned.
3. The bot just displayed the same error message for hours until you stopped it.
 
pushedx said:
Thanks!

There is a bug, but it's not with the actual login process. There's no way for you to have been banned from this bug, because the logic is coded to not login and simply return an error.

However, the bot did not stop because the return value, MaxLoginAttempts, was not processed, so it just sat there logging the same error message over and over, but it wasn't actually trying to login.

What I guess happened was this:
1. You got banned and DCed.
2. The bot tried to login, but was unable to, because you were banned.
3. The bot just displayed the same error message for hours until you stopped it.
Click to expand...
I can verify this, I've seen it done on a slew of accounts. The accounts gets banned within milliseconds of each other, and the bot sits there at the error message.
 
darkbluefirefly said:
I can verify this, I've seen it done on a slew of accounts. The accounts gets banned within milliseconds of each other, and the bot sits there at the error message.
Click to expand...

Thanks for clarifiying, Im okay with the ban, deserved :cool:
Next leagues will keep doing the same and more safe lol
 
You must log in or register to reply here.
Back
Top