Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
legitpure

Looking Glass Issues

Recommended Posts

  • [13:03:22] TRiBot Release 9.305_0 loaded. (1.8.0_131:C:\Program Files\Java\jdk1.8.0_131\jre)
  • [13:03:22] Loading human mouse movement data.
  • [13:03:23] Successfully loaded human mouse data.
  • [13:04:30] AGENT PATH: C:\Users\Val\AppData\Local\Temp\t1_agent_1093050000.jar
  • [13:04:30] No RuneScape client was found.

 

So basically everything was fine until I restarted my computer and for some reason my bot client can't find the rs client (osbuddy). I downloaded both JDK Java versions x86 and x64

Share this post


Link to post
Share on other sites

At the time of writing, the most reliable JDK to use is JDK 102, instead of the latest (at time of writing) 121. A link to the 102 JDK can be found here

Note: Many people commonly proclaim that you need the 32 Bit JDK for TRiBot to work, this is a misconception. What you do need, is your RuneScape client, and your TRiBot client running the same bit version of Java. So, if your TRiBot client is running with the 32 bit JDK, and your OSBuddy is running the 64 bit version Looking Glass will not hook. You need to have both clients running either the 64 bit java, or the 32 bit java. Therefore, feel free to download either JDK, it really doesn't make a difference.

Step 2. Head over to the Programs and Features screen, and uninstall all other Java versions. Do not leave anything behind, as the JDK will install it's own Java Runtime Environment when the JDK installs.

Step 3. Install the JDK that you downloaded in Step 1

Step 4. Head over to http://www.rsbuddy.com/ and download the OSBuddy.jar, which can be found at this link, or under the Downloads section by clicking Cross Platform

Note: You can use the standard OSBuddy.exe but the .jar is highly recommended as it ensures compatibility.

Step 5. Launch OSBuddy using the .jar, wait for the game to load, and then launch TRiBot

Step 6. Select New Client (Looking Glass) from the TRiBot selection screen, and then hit Always Allow to all the prompts that pop up.

Step 7. TRiBot should now be hooked to OSBuddy and you're free to bot using Looking Glass

  • Like 1
  • Thanks 1

Share this post


Link to post
Share on other sites
5 minutes ago, iFluffee said:

At the time of writing, the most reliable JDK to use is JDK 102, instead of the latest (at time of writing) 121. A direct link to the 102 JDK can be found here

Note: Many people commonly proclaim that you need the 32 Bit JDK for TRiBot to work, this is false. What you do need, is your RuneScape client, and your TRiBot client running the same bit version of Java. So, if your TRiBot client is running with the 32 bit JDK, and your OSBuddy is running the 64 bit version Looking Glass will not hook. You need to have both clients running either the 64 bit java, or the 32 bit java. Therefore, feel free to download either JDK, it really doesn't make a difference.

Step 2. Head over to the Programs and Features screen, and uninstall all other Java versions. Do not leave anything behind, as the JDK will install it's own Java Runtime Environment when the JDK installs.

Step 3. Install the JDK that you downloaded in Step 1

Step 4. Head over to http://www.rsbuddy.com/ and download the OSBuddy.jar, which can be found at this link, or under the Downloads section by clicking Cross Platform

Note: You can use the standard OSBuddy.exe but the .jar is highly recommended as it ensures compatibility.

Step 5. Launch OSBuddy using the .jar, wait for the game to load, and then launch TRiBot

Step 6. Select New Client (Looking Glass) from the TRiBot selection screen, and then hit Always Allow to all the prompts that pop up.

Step 7. TRiBot should now be hooked to OSBuddy and you're free to bot using Looking Glass

I think im stuck on step 6.... I accidently cancelled the prompts and it wont pop up anymore

Share this post


Link to post
Share on other sites
On 5/7/2017 at 7:53 PM, Fluffee said:

Step 6. Select New Client (Looking Glass) from the TRiBot selection screen, and then hit Always Allow to all the prompts that pop up.

Step 7. TRiBot should now be hooked to OSBuddy and you're free to bot using Looking Glass

I've done everything up to and including "Select New Client (Looking Glass) from the TRiBot selection screen," but the prompts do not pop up for me to "Always Allow"...how do you fix that?

Edited by themanman

Share this post


Link to post
Share on other sites
On 6/1/2018 at 3:49 PM, Zombize said:

Thank you, your post has helped me. Guys if you're reading this, it's proof that this still works as of 01 June 2018. :)

Tried everything in the guide and it hasn't worked for me

EDIT: nvm got it to work

 

Cheers

Edited by Bene

Share this post


Link to post
Share on other sites

L2jZ0q5.png3rsqGDi.png

NySr7Qf.png

https://rsbuddy.com/osbuddy/download?iaccept=true&fileFormat=jar

downloaded from there.

@fluffee

I opened the osbuddy jar, let it load, opened tribot, clicked on looking glass client, and it still can't find it. i provided pictures showing ive got the recommended javas installed and tribot is running off of it and no more.

am i missing something? because it can't find osbuddy to hook onto

Edited by boatsb4hose

Share this post


Link to post
Share on other sites
Posted (edited)
On 12/17/2018 at 4:58 PM, Fluffee said:

Shoot me a message on the forums or on discord. It's most likely a firewall issue, which is easier if I can connect via TeamViewer to sort 🙂

I'm also getting a blackscreen issue. I can see my minimap, inventory and chat area...but the rest of "everything" is black.

https://imgur.com/a/C8Nqw7T

I've uninstalled all other java versions. I've went in and added 185.28.23.227 to my Always Allow.

There has been no change.

Edited by Konoyaro

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Our picks

    • This update features:

      Fixed broken hooks from today's update


      Fix wilderness level with RuneLite (Thanks @Todd)


      Add support for Kotlin .class files in scripts (Thanks @wastedbro)


      Overhaul Inventory API (Thanks @wastedbro)


      Add List support for common methods


      Change method grouping to make more sense (by functionality)


      Refactor methods to utilize Java 8 streams instead of cumbersome loops




      Recognize chatbox minimization (Thanks @JoeDezzy1)


      Fix Screen#isInViewport when NPC chat is open (Thanks @JoeDezzy1)


      Fix login bot bugs (Thanks @erickho123)


      Fix hint arrow return values (Thanks @Encoded)


      Fix depositAllExcept functionality (Thanks @wastedbro)


      Change containing box interface bound and adjust for Y values (Thanks @erickho123)
      • 148 replies
    • 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.
      • 90 replies
    • This release will:

      Add new internal framework for capturing exceptions


      Fix issue with not selecting the last column in world hopper (Thanks @Todd)


      Add a message about pin usage in Banking#openBank (Thanks @Todd)


      Disable the firewall by default (Thanks @Todd)


      Fix handling of the welcome screen after login (Thanks @Encoded)


      Fix wrong amount bank withdrawal (Thanks @Encoded)


      Fix Screen#isInViewport


      Fix Game#isInViewport (Thanks @Encoded)


      Call onBreakEnd for ListenerManager Breaking Listeners (Thanks @Encoded)


      Fix Prayer#getPrayerPoints NumberFormatException (Thanks @JoeDezzy1)



      Note: If you are using LG, please restart both the RS client and TRiBot.
      • 28 replies
    • This release will:

      Fix LG for both OSBuddy and RuneLite


      Fix issue where the resizable client isn't able to be made smaller (Thanks @JoeDezzy1)


      Fix detection of the logout game tab when resizable mode and side panels are enabled (Thanks @JoeDezzy1)


      Add initial support for Sentry to allow us to identify and easily debug exceptions happening with all TRiBot users


      Add methods to determine if the bank is actually loaded, and not just the overarching interface (Thanks @wastedbro)



      Upcoming updates:

      Improved CLI support


      Full Sentry support


      Much more
      • 64 replies
    • This release will:

      Fix NPE in Camera API (Thanks @wastedbro)


      Update deposit box interface ids (Thanks @Encoded)


      Add various bank methods (Thanks @wastedbro)


      Banking#getWithdrawXQuantity


      Banking#getDefaultWithdrawQuantity


      Banking#arePlaceholdersOn




      Fix resizeable minimap bug (Thanks @wastedbro)


      Remove Java 8 requirement


      Please note: TRiBot is not yet fully compatible with Java 10+




      Fix the break handler issues by ensuring the break handler thread never gets paused


      Fix broken settings hooks



      Upcoming updates:

      Improved CLI support


      Much more



      Note: If you are using LG, please restart both the RS client and TRiBot
      • 68 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...