Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
Sign in to follow this  
TRiLeZ

TRiBot Release 10.9_0

Recommended Posts

This release will:

  • Fix an issue where breaks would stop firing
  • Fix Combat#getWildernessLevel, use dynamic search for text and cache ID for later calls (Thanks @JoeDezzy1)
  • Fix an NPE in the Combat API (Thanks @JoeDezzy1)
  • Fix Mouse#leaveGame bug where the mouse wouldn't actually leave the game screen (Thanks @Encoded)
  • Like 3

Share this post


Link to post
Share on other sites

Has it solved the issue with breaks not firing for anyone reading this thread? From my today's testing, Tribot now fires even FEWER breaks than 2 days ago:

1. First break of the session, which used to fire consistently, now doesn't. It now works ~half the time. Consecutive breaks, just like in 10.8, consistently never fire.

2. Resizable mode breaks, which were firing mostly normally in 10.8, now don't work. Same with LG.

Break system in 10.9 is in worse shape than it's  been in 10.8. The last version with somewhat functioning breaks was 10.5.

 

Long standing, 3-4 months old bug where session wouldn't correctly resume after a break, is still present. It's occured several times in the past few hours for me, running on version 10.9.

  • Sad 1

Share this post


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

Has it solved the issue with breaks not firing for anyone reading this thread? From my today's testing, Tribot now fires even FEWER breaks than 2 days ago:

1. First break of the session, which used to fire consistently, now doesn't. It now works ~half the time. Consecutive breaks, just like in 10.8, consistently never fire.

2. Resizable mode breaks, which were firing mostly normally in 10.8, now don't work. Same with LG.

Break system in 10.9 is in worse shape than it's  been in 10.8. The last version with somewhat functioning breaks was 10.5.

 

Long standing, 3-4 months old bug where session wouldn't correctly resume after a break, is still present. It's occured several times in the past few hours for me, running on version 10.9.

@contemporary


Yeah, the latest release did not fix the breaking bug, in fact it's actually even worse for me now.

I really wish I could just revert to say 10.5 or 10.6 version of the client where I had no issues, It's screwed up my scheduling and the way I farm with tribot, it's extremely frustrating. I'm forced to update the client that gives me more problems every time and not the other way round, It's sad to see a feature that is the core of tribot really bugging out right now. If only there was an archive option, I'd kill for 10.5/10.6 version of the client atm :(

@TRiLeZ

Please have another shot at fixing it..

Share this post


Link to post
Share on other sites

Hello guys,

I have a problem since last patch that was not fixed, pretty much if i have multiple tabs and i switch beetween them a couple times the top part of the client turns black and i am never able to interect with the client again even tho the scripts are running, could you guys please take a look?

Share this post


Link to post
Share on other sites
55 minutes ago, Ratz241 said:

@contemporary


Yeah, the latest release did not fix the breaking bug, in fact it's actually even worse for me now.

I really wish I could just revert to say 10.5 or 10.6 version of the client where I had no issues, It's screwed up my scheduling and the way I farm with tribot, it's extremely frustrating. I'm forced to update the client that gives me more problems every time and not the other way round, It's sad to see a feature that is the core of tribot really bugging out right now. If only there was an archive option, I'd kill for 10.5/10.6 version of the client atm :(

@TRiLeZ

Please have another shot at fixing it..

After a bit more testing, it seems the break/relogin bug that's been plaguing Tribot for the last few months is now occuring much more frequently.

In previous Tribot versions the average bug "trigger" rate was about 2% per break for me, in a sample of several thousand breaks. Sometimes I would get several a day, sometimes none for a couple days.

So far today I've had the bug happen on ~30% of all breaks. Numerically, it triggered more times today than during the whole week prior, combined. And that's on just 1 break per day/per account due to broken general break system.

Share this post


Link to post
Share on other sites
7 minutes ago, contemporary said:

After a bit more testing, it seems the break/relogin bug that's been plaguing Tribot for the last few months is now occuring much more frequently.

In previous Tribot versions the average bug "trigger" rate was about 2% per break for me, in a sample of several thousand breaks. Sometimes I would get several a day, sometimes none for a couple days.

So far today I've had the bug happen on ~30% of all breaks. Numerically, it triggered more times today than during the whole week prior, combined. And that's on just 1 break per day/per account due to broken general break system.

Currently, anytime the loginbot activates (notified by the client debug line [17:20:41] Login bot started.) your breaks will stop working. I've already told the devs about this.

Edited by Naton

Share this post


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

After a bit more testing, it seems the break/relogin bug that's been plaguing Tribot for the last few months is now occuring much more frequently.

In previous Tribot versions the average bug "trigger" rate was about 2% per break for me, in a sample of several thousand breaks. Sometimes I would get several a day, sometimes none for a couple days.

So far today I've had the bug happen on ~30% of all breaks. Numerically, it triggered more times today than during the whole week prior, combined. And that's on just 1 break per day/per account due to broken general break system.

 

I can confirm this also, I had a very low rate of the login bot bug occurring, but after this update I am getting a ton more which rubs even more salt in this wound at this point.

Just a revert back to 10.5 on the login bot/breaking while leaving everything else in tact would be helpful if it cannot be fixed swiftly, it at least gives us chance to schedule our bots and not worry too much about a potential fix, until a solid patch has been tested and released.

Share this post


Link to post
Share on other sites
12 hours ago, Naton said:

Currently, anytime the loginbot activates (notified by the client debug line [17:20:41] Login bot started.) your breaks will stop working. I've already told the devs about this.

Tribot's quality control and testing could use a look, if obvious bugs like this can make it to live updates.

1 Minute of live testing reveals this bug every time.

  • Like 1

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  

  • Our picks

    • 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
      • 50 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
    • This release will:

      Add support for using custom F key bindings to switch between game tabs (Thanks @erickho123)


      Fix tab opening for "Skills" and "Kourend Tasks" (Thanks @erickho123)



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

      Fix an issue where breaks would stop firing


      Fix Combat#getWildernessLevel, use dynamic search for text and cache ID for later calls


      Fix an NPE in the Combat API


      Fix Mouse#leaveGame bug where the mouse wouldn't actually leave the game screen
      • 21 replies
    • This release will:

      Add LG support for Runelite


      Fix NPCChat issues


      Fix a bug where the camera angle setter would just hold down a key for 5 seconds (the timeout)


      Slightly adjust the rotation via keys to be more accurate


      Add the ability for asynchronous camera movement via keys


      Make Camera rotation via mouse more fluid, with more antiban, and work much better in resizable mode


      Add a "Camera#setCamera" method, allowing the rotation and angle to be set in parallel


      Increase the likelihood of using the mouse for camera movements


      Add support for adjusting the camera to positionable entities (Positionable#adjustCameraTo)



      Upcoming updates:

      Improved CLI support


      Much more



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

    No registered users viewing this page.

×