Just got a new Windows 10 Home x64 Laptop. Going through my usual install method and finding that I cant get looking glass to work. I have followed a few "old" guides, because I cant find any that are more recent. I am installing Java SE Development Kit 8u251, I am choosing the x86 version since the only OSbuddy cross platform .jar file is 32bit. Its worked fine in the past. I then open Osbuddy, and then Open Tribot. I leave it on the default Tribot Version of 10.24.1. I select the java version for Tribot to use to be the JDK and not the jre. I changed the Heap Size to 1024 MB and login. I minimize Osbuddy, then I click New Client(Looking Glass). The Screen goes to black and says " Waiting for a Runescape client.... currently waiting for a valid client. List of detected java applications below." and there is nothing Below. I also tried a backup method that used to work as well, which was to instead click New Client (Osbuddy) and then manually select the Osbuddy .jar file which would open up Osbuddy and Create a Looking Glass Tab that mirrored Osbuddy. This no longer happens either. Ive also deleted the Hooks and Caches using Naton's Java Executable. I have also defined the correct Paths in my Computers Environment Variables.
Im at a loss for what to do. Any help greatly appreciated
tribot not working with looking glass what could be reason thanks? it says Looking for Runescape client and it was working before?
[10:06:38] TRiBot Release 10.14_1 loaded. (1.8.0_201:/usr/lib/jvm/java-8-oracle/jre)
[10:06:38] Loading human mouse movement data.
[10:06:39] Successfully loaded human mouse data.
[10:06:40] RuneLite users take notice: you must have the GPU plugin disabled. Otherwise, the client will crash.
[10:08:51] java.net.ConnectException: Connection timed out (Connection timed out)
[10:08:51] at java.net.PlainSocketImpl.socketConnect(Native Method)
[10:08:51] at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
[10:08:51] at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
[10:08:51] at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
[10:08:51] at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
[10:08:51] at java.net.Socket.connect(Socket.java:589)
[10:08:51] at java.net.Socket.connect(Socket.java:538)
[10:08:51] at java.net.Socket.<init>(Socket.java:434)
[10:08:51] at java.net.Socket.<init>(Socket.java:211)
[10:08:51] at obf.xA.qC(bb:37)
[10:08:51] at obf.xA.bb(bb:188)
[10:08:51] at obf.Yg.KM(el:324)
[10:08:51] at java.lang.Thread.run(Thread.java:748)
[10:11:02] java.net.ConnectException: Connection timed out (Connection timed out)
[10:11:02] at java.net.PlainSocketImpl.socketConnect(Native Method)
[10:11:02] at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
[10:11:02] at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
[10:11:02] at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
[10:11:02] at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
[10:11:02] at java.net.Socket.connect(Socket.java:589)
[10:11:02] at java.net.Socket.connect(Socket.java:538)
[10:11:02] at java.net.Socket.<init>(Socket.java:434)
[10:11:02] at java.net.Socket.<init>(Socket.java:211)
[10:11:02] at obf.xA.qC(bb:118)
[10:11:02] at obf.xA.bb(bb:188)
[10:11:02] at obf.Yg.KM(el:324)
[10:11:02] at java.lang.Thread.run(Thread.java:748)
Used tribot for about a year now, running lg only the entire time. ive always been able to fix errors that would come up but since the update my Lookingglass has been broken. Tried everything I know how to do ie. Uninstall everything and download proper osbuddy,tribot, and java jdk downloads.
running into the same error over and over again, and my debug log at the bottom spams errors non-stop, took a while to even be able to see some words cause it was spamming so fast.
Heres mostly what its saying in the debug, any help would be wonderful. Love everything about tribot, hope someone could help a brother out.
OSBuddy may altar things in the Runescape client and will mess up some actions in game if using Looking Glass.
For example, if you have the Jewelry Overlay enabled, then clicking on some charged items (like a Ring of Dueling) may mess up.
Ensure your OSBuddy settings are on default to guarantee Looking Glass running as smoothly as possible
How to default your OSBuddy Settings
Locate your OSBuddy folder ON WINDOWS: C:/Users/username/OSBuddy If you can't find it, just locate the folder of where you launch the OSBuddy jar, and navigate one or two levels up.
Delete the settings folder
Now when using OSBuddy all of the custom overlay settings should be turned off.
Double check if the Jewelry Overlay is disabled; and if not, disable it manually.
Pretty sure I already know the answer, but I am just trying to be lazy and not write the code myself (since i dont write java, but python)(automation), was wondering if there is a cli starter that someone knows of that uses LG, im aware of the one with tribot, and ericks public one, but i think neither support LG (assuming osbuddy is already running for LG to hook into)
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.