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 update will:

      Fix GE inventory item positioning bug


      Fix broken object hooks
        • Like
      • 23 replies
    • This release will:

      Fix some ClosedChannelException bug


      Fix bug in RSObject#getAllTiles


      Add game tab support for "Kourend Favour"
        • Like
      • 15 replies
    • This release will:

      Fix Settings UI placement bug


      Fix game object location bug


      Fix small layout bug making the client shift up and down


      Fix client crashing bug where loading the client with a small display area will cause the client to crash


      Fix annoying Linux bug relating to painting events and peers


      Fix settings saving bug where settings are saved to disk more often than they should


      Fix RSInterface#isBeingDrawn bug affecting a limited amount of people


      Drop Java 1.7 bytecode version for 1.8


      Important: Since the downloadable RS client uses Java 7, it will no longer be compatible with Looking Glass. To make up for this, we will add support for using other clients such as RuneLite (at a later date).


      This change was necessary to allow us to use Java 8 syntax. It also paves the way for Java 9/10/11 support.
        • Like
      • 40 replies
    • This update will:

      Fix the RSMenuNode bug which also fixes the bug with bank opening


      Fix the incorrect object positions bug


      Fix and re-enable the LG Objects API Accelerator


      Fix the RSObject#getAllTiles bug
        • Like
      • 22 replies
    • Try our development release by checking "Development Release" on the TRiBot Loader. Note that these new features are currently in beta.

      This release features:

      Re-sizable mode support for both LG and the regular client


      Slightly improved login bot


      Removed final access modifiers from API classes


      Added RSServer hook wrapper to get the client's cached list of server/world info


      [NEW] Bug fix for intelligent banking


      [NEW] Improvement to the stability of LG over time


      [NEW] Vastly improved the reliability and speed of Screen#getColorAt on both LG and the regular client


      [NEW] Fix LG login problems


      [NEW] Fixed re-sizable mode container bug


      [NEW] Fixed re-sizable mode mouse bug


      [NEW] Use of public constants in the Banking API


      [NEW] Use of other various constants such as Projection#NULL_PT and Screen#EMPTY_COLOR



      More features to come very soon!

      Please test it and let us know here if there are any new bugs introduced in this release.
        • Thanks
        • Like
      • 12 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×