Hello, I bought VIP-E and decided to bot with the Combat AIO script. I use the “Looking Glass” feature on the tribot with OSBuddy open. On much OSBuddy screen there is no stuttering or delay, on tribot how ever it will freeze for about a second every five seconds. I have set up a frequent break on the break manager and anytime my bot attempts to relogin, it gets hitched and messes up my email and/or password. It is then left to continually reattempt to login infinitely with a jumbled password and email. Is there any way to fix the freezing? Maybe there is a setting somewhere that’s will completely backspace my email and password every failed attempt? How can I fix this please?
so, I installed tribot, installed java, restarted computer, tried deleting and reinstalling, however, whenever I try to open tribot with java it opens for a split second then closes right away, I am on a windows 10 computer, any help would be greatly appreciated.
Having a problem with Dax hunter premium script.
When hunting if the hop settings are set to hop when another player is seen the bot will register itself as a person and get caught in an endless loop of logging in and out hoping worlds.
When hunting black chins the bot will not Bank, once out of traps, the bot will stand there (level 32-33 wildy) and just come to a stop.
Not sure how to fix this problem, I've looked into it with no luck with how to solve. I appreciate all the input.
So i bought Master Chopper AIO, and when i go to start the script, it doesn't load, instead, it gives me this;
I've deactivated and reactivated and that didn't fix anything.
P.S. For people who dont want to click the Gyazo
[01:28:36] Downloading script 'Master Chopper AIO'.
hey guys! I keep having issues with my Tribot Client. Sometimes the script will run smooth for about 15 minutes, other times it will run for about 2 seconds. I do have VIP-E and am using the looking glass feature. I installed:
Windows x86 198.04 MB jdk-8u151-windows-i586.exe as it is what it was recommended from other threads. This issue happens to ALL of my scripts which makes it literally impossible for me to bot. I have tried deleting all the files from tribot_loader and also have tried clearing all my java's and re-installing the JDK-8u151. Its just weird how the scripts run perfectly sometime for 2-5-10 minutes and then die... sometimes they also die straight away the moment i load them. I have absolutely no idea what it could be but im assuming its an issue with the java?
Can anyone help me sort this issue to get my bot running consistently again? Its so inconsistent at the moment and impossible to bit with this issue!
i bought a lifetime in master chopper aio for 20 credits. And when i went to run the script all it did was click on the minimap randomly i tried to do all the settings but they it still dint help i tried draynor and lummby tree spots. when i tried draynor it just when to draynor manor and when i tried to bot normal logs in varrock it dint cut tree's at all please fix this bug! the script is called master chopper aio
I've tried out about every single Flax spinner, but they all have problem with getting to the spinner, or to th bank, they all click on the mini-map in the black space and just get stuck. They don't even fix themselves. Can anyone here make a flax spinner that actually works? I am surprised that a bot forum such as this, that has been around soo long, doesn't even have a decent flax spinner.
Here is the crash log I recieved :
# A fatal error has been detected by the Java Runtime Environment:
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x4dce0a9d, pid=5000, tid=0x00000824
# JRE version: Java(TM) SE Runtime Environment (8.0_131-b11) (build 1.8.0_131-b11)
# Java VM: Java HotSpot(TM) Client VM (25.131-b11 mixed mode windows-x86 )
# Problematic frame:
# C 0x4dce0a9d
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
# If you would like to submit a bug report, please visit:
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
Over the past few months, I’ve been working diligently on a new project - TRiBot X. Everything has been written from the ground up, with all of the best practices of software engineering. Every aspect of TRiBot has been re-imagined to support three main goals: flexibility, useability, and reliability.
Come give us feedback on the next version of TRiBot!
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 😂).
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.
This release will:
Fix prayers and world hopper API (Thanks @JoeDezzy1 and @erickho123)
Improve banking API (Thanks @Encoded)
Adds methods for returning and using Java Lists, rather than arrays
Slightly randomizes some hardcoded behaviour
Removes sleeps from waitConditions; the efficiency saving potential is negligible in these use-cases, therefore cleaner code is preferable
Other back-end improvements
Note: If you are using LG, please restart both the RS client and TRiBot.
Recently Browsing 0 members
No registered users viewing this page.