Bought 2 private proxy for 2 accounts which I have owned for over a year. botted rc with auto runecrafter elite earlier today and it both got banned. my other accounts which i have owned for only a couple of months with individual private proxies are still fine even though i botted way more longer hours. question is can i still use both the private proxies or should i get new ones? Many thanks in advance. sorry im still learning how these things work.
There seems to be a problem with botting on a specific computer. My friend and I are botting on two different computers. The account is created on my friend's computer. The bots that were all banned are on my computer. We both share the exact same proxies and accounts, so we don't have any issues logging in the wrong proxies. He makes the accounts and gives me accounts as soon as more bots cannot be put on his computer due to CPU usage / RAM usage. He has so far handed me 9 accounts. Some were accounts he has successfully botted for a month and some that were fresh. All of the bots that were given to me have died within a few days. He has shown me how to handle the bots while scripts are running. He has even tried to do accounts himself on my computer. Same outcome. We have changed the scripts. We have tested on different scripts, Sigma Magic, Auto Agility, CombatAIO, daxMiner, Master Thiever AIO. We have changed the amount of time we have scripted on each account. Ranging from 30 mins per day to 4 hours per day with breaks between certain days as well. The scripts don't seem to be the issue since the same scripts are run on my friend's computer and are doing perfectly fine. One account got banned on my computer despite not running any scripts on it. We have also deleted Jagex's files and cache and still no luck. We're confused and are wondering if it's even possible Jagex can see our processes or compare any hardware. Our mains are played on our respective computers on the same IP and are not banned. The Java versions are also different but are working perfectly fine besides getting banned.
My friends computer details:
Desktop Windows 10 Home AMD Processor Java: jdk1.8.0_151 My computer details:
Laptop: Lenovo Windows 8.1 Pro Intel Processor Java: jdk1.8.0_121 Any help would be appreciated and we will post more details if asked upon.
By we trippy mane
I keep investing 50 bucks into tribot just to be banned within a week. I use virmach proxies, lookong glass, premium scripts, maxthon to create the account via proxy. Always get banned. I feel like quitting and giving up tribot for good. I bought many different scripts too. Just money and time down the drain. So tired of this. I keep coming to tribot because it's the only bot I have experience with. I start bot farm get banned come back month later try something else but nothing works. Mod mod mod weath always targeting me my damn worse enemy
Currently attempting to bot for the first time and using a premium hunter script, striving for that 99 and right now sitting on 84 =-) I feel i am careful when i come to botting my character, i mainly watch my botting screen because i play my other two accounts as normal|<< nerdy i know. so i am able to reply to all who speak to me within moments, along with having break handler set up and every now and again mouse clicking around the screen to change my mouse data patterns around.
I ask this because of course 99 Hunter is great money, id much more envy the fashionscape of the 99 hunter cape and would onward play the character manually and level combat for a edge 13 pray g maul pker, noob life i know but sue me.
Will i get to live out this little account dream set up or is it most likely in the end most botted accounts lose the battle against jagex =p
If anyone has any info inside on the matter would be awesome if you discussed below.
Happy botting <3 hahah
I wasn't doing anything too extreme, just botting strength at the experiments for about five hours a day over the past week. It was mostly spectator botting, in all honesty, and I kept out of everyone's way.
Does this mean I can't ever bot again on this account? Or is there a time period after which it'll be okay to start again?
Fix shift clicking option selecting
Fix high paint delay settings saving
Update prayer IDs for the quick select menu
Remove RS3 support
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.
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!
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
Hint arrow API
Fix player hooks including Player#getSkullIcon and Prayer#getPrayerIcon
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.
This release will:
Fix key event handling issue
Fix other event handling issue
Fix RSServer hook
Update world hopper to have it use OCR, thanks to Todd
Use proper disposal of old Graphics objects
Organize code imports
Apply around 8000 automated code refactorings
Make preparations for Java 9
Fix 11 various bugs
Add more reliable debugging support
Fix mouseEntered/Exited event dispatching bug
Fix minimap walking bug where it opens the map
Fix broken hooks for today's game update
Recently Browsing 0 members
No registered users viewing this page.