Jump to content
Sign in to follow this  
fleq6

LG Delay between actions

Recommended Posts

So... When I run a self-made script in the regular TriBot client withot LG, it runs flawlessly. If I run it with LG, it also runs flawlessly in terms of doing what it's supposed to do, but with a problem: quite a lot of delay between each action the bot performs.

Sadly, this means that without LG I get, for example, 15K combat XP per hour, and with LG only 7-8K.

Has anyone experienced this? Does it have a solution? 

Thanks!

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Similar Content

    • By Worthy
      OSBuddy may altar things in the Runescape client and will mess up some actions in game if using Looking Glass.
      For example, if you have the Jewelry Overlay  enabled, then clicking on some charged items (like a Ring of Dueling) may mess up.
       
      Ensure your OSBuddy settings are on default to guarantee Looking Glass running as smoothly as possible
       
       
      How to default your OSBuddy Settings
      Locate your OSBuddy folder ON WINDOWS: C:/Users/username/OSBuddy If you can't find it, just locate the folder of where you launch the OSBuddy jar, and navigate one or two levels up.
        Delete the settings folder  
       
      Now when using OSBuddy all of the custom overlay settings should be turned off.
      Double check if the Jewelry Overlay is disabled; and if not, disable it manually.
       
       
       
      Happy Botting!
      Worthy
    • By grammatoncleric
      Pretty sure I already know the answer, but I am just trying to be lazy and not write the code myself (since i dont write java, but python)(automation), was wondering if there is a cli starter that someone knows of that uses LG, im aware of the one with tribot, and ericks public one, but i think neither support LG (assuming osbuddy is already running for LG to hook into)
      Thanks,
      grammatoncleric
    • By OliverandFelix
      When using looking glass do I still connect to Runescape using the proxy selected through Tribot, or will the mirrored client run through my main ip adress as osbuddy has no option to use a proxy?
    • By zemp0
      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:
          java.io.EOFException
      [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
    • By MilkyWay
      iv never been able to get looking glass working since I joined, but I recently had a bit success and got it to hook on to osbuddy,
      but when I click start scripts nothing happens for me.
    • By herfolj
      Hello, been bitting for a couple of days on the looking glass service here. Yesterday the option didn't show up. Anyone know how to fix this?

      Thanks
    • By miggo13
      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.
  • Our picks

    • This release will:

      Fix bytecode manipulation in order to prevent the modification of parameters within the Filter and Condition classes themselves (thanks @wastedbro)


      Fix NPE caused by non-null value in GE API (thanks @erickho123)


      Add and fix equals methods for api2007.types (thanks @JoeDezzy1)


      Modify Mouse#leaveGame to make the mouse leave the game from top, left, right, or bottom (thanks @erickho123)


      Add Entrana area to Ships API (thanks @erickho123)


      Fix raid prayers index/settings in Prayer API (thanks @erickho123)



      Upcoming updates:

      Break handler bug fix


      Improved CLI support


      Much more



      Note: If you are using LG, please restart both the RS client and TRiBot
        • Like
      • 27 replies
    • This update will:

      Implement better canvas locking/synchronization mechanism


      Fix small Login API bug


      Remove the requirement for xbooting Java classes


      Use ExecutorService to perform canvas work in parallel


      Add "Account Management" game tab to GameTab API (thanks @Encoded)


      Fix NPCChat#getMessage (thanks @Encoded )


      Fix NPCChat#selectOption (thanks @Encoded )


      Fix Banking API after today's update (thanks @Encoded )


      Fix in-game world hopper after today's update (thanks @Encoded )



      Upcoming updates:

      Break handler bug fix


      Improved CLI support


      Much more



      Note: If you are using LG, please restart both the RS client and TRiBot
        • Thanks
        • Like
      • 38 replies
    • 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.





      Coming soon:

      Skull icon fix


      Improve screen rate and responsiveness of the RS client (both regular client and LG)


      Much more
        • Thanks
        • Like
      • 33 replies
    • 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


      Fix hooks



      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.
        • Thanks
        • Like
      • 25 replies
    • 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!
        • Thanks
        • Like
      • 30 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×