Jump to content
Sign in to follow this  
xFakeid

Chain ban while using proxies.

Recommended Posts

Hello,

 

I've been botting for a few months, and am trying by trial and error to find the most efficient way of collecting gold, while maintaining a low ban rate.
However, after botting for 4 days on my accounts they were banned. Not too surprising, since I am learning by trial and error.

 

However, what did surprise me was that when I looked at the Debug of the bot, I noticed they were banned around the same time.
I am using a private SOCKS5 proxy for each of my accounts, and always spoof my MAC before running a script.

Could anyone maybe explain how my accounts got (chain)banned? Are there other ways besides MAC and IP for Jagex to link accounts to each other? One thing I can imagine is that when creating accounts I use my Gmail-address, and for each account I use my gmail account adding "+ (and then a number)"
Is it possible Jagex looks whether email addresses are related to each other?

Info:
One bot was running a flax spinner, and the other was running my private script, which runs at a totally different location.

Break settings
Runtime: 04:30 hr
Randomness: 00:30 hr
Duration: 01:10 hr
Randomness: 00:15hr

 

Ps. I did not use looking glass, since as how I understand it, you have to run both a Runescape client, and a bot client, thus doubling my CPU/RAM usage. Is this correct?

 

:)

debug.PNG

Share this post


Link to post
Share on other sites

One explanation is that all your accounts were put on a ban list, then this morning all accounts on that list were disabled (Jagex working hours are in Cambridge I believe and today is Thursday, which is OSRS update day). Spinning flax seems like an easily caught method, especially if you're running 24/7.

Share this post


Link to post
Share on other sites
17 minutes ago, xFakeid said:

Hello,

 

I've been botting for a few months, and am trying by trial and error to find the most efficient way of collecting gold, while maintaining a low ban rate.
However, after botting for 4 days on my accounts they were banned. Not too surprising, since I am learning by trial and error.

 

However, what did surprise me was that when I looked at the Debug of the bot, I noticed they were banned around the same time.
I am using a private SOCKS5 proxy for each of my accounts, and always spoof my MAC before running a script.

Could anyone maybe explain how my accounts got (chain)banned? Are there other ways besides MAC and IP for Jagex to link accounts to each other? One thing I can imagine is that when creating accounts I use my Gmail-address, and for each account I use my gmail account adding "+ (and then a number)"
Is it possible Jagex looks whether email addresses are related to each other?

Info:
One bot was running a flax spinner, and the other was running my private script, which runs at a totally different location.

Break settings
Runtime: 04:30 hr
Randomness: 00:30 hr
Duration: 01:10 hr
Randomness: 00:15hr

 

Ps. I did not use looking glass, since as how I understand it, you have to run both a Runescape client, and a bot client, thus doubling my CPU/RAM usage. Is this correct?

 

:)

debug.PNG

Did you create the accounts on the proxys you associated with them? If you created the accounts on one IP they can still chain ban based on that. Also Lg does require both and it requires more then double your CPU, but well worth it imo.

Edited by yojoedude

Share this post


Link to post
Share on other sites

Oops, yea forgot to add some info.

Yes, accounts were created on the Proxy's IP adress. Also the accounts were level 30+ combat, and were wearing equipment, in order to look less suspicious.
I also botted during Jagex working days, but the time between the bans doesn't seem human-like to me. Probably banned by the automatic system.

Edited by xFakeid

Share this post


Link to post
Share on other sites
23 minutes ago, dragon.knight12377 said:

Spinning flax bot on proxy?

It's a total waste of money.

Flax spinners among other over-botted methods are the first line of soldiers. They get killed fast and on a regular basis.

You should use more inventive moneymaking methods if you plan on using proxies, because they cost money, and once you get a account banned on a proxy, it becomes useless, because of the ip flag.

And about the fact that your accounts have been banned simultaneous , don't worry.

This is Jagex common practice.

They are flagged one by one, then mass banned on the same time.

However, I don't know if Jagex does this because of the increased efficiency or it's a psychological weapon, ( you get demoralised when you see them all gone).

I opened today a topic about how Jagex catches bots:

 

Pretty sure ips aren't flagged after 1 ban

 

