Quick one here.
Botted 99 str 88 att 75 def 99 range and 94 mage + all skilling stats for barrows gloves and i got a 2 day ban a few months ago.
I just found out now about Auto clicking rapid heal at nmz and i was wanting to get 95 att and 90 def.
I know slightly randomized auto clicking is not that detectable but i was wondering how detectable it would be with my account being flagged. The fact that its randomized and i wouldnt be suiciding nmz makes me think its not that risky if im doing it for 2 hours considering i nmz legit for 2 hours anyways, just getting annoying clicking twice every minute while trying to watch a movie or something
Let me know what you think boys.
More Runescape Botting Guides at https://RSBotSpot.com
Join our Runescape Botting Discord chat channel here
Original/Updated Article here at RSBotSpot
This guide contains affiliate links
How to Use TRiBot Looking Glass & Bot though the Official Runescape Client
TRiBot’s Looking Glass feature allows you to bot through the official Runescape client by hooking onto and controlling it. Looking glass also supports proxies for botting & other clients like OSBuddy.
While there’s no evidence that TRiBot is detectable, this feature was released as a form of antiban for users worried about the potential detectability of botting clients. Botters seem to be torn 50⁄50 about the effectiveness of Looking Glass on bans, but it never hurts to have some extra protection. This guide will cover how to use TRiBot Looking Glass to bot through the official Runescape client!
1. Install Java Development Kit (JDK)
Download and install JDK here. I will be using 32 bit JDK 8u151.
Java Development Kit Download
At the time of writing, only Java 8 is supported. 2. Load Runescape & TRiBot
Load Runescape up to the login screen, and TRiBot up to the client select screen.
3. Start Looking Glass
On TRiBot, click the “New Client (Looking Glass)” button.
Hooking TRiBot to the Official Runescape Client
4.(Optional) Set a Proxy
If you’re using a proxy for runescape botting, now’s the time to apply it. To do this: right click the client’s tab on TRiBot, and select “Set Proxy”.
TRiBot Looking Glass Set Proxy
That’s it, you’re done!
Your TRiBot client is now hooked onto the official client, and you’re ready to start botting Runescape!
You can find out more about TRiBot’s Looking Glass feature on it’s release thread here You can find out more about using proxies with TRiBot Looking Glass here You can find more working Java/Client version combinations reported here More setup guides: By Einstein
Note: Some threads are only visible to TRiBot VIP users. Our Favorite Runescape Botting Proxy Providers
We've tested and had great results with Runescape botting proxies from:
Blazing Proxy (Use code RSBOTSPOT to save 5% recurring!)(CHEAPEST) Virmach (Use code SAVE20 to save 20% on your first order!) Proxy Fish (Use code OSBOT20 to save 20% on your first order!) Your Private Proxy Our Other Guides:
All About Proxies for Runescape Botting How to Create and Register Runescape Bot Accounts Through a Proxy How to Use Proxies With TRiBot How to Expand your Goldfarm with a Botting VPS How to Unlock your Runescape Bot Account
I believe Jagex relies purely on the amount of the time played, my evidence for this:
1) People report being banned for using a script, yet another person will not, this should be seen as evidence that they cannot detect the script pattern or odd behavior, or the bot client.
(For example, I ran a ranging guild script which others had warned got them banned, I ran it for at least 12 hours total, with breaks, and was never banned)
2) The only time you hear someone say they was banned, is followed by them saying that they botted for a DAY (24 hours), which suggests they ran the script for much longer than 4 hours.
3) Ask yourself, when have you banned within a couple of hours of using a script? Most likely never.
4) Jagex uses J mods to manually ban players, why would they do this if their automatic bot detection system was working?
5) I coded a macro, very basic, using pulover's macro creator (AutoHotKey) which would just fire/repair the cannon, as well as eating food when health got too low, the clicks were always in the same spot and the same time apart, I ran the script for HOURS, at least 4 in total (I was babysitting it), and was never banned.
6) Adding on to what was previously said, I also currently use a macro which switches my amour (Void Range/Ava/God Book/Rune Cbow > Void Melee/Fire Cape/Gmaul) and then it uses the special attack (all within 1 seconds :P), the mouse jumps all over the screen, moving at speeds not humanly possible, I've used it for months and still have not received anything for it, most games would detect this but RuneScape does not, you would've thought their amazing bot detection system would pick that up right?
7) It is already known that breaks reduce your chance of being banned.
Anyone got more to add?
To put this to the test, I'm going to attempt to get 99 strength and 99 ranged, I'm only going to bot for max 6 hours per day, taking breaks every 1 hour 45 minutes, for 30 minutes.
It's either this, or Jagex adds you to a list, and once you've botted too much that's when they ban you (I doubt this, they would more likely give you a 2 day ban).
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
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
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.
Recently Browsing 0 members
No registered users viewing this page.