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
Guest
This topic is now closed to further replies.
Sign in to follow this  

  • Our picks

    • [READ TO THE END FOR A TEASER]

      I've noticed some new TRiBotters have had some troubles finding out sources of how to do certain things, such as using advanced scripts and often get lost in the forums.

      We are still getting posts asking where to start, what to do, recommended scripts, etc. 

      As many of you know, I am new to the team, and had troubles myself learning how to bot, let alone script. 

      So, what our team decided to do was make it easier to learn how to bot, how to script, and just become an overall better botter and scripter faster. 

      As some of you might have seen, I've posted 3 new blogs, you can check it out by clicking on the following picture or here.


      These first 3 blogs are the first of many blogs that will be TRiBot official. They are encouraged to be challenged, improved upon and act as A Best Practices Guide for Botters.

      What information would you like to see in the blogs?

      👇 [TEASER] 👇

      .

      .

      .

      We are going to be hosting a  CONTEST  this  OCTOBER.

      Its scary to think how soon you'll find out.👻

      Stay tuned.


      - RileyZ
      • 8 replies
    • Today marks a big day for TRiBot! To make it easier for users to use TRiBot, we've created installers available for every platform! These installers are all bundled with the latest version of OpenJDK 1.8 (Java 😎, which is LG compatible.

      Using TRiBot is now easy. Simply download the installer for your platform, install TRiBot, and run it. The TRiBot Loader will correctly identify the bundled JDK so there's no need to change the Java selection.

      Windows

      EXE installer: TRiBot-windows-x64-4.0.3.exe


      MSI installer: TRiBot-windows-x64-4.0.3.msi


      Portable version: TRiBot-windows-x64-4.0.3.zip


      Mac OS

      Installer: TRiBot-macos-4.0.3.dmg


      Portable version: TRiBot-macos-4.0.3.tgz


      Unix/Linux

      Installer: TRiBot-unix-4.0.3.sh


      RPM installer (CentOS/Fedora): TRiBot-linux-4.0.3.rpm


      DEB installer (Debian): TRiBot-linux-4.0.3.deb


      Portable version: TRiBot-unix-4.0.3.tar.gz


      Platform Independent

      JAR file: tribot-loader-4.0.3.jar


      Note that this jar file does not include the bundled JDK.



      Windows and Mac OS users may notice a warning message stating that the installer/application is un-recognized or un-trusted. Please ignore this message and proceed with running the installer/application. We need to acquire a code signing certificate so that we can sign the installers letting the operating system know that these files can be trusted. It will take a week or more to acquire one, so please hold tight.

      Other notable changes to the TRiBot Loader:

      Support getting the version from OpenJDK distributions


      Add check for bundled JDK


      Copy OpenJDK tools.jar to the bundled JDK if not present


      Set the current java as the first available list entry


      Ignore Java versions which are symbolic links


      Make the bundled JDK the preferred Java version


      Update icon images


      Reduce the number of HTTP calls
        • Thanks
        • Like
      • 18 replies
    • TRiBot is looking to improve a lot of its customer relationship management, customer on boarding process, customer experience, design elements, community engagement and pretty much everything else you can imagine when it comes to marketing.

      Our goal: To ensure that the marketing done TRULY reflects the experience and does not shine an inaccurate light on what TRiBot is lacking in.

      So I ask, what do you love about TRiBot and what do you hate about TRiBot? What does O S Bot, Rune M8, PowR Bot and Dre amBot do better? (yes I purposely didn't spell it right 😂).

      Love, 

      RileyZ
        • Like
      • 17 replies
    • Hello TRiBot,

      Today we have a significant release that has been in the works for the last month addressing several key issues, features and bugs in the backlog.

      With these changes, we are also including a new TRiBot Loader which will allow you to select any version that is released. This adds the flexibility of allowing you to revert to a previous version should an issue arise, run development only builds, view an accurate change log between versions etc. we are very proud to offer this feature and think it will add a lot more functionality down the road as we continue to release new versions.

      These changes include 80+ commits by our development team, a list of them is summarized below and also available for your viewing pleasure in the new TRiBot Loader.

      In addition, we have taken additional steps to improve as a development team by adding continuous integration and deployment into our workflow to assist in delivering timely releases such as bug fixes as well as new features on a weekly basis depending on our development cycle.
        • Thanks
        • Like
      • 39 replies
    • Over the last three weeks, I've been working on upgrading our server infrastructure. It's finally ready and is now live!

      Why?

      Increased reliability - less server errors


      Increased availability - less downtime


      Increased security - keeping us and you secure


      Increased capacity - ability to serve you better


      Increased speed - less waiting for things to load


      Faster development - server and service updates will come faster


      What are the changes?

      Move from a single AWS EC2 instance to AWS ECS (Elastic Container Service)


      Distributed computing


      Load balancing


      Git management of server files and filesystem


      Redis caching


      How?

      AWS ECS (with 10 EC2 instances)


      AWS ElastiCache (Redis)


      AWS Load Balancing


      AWS EFS (Elastic file system)


      Please bare with us as I continue to tune the server for maximum performance. Slow loading speeds may occur temporarily. I thank everyone for their patience.

      Please post on this thread if you experience any issues other than slow loading times.
        • Like
      • 51 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...