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

TRiBot Release 9.100_0

Recommended Posts

I hope the maze is fixed, just downloaded _5 i believe. So odd, maze worked for me, and as far as i know everybody else when i signed up almost 3 weeks ago, but the random failures have been so frequent is so annoying, heh.

 

Thanks for the update.

 

Trilez, could you expand on Max Heap Size btw? I saw the other thread where you said 512 for 2 bots, etc etc.

 

But did you mean if you plan on running 2 bots, you do 512 on both clients

 

or 256 on bot 1, 512 on bot 2, 720 (or whatever it was) on bot 3, etc.

 

Let me know, thanks again.

Edited by avengerduels

Share this post


Link to post
Share on other sites

I hope the maze is fixed, just downloaded _5 i believe. So odd, maze worked for me, and as far as i know everybody else when i signed up almost 3 weeks ago, but the random failures have been so frequent is so annoying, heh.

 

Thanks for the update.

 

Trilez, could you expand on Max Heap Size btw? I saw the other thread where you said 512 for 2 bots, etc etc.

 

But did you mean if you plan on running 2 bots, you do 512 on both clients

 

or 256 on bot 1, 512 on bot 2, 720 (or whatever it was) on bot 3, etc.

 

Let me know, thanks again.

  • Max Heap Size
    • This controls how much memory you allow the Java Virtual Machine to use.
    • Please do not use more than 256mb per client that you run. Ex: Don't use more than 256mb if you are only running one client. Do not use more than 512mb if you are only running two clients. Do not use more than 1024mb if you are only running four clients.
    • Try using this formula for the amount you should allocate: 256MB + ((amount of clients - 1) * 128MB)
      • Warning: This formula isn't perfect.

Share this post


Link to post
Share on other sites

 

I hope the maze is fixed, just downloaded _5 i believe. So odd, maze worked for me, and as far as i know everybody else when i signed up almost 3 weeks ago, but the random failures have been so frequent is so annoying, heh.

 

Thanks for the update.

 

Trilez, could you expand on Max Heap Size btw? I saw the other thread where you said 512 for 2 bots, etc etc.

 

But did you mean if you plan on running 2 bots, you do 512 on both clients

 

or 256 on bot 1, 512 on bot 2, 720 (or whatever it was) on bot 3, etc.

 

Let me know, thanks again.

  • Max Heap Size
    • This controls how much memory you allow the Java Virtual Machine to use.
    • Please do not use more than 256mb per client that you run. Ex: Don't use more than 256mb if you are only running one client. Do not use more than 512mb if you are only running two clients. Do not use more than 1024mb if you are only running four clients.
    • Try using this formula for the amount you should allocate: 256MB + ((amount of clients - 1) * 128MB)
      • Warning: This formula isn't perfect.

 

Ya i already read that. I wanted to know if you meant 1st client = 256mb, then 2nd client is 512mb

 

or if you meant, if running two clients if you put BOTH on 512mb, or if you gradually increase it individually per client.

 

For example, lets say i want to run 2 clients, do i start 2 bots and put them both to 512? Or do i make one 256, and the second one 512?

 

Also, please fix the maze and freaky forrester (less annoying) asap, it seriously depreciates the usefulness of the bot.

Share this post


Link to post
Share on other sites

Ya i already read that. I wanted to know if you meant 1st client = 256mb, then 2nd client is 512mb

 

or if you meant, if running two clients if you put BOTH on 512mb, or if you gradually increase it individually per client.

 

For example, lets say i want to run 2 clients, do i start 2 bots and put them both to 512? Or do i make one 256, and the second one 512?

 

Also, please fix the maze and freaky forrester (less annoying) asap, it seriously depreciates the usefulness of the bot.

 

The more clients you run per TRiBot window, the greater the needed heap size. If you run 2 clients in one window, you should use between 384-512 MB.

 

A new maze solver should be coming this weekend. If you have an account in the Freaky Forester/Maze random, PM it to me so I can fix the solver.

Share this post


Link to post
Share on other sites

The more clients you run per TRiBot window, the greater the needed heap size. If you run 2 clients in one window, you should use between 384-512 MB.

 

A new maze solver should be coming this weekend. If you have an account in the Freaky Forester/Maze random, PM it to me so I can fix the solver.

The problem is, the random solver usually succeeds on 2nd try, 3rd try, etc. And isn't a 100% fail/0% succeed.

 

I would suggest recoding the login bot to start when the game is in the main menu for ANY reason. That way if something like this occurs again in the future, the login bot will keep on trying indefinitely, instead of just freezing at the menu until I have to wake up and manually start over. just a suggestion.

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

    • 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
        • Like
      • 62 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
        • Like
      • 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
        • Like
      • 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
        • Like
      • 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
        • Thanks
        • Like
      • 59 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×