Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
Buy OSRS Gold

Sell OSRS Gold
Sign in to follow this  
Todd

TRiBot Dev Release 10.14_3

Recommended Posts

This release will:

  • Attempt an experimental fix to a long-standing issue involving the break handler not working as intended
  • Fix Screen#isInViewport when NPC chat is open.
  • Fix bug involving interface bounds
  • Fix bug involving world sorting
  • Fix depositAll functionality
  • Fix Hint Arrow return values
  • Implement some Inventory API additions
    • - Add List support for common methods
      - Change method grouping
      - Refactor methods to utilize Java 8 streams
  • Fix broken ID value for Advanced Option Interface
  • Add fix to allow GetWildernessLevel to work with a certain HD client's default plugin.

NOTE: this is a DEV release, so for no reason run this release for an extended unsupervised amount of time.
Most of these changes were in the last release, but I mistakenly forgot to document them so I wanted to make a new release.

Note: If you are using LG, please restart both the RS client and TRiBot.

  • Like 4
  • Thanks 1

Share this post


Link to post
Share on other sites

If any public members/scriptwriters notice bugs in any of the above scenarios feel free to contact me through a direct message.
Input on this thread is highly valued and appreciated.
We're releasing these updates to provide a more powerful and effective client for every single person/bot here at/from TRiBot.

  • "Attempt an experimental fix to a long-standing issue involving the break handler not working as intended"
    > This update should fix the breaking issue that's been widely spoken about for a while now. So
    > This proposed fix
    current stands "untested on a large scale", however holds high potential if little to no side effects.

 

  • "Fix Screen#isInViewport when NPC chat is open. "
    > This fix/update is intended to fully restore the functionality of API methods Clickable#isClickable() and isOnScreen() for running clients on Resizeable-mode.
    > This fix/update currently accounts for all interface-able HUD (Game-tabs, Minimized Game-tabs, Data-orbs, Mini-map, Chat-box, NPC chat, Click-through chat-box, Minimized-Chat box, Side panels on/off)

    > This fix/update's algorithm cache's all block-able HUD once, then translates the data relative to the current view-port of any given size.
    This bugs public release would mean a huge performance boost for TRiBot across the board especially for our Looking Glass users. (It is will have less of an effect on the hardware running TRiBot.)
    Input here is as well appreciated, as @FALSkills has pointed out to me in recent days something I left unaccounted for, which occurred due to not accounting for the games rendering distance (X, Y), thus Clickable#isClickable() returning true for entities in the black (UN-rendered) area within the games view-port.  Thank you FALSkills

 

  • Like 1

Share this post


Link to post
Share on other sites
On 5/10/2019 at 6:05 AM, NinjadGuy said:

Have been testing it for a few days now and it seems like it has been fixed. Good job!

Thank you, if there is anything you've noticed since then, like I said, post here or feel free to send a message to myself or one of our developers here at TRiBot. 8 Free credits for you, kind sir, for your generosity of your 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

    • Over the past few months, I’ve been working diligently on a new project - TRiBot X. Everything has been written from the ground up, with all of the best practices of software engineering. Every aspect of TRiBot has been re-imagined to support three main goals: flexibility, useability, and reliability.
        • Like
      • 26 replies
    • Come give us feedback on the next version of TRiBot!
        • Thanks
        • Like
      • 70 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
      • 23 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 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
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...