Share this post


Link to post
Share on other sites
1 hour ago, dragon.knight12377 said:

I respect your oppinion bro!

Still, I am the paranoid type.

If i have a ban on a proxy, i feel like it has been somehow compromised.

And since I get a free ip change for each one, a small change there won't hurt anybody :D

I won't run more then 1 bot per proxy - however I will reuse a proxy if banned up to 3 times. (Unless 30 days is close to up for renewal)

I had 2 bans on a proxy when I was new, decided to try it on one last account and it's still going. (5th bond)

Share this post


Link to post
Share on other sites

Our clients have successful runs with VirtualBuddy's proxy service, if you want to take a look at our wares you are free to here: www.virtualbuddy.org

Non-blacklisted/flagged, and fresh IP ever time to ensure lowest possible chance to get caught.

From what I can see from the comments you may have created the accounts on the same IP, HTTP proxies can be used to create accounts on various IP's, while SOCKS5 will help you be protected while botting.

We offer HTTP & SOCKS5 (one of each for a total of 2 proxies) for only $3.25, currently with 30% off you're looking at around $2.22.

Let me know if you have any questions

 

Best Regards,

Cows.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Our picks

    • This release includes:

      Fix updater bug which was causing a bunch of issues


      TRiBot will no longer require manual hook fixes every time the RS client updates - the updater has been fully patched for objects


      Hooked login fields


      Improved the login bot


      Ability to recognize the banned/locked messages again


      Ability to read the current input for username and password fields


      If the username or password is already entered correctly, it won't be erased


      If only part of the username or password is already entered correctly, it won't be erased. The login bot will fill in what's missing.


      If there are a few invalid characters after a valid substring of your username/password, only (approximately) those invalid characters will be erased. The login bot will then proceed to fill in the missing characters.





      Coming soon:

      Skull icon fix


      Improve screen rate and responsiveness of the RS client (both regular client and LG)


      Much more
        • Thanks
        • Like
      • 15 replies
    • This release includes:

      Fix shift clicking option selecting


      Fix high paint delay settings saving


      Update prayer IDs for the quick select menu


      Remove RS3 support


      Fix hooks



      RS3 Support Removed

      The RS3 client hasn't been updated since our Old-School version of TRiBot was released, as many of you may have noticed. Keeping all of the RS3 code in the client made the client as a whole harder to maintain, larger, slower, and messier. As hardly anyone still uses the RS3 client, and since the RS3 API was hardly functioning, we made the decision to completely remove it from TRiBot.

      For the average user, this means that the client will be smaller, cleaner, and faster. Future updates will also take less work meaning there will be more frequent updates.

      If you were one of the few users still using the RS3 client, we apologize for the inconvenience. No future support for RS3 is planned. There are many other botting clients which has support for RS3, so we recommend finding an alternative if you wish to continue botting on RS3.
        • Thanks
        • Like
      • 25 replies
    • Please welcome our new developers, @JoeDezzy1, @erickho123, @Encoded, and @wastedbro.

      These members will be responsible for working on, maintaining, and improving TRiBot.

      This means that bug fixes and improvements will now come at a much faster pace! We're committed to providing users with the best botting experience possible!
        • Thanks
        • Like
      • 30 replies
    • This release includes:

      More 3rd party libraries for script writers to use


      Apache Commons Codec


      Apache Commons Collections


      Apache Commons Configuration


      Apache Commons IO


      Apache Commons Lang


      Apache Commons Math


      GSON


      Guava


      JFoenix




      Hint arrow API


      Game#getHintArrowX


      Game#getHintArrowY




      Fix player hooks including Player#getSkullIcon and Prayer#getPrayerIcon
        • Thanks
        • Like
      • 49 replies
    • This update includes:

      Fix broken hooks


      Fix login bot for the message "No reply from login server. Please wait 1 minute and try again."


      Fix bug relating to which bot tab is sent human input


      General#randomLong bug fix involving negative numbers


      Fix GE API



      Please note: There are still some issues with the login bot due to a change in the game mechanisms handling the login screen. We're working on a fix and will upload it when ready.
        • Thanks
        • Like
      • 37 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×