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

TRiBot Release 10.18_3

Recommended Posts

This release will:

18_1

  • Fix a issue with camera movement in Looking Glass
  • Add banking default withdraw quantity
  • Fix big object model positions

18_2

  • Improve mouse movement for looking glass
  • Add additional login bot messages

18_3

  • Implement nature rune name fix

 

Updates to LG and Runelite compatibility coming in a future update.

 

  • Like 3

Share this post


Link to post
Share on other sites
18 minutes ago, Todd said:

This release will:

  • Fix a issue with camera movement in Looking Glass
  • Add banking default withdraw quantity
  • Fix big object model positions

Updates to LG and Runelite compatibility coming in a future update.

This is the same client as 18_1 Dev Release, just released to the main branch.

Any update for the new login screen message?

  • Like 2
  • Thanks 1

Share this post


Link to post
Share on other sites
2 hours ago, Todd said:

This release will:

  • Fix a issue with camera movement in Looking Glass
  • Add banking default withdraw quantity
  • Fix big object model positions

Updates to LG and Runelite compatibility coming in a future update.

This is the same client as 18_1 Dev Release, just released to the main branch.

No update to the new login message?

This new OSRS message is uniform and Tribot can't handle it, so a lot of sessions now stop prematurely. It can happen due to disconnect, 6hour forced logout, world hopping, etc.

https://gitlab.com/trilez-software/tribot/TRiBot-Issues/issues/134

  • Like 1

Share this post


Link to post
Share on other sites
14 hours ago, contemporary said:

No update to the new login message?

This new OSRS message is uniform and Tribot can't handle it, so a lot of sessions now stop prematurely. It can happen due to disconnect, 6hour forced logout, world hopping, etc.

https://gitlab.com/trilez-software/tribot/TRiBot-Issues/issues/134

This is a problem it affects some of my instances for sure

Share this post


Link to post
Share on other sites

Hi all. Posted a little _3 update with the nature run fix.

We're focusing on the back-end of TRiBot right now to help with server stability, release cycles, development and more. As always let me know if you have any questions.

  • Like 2

Share this post


Link to post
Share on other sites
Posted (edited)

Will it ever be possible to have an option on whether or not we want to update Tribot instead of it being mandatory? seems a bit excessive to have an update just to fix one item, if that's all that went down in _3

Edited by theholyone

Share this post


Link to post
Share on other sites
30 minutes ago, theholyone said:

Will it ever be possible to have an option on whether or not we want to update Tribot instead of it being mandatory? seems a bit excessive to have an update just to fix one item, if that's all that went down in _3

It takes like 2 mins to download my guy. 

Share this post


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

Will it ever be possible to have an option on whether or not we want to update Tribot instead of it being mandatory? seems a bit excessive to have an update just to fix one item, if that's all that went down in _3

It was a fix for hooks which affected numerous RSObjects, I think he meant for the altar.

Share this post


Link to post
Share on other sites
Posted (edited)

It seems the break handler problem is back since today, not this shit again, is there any way for me to use the previous version i dont want to deal with this broken crap again, thank you!!!!

Example:

  • [22:58:09] Break Handler: Break ended.
  • [23:01:30] The maximum amount of instances for this script has been surpassed. Stopping script (1). Message: 0
Edited by 9055394

Share this post


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

It seems the break handler problem is back since today, not this shit again, is there any way for me to use the previous version i dont want to deal with this broken crap again, thank you!!!!

Are you sure it's the same break handler issue? All that was changed was runecrafting altars in _3

Share this post


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

Are you sure it's the same break handler issue? All that was changed was runecrafting altars in _3

Not completely sure yet, but it sure seems like it, or something else is cause the script to stop after a break ends, and after 3 hours half of my instances were stopped, its actually worse in this state, will keep you posted 

On most instance stops it was minutes after the break ended, just like before, i dont know what is causing this crap this time

  • [22:58:32] Break Handler: Break ended.
  • [23:01:30] The maximum amount of instances for this script has been surpassed. Stopping script (1). Message: 0
Edited by 9055394

Share this post


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

  • Our picks

    • 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
    • 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
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...