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?
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.
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!
Here are two hong kong ip addresses
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?
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?
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)
Deleting random.dat + jagex_cl_oldschool_LIVE.dat files after your account was banned is a good way to lessen the chance of other bans when using the same machine (PC/VPS/whatever) + multiple accounts.
In Windows, you can find them here: C:\Users\[Your computer account name]
Also, I'd like to ask more experienced botters if deleting the whole 'jagexcache' folder found in that same folder is of any help or pointless.
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.
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.
Recently Browsing 0 members
No registered users viewing this page.