Jump to content
Sign in to follow this  
mullensk

Avoiding Bans (feat . It's just business?)

Recommended Posts

Firstly, let me introduce myself without wasting too much of your time.

I'm from the US, my preferred botting is Woodcutting, I have four computers capable of running 28-30 bots simultaneously, depending on how many browser tabs I have open, YT, etc..

I'm sure there's been some of the more trial-and-error minded individuals who learn the hard way, and those who simply understand the mechanics of it who have come to find their own way of properly creating and running accounts.. accounts that would be viewed as 'suicide accounts' to one individual that would actually be long-term bots by another because they simply don't get banned that often because they're able to avoid chain bans.

All of what was previously stated has been tested within some margin of error.

What are your opinions on sharing crucial information for the bot community? I'm sure Jagex has their own people who regularly check and see what's the latest and greatest in the botting world. 

Is is bad for business to share all the ins and outs of one's own hypotheses? Would it be better off left unsaid so Jagex doesn't tweak their BotWatch to detect certain things now that they know we know? 
 

I'm interested in engaging in conversation via Message, Skype, TS, Discord, whatever on sharing information of what you've found and what I've found. 

~I've searched pretty far and wide to figure out if this info is already posted both on this forum and others and it appears some of the things that I'd like to share are not only difficult to find, but seems they simply don't exist. 

When I see people asking why they got chain-banned asking if their IP is flagged for botting, it's almost frustrating not just because I was in that position, but also because I know how to solve that. hmm...

Anyway, I'd like to start an active discussion on basic botting i.e. best way to prevent cross-contamination of mules, bots, and mains throughout your systems and ISPs i.e. phone tethering, etc.. 

 

Not going to bother discussing the basics of VPNs, creating accounts on TOR, ABC2, or x-fering, but more along the lines of how to stay safe and how to transfer the gp successfully even from an account that's flagged for bot farming.

Oh shit, that took long to post lol.

 

(edited for color fix lol)

Edited by mullensk

Share this post


Link to post
Share on other sites
1 hour ago, mullensk said:

Firstly, let me introduce myself without wasting too much of your time.

I'm from the US, my preferred botting is Woodcutting, I have four computers capable of running 28-30 bots simultaneously, depending on how many browser tabs I have open, YT, etc..

I'm sure there's been some of the more trial-and-error minded individuals who learn the hard way, and those who simply understand the mechanics of it who have come to find their own way of properly creating and running accounts.. accounts that would be viewed as 'suicide accounts' to one individual that would actually be long-term bots by another because they simply don't get banned that often because they're able to avoid chain bans.

All of what was previously stated has been tested within some margin of error.

What are your opinions on sharing crucial information for the bot community? I'm sure Jagex has their own people who regularly check and see what's the latest and greatest in the botting world. 

Is is bad for business to share all the ins and outs of one's own hypotheses? Would it be better off left unsaid so Jagex doesn't tweak their BotWatch to detect certain things now that they know we know? 
 

I'm interested in engaging in conversation via Message, Skype, TS, Discord, whatever on sharing information of what you've found and what I've found. 

~I've searched pretty far and wide to figure out if this info is already posted both on this forum and others and it appears some of the things that I'd like to share are not only difficult to find, but seems they simply don't exist. 

When I see people asking why they got chain-banned asking if their IP is flagged for botting, it's almost frustrating not just because I was in that position, but also because I know how to solve that. hmm...

Anyway, I'd like to start an active discussion on basic botting i.e. best way to prevent cross-contamination of mules, bots, and mains throughout your systems and ISPs i.e. phone tethering, etc.. 

 

Not going to bother discussing the basics of VPNs, creating accounts on TOR, ABC2, or x-fering, but more along the lines of how to stay safe and how to transfer the gp successfully even from an account that's flagged for bot farming.

Oh shit, that took long to post lol.

Step one -  please color your post one color so I can read it

Share this post


Link to post
Share on other sites

u just cant share these kind of stuff.

i see 3 scenarios:

1. u hurt urself, making ur own method overused and therefore useless.

2. u hurt the rs community, overflooding the game with items/gold.

3. u hurt the botting community, allowing jagex to find solutions to stop the bots.

 

the only things that can be shared are basic knowledge (such as proxies, flagged IP, dont bot 24/7 etc.) and theories, not actual working methods.

if every1 is a successful botter, then no1 is.

Share this post


Link to post
Share on other sites

figured as much. I'm more trying to tackle this from a mutually beneficial tactic.

there's no point in sharing key points of ban avoidance because it's self destructive, Jagex sees it, other botters reduce your own value.. etc. 

I'm going to go based on PMs and other direct messaging so I can share/receive information of equal value so we can both benefit. 

Starting to see more and more how it's imperative to develop one's own scripts to even succeed at anything feasible.

Share this post


Link to post
Share on other sites

well it's always nice to get a reply/pm so that I feel less like a useless dickhead taking up forum space.

Thanks guys. Cheers to each of our individual future endeavors and best of luck to you all. 

I hope to continue to seek to better myself to the point of self-learning programming and script writing. 

I want to out do my friend whose in a University for scripting ;) want to demonstrate the power of self-learned

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  

  • Similar Content

    • By zanfax
      I've recently been banned on 7 accounts due to me running 10 on the same IP address and i need to know if it is possible to use socks 5 proxies on 10 accounts or more spread out on different IP's on the same computer?
    • By Shibalicious
      Hello,

      I have been doing some research recently and speculating on the ways Jagex trace devices and networks that players play on.

      Firstly, we know that your global IP address can be seen easily outside your local network.

      Secondly, your MAC address. I understand that it's not visible outside your router. I have seen a lot of people say that Jagex aren't able to see your MAC address but I am certain there are software and scripts that allow them to collect your devices information, including HWID and MAC address. I know this because, here, in the U.K gambling websites install a tracing tool whenever you make a new account that collects vasts amounts of data, anything there is to know about your device (device information, specifications, operating system version and even browsing history) and stores it on remote servers. This is to prevent people creating multiple accounts and abusing their promotional offers. The tool is called "iesnare" or "mpsnare" and it is completely legal for them to collect your information as it's stated in their terms and conditions. Now back to Jagex, as the Runescape client is a downloadable software, it is completely possible for them to collect various information about your device. In fact, their Privacy Policy states it clearly that they DO collect your device information as stated in this post here: https://tribot.org/forums/topic/67175-can-runescape-see-my-system-information/

      Now to my main questions:

      1. I read many threads on this forum and people suggest using proxies for multiple account botting. So if I wanted to bot on 25 different accounts and had set 25 different proxies for every single one of them, that would result in me botting on 25 different clients with unique IP addresses. Nevertheless, people who do this don't get chain-banned frequently and I have no idea why as Jagex can clearly see that you are running those clients from the same device.

      2. Lastly, if I were to setup 5 virtual machines and run 5 clients through 5 proxies on each VM, would that be seen by Jagex as 5 different devices running 5 clients each through proxies (so each client would have a different IP but they would still be able to see every 5 clients originating from the same device)?

      Any input and suggestions are really appreciated!

      Shibalicious
       
    • By Dollarbill
      Here are two hong kong ip addresses 
      e.g. 
      xxx.1x0.157.55 
      and 
      xxx.1x0.157.12
      So the two ip addresses are the same except for the two ending digits one is 55 and the other 12.
      So if my RS acc got banned on 55 and i start using the 12, will my rs acc on the 12 get banned? Will jagex be able to do a chain ban, like are they able to relate the first ip to the second ip im using?
    • By crazygerrit
      I have been banned before on my home IP address and currently I am still botting a few accounts on this same IP address. If all my accounts reach a certain goal I would invest in making them all member since they are f2p right now and I would like to use premium proxies. The only thing that bothers me right now is.
      Do premium proxies work if I botted on a flagged IP before? or will Jagex just look at previous IPs I guess that no1 really knows the answer but does anyone ever experienced something similar like this before?
    • By paragon51
      Hello! I'm new to the runescape. I just started to play the oldschool version and I need free or premium scripts that actually allow just be in the game to have maximum time played. I think they should have some rest option or something to logout automatically and then login. I tried to use free woodcutter and fishing scripts, but my accounts always get banned. It would be very nice of you if u advise me some scripts. Thanks in advance!
    • By mullensk
      I previously asked a question as to what I'm doing wrong. 
      My bots went from extremely successful one minute to banned right after tutorial island. Is Jagex Cache really ONLY where they store files? 
      AFAIK the cache is located under the user in your SSD/HDD named as 3 files: jagexcache, random.dat (for multilogging accounts), as well as one more file. 
      What else could be the issue? I've realistically ran enough bots to be flagged for a mass-gold farm, but am now facing resetting EVERYTHING just to get off their hit-list.
      Are there any programmers here that actually know how to 'reset' your system without actually reinstalling everything?
      (Yes, I have ran VMs, yes, I've reset my IP every day, and as far as I know VPNs don't matter in the slightest unless you don't have control over your IP (like on a public network). 
      It's definitely not fun logging in and finding out you've just lost 400+mill in a single ban sweep, but I'm trying to use this as a learning experience. 
       
      I wish to not sound redundant or repeat myself, but people keep recommending virtual machines or VPNs, the only thing that's thus far worked for me is a hard reset of everything. 
      There has to be a more efficient way. 
      I understand business is business and everyone wants their cut of the market and it might not even be financially beneficial for them to provide legitimate assistance in this matter, but as a paying member and fan of the TriBot community, this issue is beyond me at this moment and I need a savior. Thank you all.
      Yes, I've read many guides on how to safely bot. They don't say what to do after Jagex has you flagged. 

    • By mullensk
      edited comment.
       
      thanks for all your answers
  • 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
      • 23 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.

×