Jump to content
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 update will:

      Fix GE inventory item positioning bug


      Fix broken object hooks
        • Like
      • 23 replies
    • This release will:

      Fix some ClosedChannelException bug


      Fix bug in RSObject#getAllTiles


      Add game tab support for "Kourend Favour"
      • 15 replies
    • This release will:

      Fix Settings UI placement bug


      Fix game object location bug


      Fix small layout bug making the client shift up and down


      Fix client crashing bug where loading the client with a small display area will cause the client to crash


      Fix annoying Linux bug relating to painting events and peers


      Fix settings saving bug where settings are saved to disk more often than they should


      Fix RSInterface#isBeingDrawn bug affecting a limited amount of people


      Drop Java 1.7 bytecode version for 1.8


      Important: Since the downloadable RS client uses Java 7, it will no longer be compatible with Looking Glass. To make up for this, we will add support for using other clients such as RuneLite (at a later date).


      This change was necessary to allow us to use Java 8 syntax. It also paves the way for Java 9/10/11 support.
        • Haha
      • 40 replies
    • This update will:

      Fix the RSMenuNode bug which also fixes the bug with bank opening


      Fix the incorrect object positions bug


      Fix and re-enable the LG Objects API Accelerator


      Fix the RSObject#getAllTiles bug
      • 22 replies
    • Try our development release by checking "Development Release" on the TRiBot Loader. Note that these new features are currently in beta.

      This release features:

      Re-sizable mode support for both LG and the regular client


      Slightly improved login bot


      Removed final access modifiers from API classes


      Added RSServer hook wrapper to get the client's cached list of server/world info


      [NEW] Bug fix for intelligent banking


      [NEW] Improvement to the stability of LG over time


      [NEW] Vastly improved the reliability and speed of Screen#getColorAt on both LG and the regular client


      [NEW] Fix LG login problems


      [NEW] Fixed re-sizable mode container bug


      [NEW] Fixed re-sizable mode mouse bug


      [NEW] Use of public constants in the Banking API


      [NEW] Use of other various constants such as Projection#NULL_PT and Screen#EMPTY_COLOR



      More features to come very soon!

      Please test it and let us know here if there are any new bugs introduced in this release.
        • Like
      • 12 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×