Jump to content
TRiLeZ

TRiBot Release 9.400_2

Recommended Posts

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.

  • Like 6
  • Thanks 2

Share this post


Link to post
Share on other sites
1 minute ago, TRiLeZ said:

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.

❤️❤️❤️ u da best trilez

Share this post


Link to post
Share on other sites
Posted (edited)
5 minutes ago, TRiLeZ said:

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.

It looks like the update broke LG. Just restarted my TRiBot Loader and now it can't hook onto OSBuddy. Not sure why?

EDIT: Looks like I had to restart the OSBuddy clients. Works fine now!

Edited by coffeedog

Share this post


Link to post
Share on other sites

@TRiLeZ I used to be able to minimize clients and reduce my cpu usage to about 1/3 of what it would be when it is open/visible in desktop, but now it has the same cpu usage for every client even when it is minimized. Is there a fix on this problem? Is anyone else here having the same problem?

Share this post


Link to post
Share on other sites
36 minutes ago, mike9021 said:

@TRiLeZ I used to be able to minimize clients and reduce my cpu usage to about 1/3 of what it would be when it is open/visible in desktop, but now it has the same cpu usage for every client even when it is minimized. Is there a fix on this problem? Is anyone else here having the same problem?

Turn up your paint delay to save cpu usage

Share this post


Link to post
Share on other sites
Posted (edited)
36 minutes ago, tarxan said:

Turn up your paint delay to save cpu usage

I have been running for months and this is the first time a minimized client with no account logged in and no script running consumes 14% of my cpu usage it has always averaged around 4% only. Not even disabling graphics would help. My paint delay has always been the same 20ms and I need it that way for the scripts I run.

I have added a picture of the cpu usage of my clients. The first three are running around killing npcs etc, and the highlighted fourth one is a freshly launched minimized client(no running script and no logged in account). This wasn't the case before the update. I need this to be the way it used to before because I need my cpu usage to run other accounts while some of them are on a break. Any help would be much appreciated.

 

cpu usage.PNG

Edited by mike9021
image of cpu usage added

Share this post


Link to post
Share on other sites
4 hours ago, H22A4 said:

Looking glass is now a black screen for me after this update. Ive deleted and re installed tribot, osbuddy and java, Still the same issue.

 

3 hours ago, Leonidas said:

Running into the same issue.

 

6 hours ago, coffeedog said:

It looks like the update broke LG. Just restarted my TRiBot Loader and now it can't hook onto OSBuddy. Not sure why?

EDIT: Looks like I had to restart the OSBuddy clients. Works fine now!

I found a fix for the black screen issue. First load a client within Tribot without using LG, then close the client open up a new one and LG should work. Happened to me and this fixed the issue.

  • Like 3

Share this post


Link to post
Share on other sites
1 hour ago, border said:

 

 

I found a fix for the black screen issue. First load a client within Tribot without using LG, then close the client open up a new one and LG should work. Happened to me and this fixed the issue.

Thank you, this worked for me! :D

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

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

    No registered users viewing this page.

×