So I recently let my brother use my tribot account, I had to hand hold him through everything.
he bots for what he says is like 5 hours based on levels closer I would say more like 10 hours over 2 days. Banned.
I've botted for a fair bit on self made scripts. recently using the same one he was using a (premium), I suicide botted a fresh account 12 hours day one nothing.
Many people have been receiving emails from <[email protected]> claiming that your Tribot account has been locked for security reasons.
Most likely someone using a database leak from a different site.
If you don't use the same password at multiple sites and/or have 2 factor authentication enabled, you have nothing to worry about.
Email is legitimate, means that TRiBot security has blocked the unauthorized attempts, no need to worry or change your password.
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.
Hi i havent used tribot in a while, thankfully i have somehow not logged out in like forever but i cannot remembermy password. i attempted to use"forgot password on the bots opening but no luck keeps saying unavailable, can anyone help me out? am i doing something wrong
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).
[READ TO THE END FOR A TEASER]
I've noticed some new TRiBotters have had some troubles finding out sources of how to do certain things, such as using advanced scripts and often get lost in the forums.
We are still getting posts asking where to start, what to do, recommended scripts, etc.
As many of you know, I am new to the team, and had troubles myself learning how to bot, let alone script.
So, what our team decided to do was make it easier to learn how to bot, how to script, and just become an overall better botter and scripter faster.
As some of you might have seen, I've posted 3 new blogs, you can check it out by clicking on the following picture or here.
These first 3 blogs are the first of many blogs that will be TRiBot official. They are encouraged to be challenged, improved upon and act as A Best Practices Guide for Botters.
What information would you like to see in the blogs?
👇 [TEASER] 👇
We are going to be hosting a CONTEST this OCTOBER.
Its scary to think how soon you'll find out.👻
Today marks a big day for TRiBot! To make it easier for users to use TRiBot, we've created installers available for every platform! These installers are all bundled with the latest version of OpenJDK 1.8 (Java 😎, which is LG compatible.
Using TRiBot is now easy. Simply download the installer for your platform, install TRiBot, and run it. The TRiBot Loader will correctly identify the bundled JDK so there's no need to change the Java selection.
EXE installer: TRiBot-windows-x64-4.0.3.exe
MSI installer: TRiBot-windows-x64-4.0.3.msi
Portable version: TRiBot-windows-x64-4.0.3.zip
Portable version: TRiBot-macos-4.0.3.tgz
RPM installer (CentOS/Fedora): TRiBot-linux-4.0.3.rpm
DEB installer (Debian): TRiBot-linux-4.0.3.deb
Portable version: TRiBot-unix-4.0.3.tar.gz
JAR file: tribot-loader-4.0.3.jar
Note that this jar file does not include the bundled JDK.
Windows and Mac OS users may notice a warning message stating that the installer/application is un-recognized or un-trusted. Please ignore this message and proceed with running the installer/application. We need to acquire a code signing certificate so that we can sign the installers letting the operating system know that these files can be trusted. It will take a week or more to acquire one, so please hold tight.
Other notable changes to the TRiBot Loader:
Support getting the version from OpenJDK distributions
Add check for bundled JDK
Copy OpenJDK tools.jar to the bundled JDK if not present
Set the current java as the first available list entry
Ignore Java versions which are symbolic links
Make the bundled JDK the preferred Java version
Update icon images
Reduce the number of HTTP calls
TRiBot is looking to improve a lot of its customer relationship management, customer on boarding process, customer experience, design elements, community engagement and pretty much everything else you can imagine when it comes to marketing.
Our goal: To ensure that the marketing done TRULY reflects the experience and does not shine an inaccurate light on what TRiBot is lacking in.
So I ask, what do you love about TRiBot and what do you hate about TRiBot? What does O S Bot, Rune M8, PowR Bot and Dre amBot do better? (yes I purposely didn't spell it right 😂).
Today we have a significant release that has been in the works for the last month addressing several key issues, features and bugs in the backlog.
With these changes, we are also including a new TRiBot Loader which will allow you to select any version that is released. This adds the flexibility of allowing you to revert to a previous version should an issue arise, run development only builds, view an accurate change log between versions etc. we are very proud to offer this feature and think it will add a lot more functionality down the road as we continue to release new versions.
These changes include 80+ commits by our development team, a list of them is summarized below and also available for your viewing pleasure in the new TRiBot Loader.
In addition, we have taken additional steps to improve as a development team by adding continuous integration and deployment into our workflow to assist in delivering timely releases such as bug fixes as well as new features on a weekly basis depending on our development cycle.
Over the last three weeks, I've been working on upgrading our server infrastructure. It's finally ready and is now live!
Increased reliability - less server errors
Increased availability - less downtime
Increased security - keeping us and you secure
Increased capacity - ability to serve you better
Increased speed - less waiting for things to load
Faster development - server and service updates will come faster
What are the changes?
Move from a single AWS EC2 instance to AWS ECS (Elastic Container Service)
Git management of server files and filesystem
AWS ECS (with 10 EC2 instances)
AWS ElastiCache (Redis)
AWS Load Balancing
AWS EFS (Elastic file system)
Please bare with us as I continue to tune the server for maximum performance. Slow loading speeds may occur temporarily. I thank everyone for their patience.
Please post on this thread if you experience any issues other than slow loading times.
Recently Browsing 0 members
No registered users viewing this page.