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

After update,looking glass broke

Recommended Posts

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.

 

Debug:

 

debug log.txt

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.


  • Similar Content

    • By TRiLeZ
      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.
    • By joewhite1997
      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.
    • By witn6ss
      Hey guys, I'm currently a VIP member and LG is not showing up for me. It has always shown up and worked before but it isnt now and i just renewed my vip today. i've tried closing and re-opening tribot as well as re-installing it. please help if you can, thanks.
    • By TheIronPride
      Hey everyone i been using looking glass for a few months now, and just today i no longer see it as an option, i only see "new Client" and "New Client (advanced)" where there is normally a "new Client (looking Glass)" option, any suggestions?
    • By Rij
      tribot not working with looking glass what could be reason thanks? it says Looking for Runescape client and it was working before?
       
      Debug Code:
      [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)
    • By ToxicDeadlyMP
      Have you been banned yet?
      I'm not a newbie, I really want to purchase the extended for the looking glass feature. My plan is to run it for about 2-3hrs with a few hours in between as breaks. Never exceeding 3 hours of continuous boting. I want to use it on my main account so I'm wondering if using looking glass with these boting habits will keep me being detected extremely low. I'm also not just going to leave it running and turn off the screen, I'll be watching it for errors and such as I play other games. Also with the added looking glass feature and the human like mouse movements and the breaks, how could they even detect the boting? 
  • 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   0 members

    No registered users viewing this page.

×
×
  • Create New...