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

The Complete Guide To Looking Glass

Recommended Posts

The Complete Guide To Looking Glass

 

Looking Glass is a hirwlxB.png feature, but information about it should be free for all users.

 

 

Table of Contents

  • What is Looking Glass?
  • Ban-Rate Difference
  • How to Fix Looking Glass
  • Proxy Usage
  • Bugs & Solutions

 

What is Looking Glass?

 

The standard TRiBot client works by loading the RuneScape client into itself. Looking Glass works in a fundamentally different way:

1. The user opens a legitimate RuneScape client (official release or approved third party such as OSBuddy).

2. Looking Glass finds the RuneScape instance process and hooks onto it.

3. From this point on, TRiBot can retrieve and send data to the client.

Since the legitimate RuneScape client is the one communicating with the server and TRiBot is not involved in the process, client detection becomes almost impossible.

 

 

Ban-Rate Difference

 

Looking Glass cannot guarantee a lower ban rate.

Its only purpose is to conceal the TRiBot client itself and make it completely invisible to any potential client detection code implemented on the client or server side.

However, even if Jagex is no longer capable of detecting third party software on a code level, all patterns and heuristics generated by the running script are not affected at all by Looking Glass. Reaction times, mouse movement, mouse speed, clicking locations, camera and everything else related to the player's actions, are all controlled by the running script and altered by the client's input modifiers (for example fatigue). All the patterns generated can and will still be collected and analyzed by their automated data processing system, regardless of the type of client used.

With that being said, some users believe that Looking Glass can drastically extend the life span of their bots, while other users think that it makes no difference whatsoever. You will have to test it and decide for yourself. One thing is for sure though, Looking Glass will use significantly more resources than the normal client.

 

 

 

How to Fix Looking Glass

 

Thank you @Fluffee for posting this comment. Most users to whom I've sent this link have managed to fix Looking Glass in a timely manner. This whole section is based on Fluffee's reply.

 

Using Looking Glass requires hirwlxB.png

As stated at the beginning of this guide, VIP-E is required in order to use this feature. If you already have VIP, you can upgrade to the required package by paying the difference on the same page where you've made your purchase. Scroll all the way down and you will see the upgrade option: https://tribot.org/repository/user_panel/vip/

 

 

HFScVNj.png

Although the message indicates that you need to use the 32 bit Java version, this might not be always the case, as the requirement is to run both the legitimate RuneScape client and TRiBot on the same Java bit version.

 

Here is a thread where users shared their own Looking Glass setup. If you want to experiment with different versions, you can use this as a guideline: https://tribot.org/forums/topic/73658-share-your-looking-glass-setup/

 

 

Important note: You will need to follow the following instructions step by step. Do not skip any of them, otherwise Looking Glass might not hook. If it still fails to work despite the fact that you've done everything listed here, check your Anti Virus and Firewall and make sure that both TRiBot and the RuneScape client are not blocked in any way by them.

 

Step 1 - The downloads

 

Step 2 - Delete all other Java versions

  • Navigate to Control Panel\Programs\Programs and Features.
  • Uninstall all other Java versions.
  • Make sure there is nothing left.

 

Step 3 - Install JDK 102

  • Install the Java version downloaded at step 1
  • If you've followed the instructions correctly, this should be the only Java version installed on your computer.

 

Step 4 - Open OSBuddy

  • Launch OSBuddy
  • Wait for the game to load
  • Minimize it in the system task bar and do not maximize it again during the botting session.

 

Step 5 - Open TRiBot

  • With the OSBuddy client minimized, open TRiBot
  • After it finished loading, start a new Looking Glass Client

eFGEwtZ.png      or        w8NMGpg.png

 

 

Congratulations! If you've followed the instructions step by step, Looking Glass will successfully hook onto OSBuddy and you are ready to start botting!

 

 

 

 

 

 

Proxy Usage

 

Looking Glass supports proxy usage.

The legitimate RuneScape client will be initialized on your computer's IP address. As soon as looking glass hooks into it, all client-server communication will be passed through the proxy specified by TRiBot.

There is no reason to use any third party software and try to initialize OSBuddy from the proxy address, as there is no account that Jagex can associate data to. (Do not log in RuneScape before Looking Glass hooks.)

 

 

 

 

Bugs & Solutions

 

TRiBot doesn't open now! What happened?

  • Run the jarfix program linked in step 1
  • Launch TRiBot again, assuming you followed all other steps, it should load fine.

Looking Glass still doesn't work!

  • Follow the instructions above, make sure that you are not skipping any step.
  • Make sure that your antivirus / firewall are not blocking any connections for TRiBot / the RuneScape client.
  • The most stable Java versions are 102 and 112. Try both 32 bit and 64 bit versions.

 

Low FPS!

  • Minimize OSBuddy before hooking Looking Glass.
  • Do not maximize it again for the entire botting session.

 

Break handler doesn't work on Looking Glass!

  • Minimize OSBuddy before hooking Looking Glass.
  • Do not maximize it again for the entire botting session.

 

java.nio.file.AccessDeniedException

  • Like 3
  • Thanks 1

Share this post


Link to post
Share on other sites
5 hours ago, Einstein said:

With that being said, some users believe that Looking Glass can drastically extend the life span of your bots, while other users think that it makes no difference whatsoever. You will have to test it and decide for yourself. One thing is for sure though, Looking Glass will use significantly more resources than the normal client.

I'm glad you didn't take a side. Nice guide! Should add in if it's still not connecting and you only have one java installed try running jarfix.

I had 64bit java and osbuddy and it wasn't connecting. Ran that and bam it worked. 

  • Like 1

Share this post


Link to post
Share on other sites
49 minutes ago, Okina said:

Excellent guide, kudos.

I've got both OSBuddy and TRiBot running in 64-bit, and there's a quite significant lag.  I tried minimizing OSB and opening TRiBot, to no avail.  Any other tips?

You should minimize OSBuddy before even starting TRiBot. Then start it, hook looking glass and don't maximise OSBuddy again.

Most users managed to solve the FPS problem by doing this.

 

Also, you should only have one single TRiBot window maximized at any given time, otherwise the FPS issue will be caused by another known client bug.

Share this post


Link to post
Share on other sites
On 1/16/2018 at 4:21 PM, Einstein said:

You should minimize OSBuddy before even starting TRiBot. Then start it, hook looking glass and don't maximise OSBuddy again.

Most users managed to solve the FPS problem by doing this.

 

Also, you should only have one single TRiBot window maximized at any given time, otherwise the FPS issue will be caused by another known client bug.

MAJOR FIX! Thank you so much fixed FPS for me. noticed my my computer components(CPU, GPU, ECT.)  are running under 15% in all and i was lagging but this fixed it!

  • Like 1

Share this post


Link to post
Share on other sites
On 1/16/2018 at 3:26 PM, Okina said:

Excellent guide, kudos.

I've got both OSBuddy and TRiBot running in 64-bit, and there's a quite significant lag.  I tried minimizing OSB and opening TRiBot, to no avail.  Any other tips?

along with Einstein  - try installing X32 version of os buddy huge improvement there as well-

good luck

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)
        • Like
      • 151 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.
        • Sad
        • Haha
        • Thanks
        • Like
      • 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.
        • Thanks
        • Like
      • 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
        • Like
      • 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
        • Like
      • 68 replies
  • Recently Browsing   1 member

×
×
  • Create New...