Jump to content
TRiLeZ

TRiBot Beta 7.12_0

Recommended Posts

Great thanks, have you addressed the bug where it sometimes tries to click tiles off the minimap? This only happens when you first start webwalking. 

I addressed an issue where minimap tiles where in-accurately calculated depending on the camera angle. So I think that should fix the off-minimap tile clicking.

 

 

great update. :)

 

@Trilez Is it possible if you could make Grounditems detect amounts?

I don't believe it's possible to detect Ground Item stack.

Share this post


Link to post
Share on other sites

I addressed an issue where minimap tiles where in-accurately calculated depending on the camera angle. So I think that should fix the off-minimap tile clicking.

 

 

I don't believe it's possible to detect Ground Item stack.

 

Does WebWalking support the wild yet? Everytime I tried to use it for a tile in the wild, it walked west (even if I was only a few squares on the south side of the ditch). It seemed to work when I was actually in the while, though.

Share this post


Link to post
Share on other sites

Does WebWalking support the wild yet? Everytime I tried to use it for a tile in the wild, it walked west (even if I was only a few squares on the south side of the ditch). It seemed to work when I was actually in the while, though.

No, not yet. It will soon though.

Share this post


Link to post
Share on other sites

Hey Trilez, did any1 reported tribot breaks with the latest update on linux yet? I was running some scripts and the script ended abruptly http://imgur.com/mqgi0pz, so I restarted the client and it prompted me to redownload the jar file as its outdated, to the newest 1.61. The login interface pops out and after entering credentials and clicking on login, it takes forever to load and the interface where you select "new client" doesn't pop out but this instead http://imgur.com/rT75gFM. I tried changing forum password as suggested by druid but does no difference. If this is because of the latest update, a fix/update would be greatly appreciated :D Thanks!

Share this post


Link to post
Share on other sites

On ubuntu, when running multiple bots either a client goes all white when switching screens,can kill the process with task manager only, or all the clients freeze and cant even close them, only solution is restarting the vnc

can't provide any errors logs because theres none, and no, cpu isn't even over 60% and got enough ram for it, never goes over 40%, even changed the max heap size to 1gb

started happening since TRiBot Beta 7.03_0 i think

Share this post


Link to post
Share on other sites

To be honest, client version 7.0_25 was the best I still got some clients opened.

Facts about version 7.0_25:

1. They take a lot less cpu then the current version of client (running on centos 5.9,7.0_25v takes around 2 times less cpu then the current tribot client version)

2. They don't crash, non of my 7.0_25 clients crashed and with current version of the client you get white-out every ~5 hours and you can't even kill the process (kill (pid) or killall java, won't even kill the client that froze, you have to reboot computer..).

 

Could it be possible to backup 7.0_25 version of client? Because it was the best one for linux users =)

Maybe I am missing something and we can boot older version of the client, but I just don't how?

 

EDIT: I just realized that 1.7.0_25 is my java version and that's not a tribot client's version. I can't check the version of the client, since message from client's log is gone :/. However I know that client used Tribot loader 1.58

Edited by yutpod
  • Like 1

Share this post


Link to post
Share on other sites

To be honest, client version 7.0_25 was the best I still got some clients opened.

Facts about version 7.0_25:

1. They take a lot less cpu then the current version of client (running on centos 5.9,7.0_25v takes around 2 times less cpu then the current tribot client version)

2. They don't crash, non of my 7.0_25 clients crashed and with current version of the client you get white-out every ~5 hours and you can't even kill the process (kill (pid) or killall java, won't even kill the client that froze, you have to reboot computer..).

 

Could it be possible to backup 7.0_25 version of client? Because it was the best one for linux users =)

Maybe I am missing something and we can boot older version of the client, but I just don't how?

Ahh not only me noticed that bot uses a lot more cpu. I'm using win8

Share this post


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

  • Our picks

    • This release includes:

      Fix updater bug which was causing a bunch of issues


      TRiBot will no longer require manual hook fixes every time the RS client updates - the updater has been fully patched for objects


      Hooked login fields


      Improved the login bot


      Ability to recognize the banned/locked messages again


      Ability to read the current input for username and password fields


      If the username or password is already entered correctly, it won't be erased


      If only part of the username or password is already entered correctly, it won't be erased. The login bot will fill in what's missing.


      If there are a few invalid characters after a valid substring of your username/password, only (approximately) those invalid characters will be erased. The login bot will then proceed to fill in the missing characters.





      Coming soon:

      Skull icon fix


      Improve screen rate and responsiveness of the RS client (both regular client and LG)


      Much more
        • Thanks
        • Like
      • 23 replies
    • This release includes:

      Fix shift clicking option selecting


      Fix high paint delay settings saving


      Update prayer IDs for the quick select menu


      Remove RS3 support


      Fix hooks



      RS3 Support Removed

      The RS3 client hasn't been updated since our Old-School version of TRiBot was released, as many of you may have noticed. Keeping all of the RS3 code in the client made the client as a whole harder to maintain, larger, slower, and messier. As hardly anyone still uses the RS3 client, and since the RS3 API was hardly functioning, we made the decision to completely remove it from TRiBot.

      For the average user, this means that the client will be smaller, cleaner, and faster. Future updates will also take less work meaning there will be more frequent updates.

      If you were one of the few users still using the RS3 client, we apologize for the inconvenience. No future support for RS3 is planned. There are many other botting clients which has support for RS3, so we recommend finding an alternative if you wish to continue botting on RS3.
        • Thanks
        • Like
      • 25 replies
    • Please welcome our new developers, @JoeDezzy1, @erickho123, @Encoded, and @wastedbro.

      These members will be responsible for working on, maintaining, and improving TRiBot.

      This means that bug fixes and improvements will now come at a much faster pace! We're committed to providing users with the best botting experience possible!
        • Thanks
        • Like
      • 30 replies
    • This release includes:

      More 3rd party libraries for script writers to use


      Apache Commons Codec


      Apache Commons Collections


      Apache Commons Configuration


      Apache Commons IO


      Apache Commons Lang


      Apache Commons Math


      GSON


      Guava


      JFoenix




      Hint arrow API


      Game#getHintArrowX


      Game#getHintArrowY




      Fix player hooks including Player#getSkullIcon and Prayer#getPrayerIcon
        • Thanks
        • Like
      • 49 replies
    • This update includes:

      Fix broken hooks


      Fix login bot for the message "No reply from login server. Please wait 1 minute and try again."


      Fix bug relating to which bot tab is sent human input


      General#randomLong bug fix involving negative numbers


      Fix GE API



      Please note: There are still some issues with the login bot due to a change in the game mechanisms handling the login screen. We're working on a fix and will upload it when ready.
        • Thanks
        • Like
      • 37 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×