Hello guys. I've tried every possible setup with java jdk 1.8.0_202 and java jdk 1.8.0_252. Osbuddy, openosrs, every guide found on forum so far, and yet i my looking glass can't seem to find osbuddy or openosrs or any client for that matter. I've deleted hooks, followed natan script that deletes cache/hooks/everything, but so far i'm stuck not being able to load it, also tried updating java policy for full permissions. . Can someone suggest something that i might be overlooking?
(I've tried this with windows 7 32 bit, windows 10 64bit(reinstalled both 2x)), same problem. I have it running with no problems with the same steps i did on a computer just next to me. I do not understand at this point what am I doing wrong? Can someone please guide me?
I was playing around with a VM as it is easier to manage multiple instances for me personally on my local machine (I do not use proxies, but use a vpn). But I can't get LG to work... On my local machine everything runs smooth, but on the VM it always says "looking for OSRS client" (you know the message). I have the same configuration as on my local machine.
Is there a configuration property to be set on VM level or something?
All suggestions are welcome!
--------Specs of the VM:
- Clean install with VMware Workstation 15 Player running Windows 7 Ultimate (also tested with Windows 10 with VirtualBox)
- Java JDK 8u251
- Tribot loader 4.0.4
as the title suggests, it works, but my issue is that for me it only works with OSbuddy.
this is what i have installed for java
however when i try and open the runelite (or open osrs) jar file i get this error
so, i inquired about what i should do to get RL or OPRS working, i installed JDK 11 (also 13 after to check if there was any diff, but none).
this lead to RL working, but then my Tribot loader AND my OSB wouldnt load.
my tribot loader didnt even give an error, it just didnt open, and my OSB gave this error
can someone please help me out, i just want to use tribot looking glass witrh runelite instead of OSB
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
This update includes:
Fix OSBuddy LG input bug Fix updater exception Added error loading profile message to login-bot (Thanks @Todd) Prevent auto-relog from being typed in the client (Thanks @Todd) Comment out a pause in the clicking method (Thanks @Todd) Fix Prayer API (Thanks @Todd) To compensate VIP-E users for the downtime, all current VIP-E users (as of the time of extension) will be given an extension of 2 weeks. The extension will be applied sometime between 24 to 48 hours from now.
A fix for RuneLite support is still in the works.
whenever i load the bot client, (just spent ages with jar fix and reinstalling all java to my pc several times as client stoppped working for me. The looking glass window just loads a blank black screen? any help would be greatly appreciated, first time back on rs and botting for a long time.
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.