Jump to content
Sign in to follow this  
shaiguy

Mule Repeatedly Banned--Any Help?

Recommended Posts

Hi, so for the past two months my mules have been constantly getting chained banned.

I suicide bot 15 accounts on a single proxy because I don't care if those 15 get chain-banned, and log into the mule on my home's ip.

All of the mules were hand trained by me, usually up to 70/70/1 in melee stats, and each and every one of them were banned for macro (major) on a monday (which is usually when my bots get banned) even though I never bot on them. It's never even for RWT.

When I transfer directly to the mule via trading, it ends up banned.

When I duel the bots to transfer, it ends up banned.

I've been losing quite a bit recently so I have a few questions.

- Would drop trading work (though it does sound unconventional to me)?

- Would using a VPN prevent my Mule from getting banned?

-Is it because I don't have enough proxies?

Any help would be greatly appreciated.

Share this post


Link to post
Share on other sites
1 minute ago, TerrifiedVirus said:

Put your mule on a proxy and maybe get a second mule

 

By that do you mean I should log on a proxy through the Tribot client? I avoided doing so because I thought it would put me at risk of being banned even more. But if you insist, then thank you for the suggestion, I'll definitely try it.

Share this post


Link to post
Share on other sites
13 minutes ago, shaiguy said:

By that do you mean I should log on a proxy through the Tribot client? I avoided doing so because I thought it would put me at risk of being banned even more. But if you insist, then thank you for the suggestion, I'll definitely try it.

Know that anything I say isn't guaranteed to work, first rule of botting - what works for one person won't necessarily work for another.

That said, private (NOT those free proxies you find online) proxies which you both create an account on (which you can do in Maxthon browser) and then run Tribot in should separate it from your home network, as your home network may be flagged. I can assure you if you choose the right trustworthy proxy you're not at risk of being banned even more. I believe they're $3.5 at socks5proxies.net

Share this post


Link to post
Share on other sites

Personally, my mules get banned very rarely and my mule trades a lot of accounts per day. I have my mule on a proxy, and it is the only account on the proxy and I only ever login on it either to re-supply accounts or mule profits at the end of the day. I never keep gold on my mule either, I keep supplies sometimes, the supplies end up being 30-60m worth of gp but not cash. I transfer off the gp to my main account which I play legit (but barely these days, just login for taking gp from mule). My mule is only 30-50 combat with a few quests and various skills leveled.

  • Like 1

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 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.
      • 39 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
      • 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.
      • 12 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


      Bug fix for intelligent banking


      Improvement to the stability of LG over time



      More features to come very soon!

      Please test it and let us know here if there are any new bugs introduced in this release.
      • 10 replies
    • - Updated the banking API to use the game item cache instead of interfaces. This will result in less delay, greater efficiency, and greater reliability. LG will especially benefit from this update.
      - Fixed a bug with the Grand Exchange API relating to searching for items.
      • 5 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×