Hey, been trying the whole day solving this issue ive read probably every single thread on the issue and still cant get it to work....
Here is log:
[02:08:01] TRiBot Release 9.312_5 loaded. (1.8.0_172:C:\Program Files (x86)\Java\jdk1.8.0_172\jre)
[02:08:01] Loading human mouse movement data.
[02:08:02] Successfully loaded human mouse data.
[02:08:03] AGENT PATH: C:\Users\hmyhr\AppData\Local\Temp\t1_agent_1093120500.jar
[02:08:03] java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
[02:08:03] at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:307)
[02:08:03] at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:202)
[02:08:03] at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:129)
[02:08:03] at java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:227)
[02:08:03] at java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:179)
[02:08:03] at com.sun.proxy.$Proxy0.newClient(Unknown Source)
[02:08:03] at javax.management.remote.rmi.RMIConnector.getConnection(RMIConnector.java:2430)
[02:08:03] at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:308)
[02:08:03] at obf.GO.iV(ffa:504)
[02:08:03] at obf.MJ.run(re:18)
[02:08:03] at java.lang.Thread.run(Thread.java:748)
[02:08:03] Caused by: java.io.EOFException
[02:08:03] at java.io.DataInputStream.readByte(DataInputStream.java:267)
[02:08:03] at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:246)
[02:08:03] ... 10 more
[02:08:03] No RuneScape client was found.
I've tried alot of different versions of JDK 102, 112 etc etc both 64bit and 32bit using osbuddy at same bit ofc. Disabled firewall aswell and antivirus, ran jarfix, made new account on pc legit tried everything i read pls someone help
EDIT: Resolved by Fluffeee thanks alot! If anyone has same issue just follow his link below worked
I formatted my PC yesterday and before i did all was good, but now after format, my tribot Looking glass keeps telling me "No runescape client found".
i have literally tried over 10 different java versions, 32bit and 64bit and nothing works
I have Windows 10 Home
Currently: Java JDK 161 (64bit), I have tried the 32bit version too, didn't work.
Yesterday everything was working, i have read trough all posts about this issue and i did everything they suggested, from fixing my java.policy to removing tribot foler, removing hooks.dat, Removing my temp folder, redownloaded tribot and osbuddy, trying the Java JDK 102 version.
One note, first time i started tribot+osbuddy today after format, it somehow hooked to the client and i could bot, but after i restarted my pc it stopped working :/
I would really appreciate some help, either from the community or someone who has knowledge about this issue!
Also i get these kind of errors when i try to hook to the client.
[00:38:00] TRiBot Release 9.308_1 loaded. (1.8.0_102:C:\Program Files\Java\jdk1.8.0_102\jre) [00:38:01] Loading human mouse movement data. [00:38:02] Successfully loaded human mouse data. [00:38:04] java.io.IOException: Access denied [00:38:04] at sun.tools.attach.WindowsVirtualMachine.openProcess(Native Method) [00:38:04] at sun.tools.attach.WindowsVirtualMachine.(WindowsVirtualMachine.java:56) [00:38:04] at sun.tools.attach.WindowsAttachProvider.attachVirtualMachine(WindowsAttachProvider.java:69) [00:38:04] at com.sun.tools.attach.spi.AttachProvider.attachVirtualMachine(AttachProvider.java:194) [00:38:04] at obf.Tn.ex(zo:381) [00:38:04] at obf.Tn.rV(zo:603) [00:38:04] at obf.kl.run(fk:13) [00:38:04] at java.lang.Thread.run(Thread.java:745) [00:38:04] AGENT PATH: C:\Users\maged\AppData\Local\Temp\t1_agent_1093080100.jar [00:38:04] No RuneScape client was found.
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
have anyone else also noticed that after a break when bot was supposed to re-log in, it does nothing..
Before I started using Looking Glass function, I've never had that kind of a issue. But now I cannot bot over my first break as it just simply stucks at it. Any ideas?
By we trippy mane
Looking glass really helps prevent bans. They updated it though so it took me 3 hours to set it up this time while way back it took 10 min max. The issue was 32 vs 64 bit version's of everything. my guide if you want to start looking glass. Link looking glass with osbuddy. Get's complicated. did you download the 32 bit version of osbuddy? Also the 32 bit 102 jdk? and Are you opening tribot with jdk? also make sure you have 32bit version of java. Took few hours for me to figure this out. I had to delete literally everything and redownload everything the right way to make it work. Also fluffee's advice helped me. His thread is
This release includes:
Fix updater bug which was causing a bunch of issues
TRiBot will no longer require manual hook fixes every time the RS client updates - the updater has been fully patched for objects
Hooked login fields
Improved the login bot
Ability to recognize the banned/locked messages again
Ability to read the current input for username and password fields
If the username or password is already entered correctly, it won't be erased
If only part of the username or password is already entered correctly, it won't be erased. The login bot will fill in what's missing.
If there are a few invalid characters after a valid substring of your username/password, only (approximately) those invalid characters will be erased. The login bot will then proceed to fill in the missing characters.
Skull icon fix
Improve screen rate and responsiveness of the RS client (both regular client and LG)
This release includes:
Fix shift clicking option selecting
Fix high paint delay settings saving
Update prayer IDs for the quick select menu
Remove RS3 support
RS3 Support Removed
The RS3 client hasn't been updated since our Old-School version of TRiBot was released, as many of you may have noticed. Keeping all of the RS3 code in the client made the client as a whole harder to maintain, larger, slower, and messier. As hardly anyone still uses the RS3 client, and since the RS3 API was hardly functioning, we made the decision to completely remove it from TRiBot.
For the average user, this means that the client will be smaller, cleaner, and faster. Future updates will also take less work meaning there will be more frequent updates.
If you were one of the few users still using the RS3 client, we apologize for the inconvenience. No future support for RS3 is planned. There are many other botting clients which has support for RS3, so we recommend finding an alternative if you wish to continue botting on RS3.
Please welcome our new developers, @JoeDezzy1, @erickho123, @Encoded, and @wastedbro.
These members will be responsible for working on, maintaining, and improving TRiBot.
This means that bug fixes and improvements will now come at a much faster pace! We're committed to providing users with the best botting experience possible!
This release includes:
More 3rd party libraries for script writers to use
Apache Commons Codec
Apache Commons Collections
Apache Commons Configuration
Apache Commons IO
Apache Commons Lang
Apache Commons Math
Hint arrow API
Fix player hooks including Player#getSkullIcon and Prayer#getPrayerIcon
This update includes:
Fix broken hooks
Fix login bot for the message "No reply from login server. Please wait 1 minute and try again."
Fix bug relating to which bot tab is sent human input
General#randomLong bug fix involving negative numbers
Fix GE API
Please note: There are still some issues with the login bot due to a change in the game mechanisms handling the login screen. We're working on a fix and will upload it when ready.
Recently Browsing 0 members
No registered users viewing this page.