Jump to content
TacoManStan

AIO TRiBot Support Thread

Recommended Posts

Describe the problem: When I try to run a "New Client" on the loader, it starts up but crashes and closes out before finishing loading the login screen.

Operating system (Mac OSX, Windows 7, etc): Windows 10

Was it working at an earlier time? (Yes/No): No

What steps have been taken by you/others in an attempt to solve the problem?: Reinstalled both TRiBot and the latest JAVA versions. Changed the JAVA_HOME directory as well.

Additional information (Provide as much as you can):

Share this post


Link to post
Share on other sites
7 minutes ago, tfrye01 said:

Describe the problem: When I try to run a "New Client" on the loader, it starts up but crashes and closes out before finishing loading the login screen.

Operating system (Mac OSX, Windows 7, etc): Windows 10

Was it working at an earlier time? (Yes/No): No

What steps have been taken by you/others in an attempt to solve the problem?: Reinstalled both TRiBot and the latest JAVA versions. Changed the JAVA_HOME directory as well.

Additional information (Provide as much as you can):

Are you trying to load OSRS or RS3?

Share this post


Link to post
Share on other sites
4 minutes ago, iFluffee said:

Sadly, TRiBot no longer actively supports RS3. In the meantime, I encourage you to try out our awesome OldSchool bot, I'm sure you'll enjoy it :)

And as stupid as this may sound, I use Google to sign in on RS3, how can I sign in on OSRS?

Share this post


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

And as stupid as this may sound, I use Google to sign in on RS3, how can I sign in on OSRS?

Honestly? Not a clue. I've always used an email and password to sign in. I would suggest googling it, as I'm sure Jagex has some kind of system in place! :)

Edit: You may need to follow the instructions here , and upgrade to a full RuneScape account. Then use the new credentials to sign in on OSRS!

Edited by iFluffee

Share this post


Link to post
Share on other sites

Describe the problem: Unknown Source

Operating system (Mac OSX, Windows 7, etc): Windows 10

Was it working at an earlier time? (Yes/No): Yes

If yes:

Approximately when was it working last?: 3 days ago

What changed?: upgraded to vip-e

What steps can be taken to replicate the issue?:

Screenshots (if relevant):

Bot/Client debug (if relevant):

Spoiler
  •  
  • [21:38:17] java.net.SocketException: Address family not supported by protocol family: connect
  • [21:38:17] at java.net.DualStackPlainSocketImpl.connect0(Native Method)
  • [21:38:17] at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
  • [21:38:17] at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
  • [21:38:17] at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
  • [21:38:17] at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
  • [21:38:17] at java.net.PlainSocketImpl.connect(Unknown Source)
  • [21:38:17] at java.net.SocksSocketImpl.connect(Unknown Source)
  • [21:38:17] at java.net.Socket.connect(Unknown Source)
  • [21:38:17] at sun.net.NetworkClient.doConnect(Unknown Source)
  • [21:38:17] at sun.net.www.http.HttpClient.openServer(Unknown Source)
  • [21:38:17] at sun.net.www.http.HttpClient.openServer(Unknown Source)
  • [21:38:17] at sun.net.www.http.HttpClient.(Unknown Source)
  • [21:38:17] at sun.net.www.http.HttpClient.New(Unknown Source)
  • [21:38:17] at sun.net.www.http.HttpClient.New(Unknown Source)
  • [21:38:17] at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Unknown Source)
  • [21:38:17] at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(Unknown Source)
  • [21:38:17] at sun.net.www.protocol.http.HttpURLConnection$6.run(Unknown Source)
  • [21:38:17] at sun.net.www.protocol.http.HttpURLConnection$6.run(Unknown Source)
  • [21:38:17] at java.security.AccessController.doPrivileged(Native Method)
  • [21:38:17] at java.security.AccessController.doPrivilegedWithCombiner(Unknown Source)
  • [21:38:17] at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)
  • [21:38:17] at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source)
  • [21:38:17] at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Unknown Source)
  • [21:38:17] at sun.net.www.protocol.http.HttpURLConnection.access$200(Unknown Source)
  • [21:38:17] at sun.net.www.protocol.http.HttpURLConnection$9.run(Unknown Source)
  • [21:38:17] at sun.net.www.protocol.http.HttpURLConnection$9.run(Unknown Source)
  • [21:38:17] at java.security.AccessController.doPrivileged(Native Method)
  • [21:38:17] at java.security.AccessController.doPrivilegedWithCombiner(Unknown Source)
  • [21:38:17] at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
  • [21:38:17] at java.net.HttpURLConnection.getResponseCode(Unknown Source)
  • [21:38:17] at obf.HF.mi(ng:221)
  • [21:38:17] at obf.MJ.xJ(uf:91)
  • [21:38:17] at obf.MJ.(uf:205)
  • [21:38:17] at obf.kJ.Ma(ig:205)
  • [21:38:17] at obf.LK.I(ve:392)
  • [21:38:17] at obf.LK.(ve:87)
  • [21:38:17] at obf.zl.(xf:114)
  • [21:38:17] at obf.kJ.(ig:24)
  • [21:38:17] at obf.Rl.(he:95)
  • [21:38:17] at obf.VH.run(jd:245)
  • [21:38:17] at java.lang.Thread.run(Unknown Source)

What steps have been taken by you/others in an attempt to solve the problem?: reinstall java, delete tribot folder

Additional information (Provide as much as you can)

Share this post


Link to post
Share on other sites

@ryancb596 Here is the apparent solution:

Looks to me like its trying to connect over IPv6 instead of IPv4, reinstalling java might do it, but i think you can also run this from a command line.

setx _JAVA_OPTIONS -Djava.net.preferIPv4Stack=true

if you are unsure where to type that, open Start, type CMD and hit enter. A black box will appear and you can paste the above line by right clicking somewhere and clicking paste. 

Please note: You mention you upgraded to VIP-E, but this is not present on your profile.

Share this post


Link to post
Share on other sites
15 minutes ago, allmaxedplayersbot said:

Hello, I am running the aAgility V2 script and it will run for a few minutes and then end the script for some reason. Any help on solving this issue?

You should post script specific issues on the script's thread.
You'll probably get better/faster support that way.

Check out the bot debug and client debug tags under TRiBot.
And copy/paste the debug into the thread along with your bug report.
 


This thread is more for TRiBot client issues.

Share this post


Link to post
Share on other sites

The Problem

ERROR When I launch Tri-Bot Loader

 Java HotSpot(TM) Client VM warning: Using incremental CMS is deprecated and will likely be removed in a future release

 

When I see this error, the client continues to load. I then click New Client, and the client loads. When I see the runescape login screen, I cant click New User or Existing Account

 

IMPORTANT:  Its important to note that I have successfully run Tri-Bot and ran bots for hours, and sometimes days straight with no problems. Eventually I always encounter this error, and I can no longer login. I have been solving this issue by re-installing the operating system each and every time this happens, however that is time consuming, and there MUST be a better solution :).

 

When does this error occur?

This error randomly occurs (usually once I restart the server/computer)

 

What have I done to attempt to fix this error?

  • Re-Install the operating system (Works)
  • Un-installing & Re-installing Oracle Java

 

My System Information

I am using Linux Ubuntu 12.04 (Un-installed Unity, and bloatware, then installed LXDE core as my desktop environment.

I have Oracle Java (not OpenJDK) installed using the following command

sudo add-apt-repository ppa:webupd8team/java
sudo apt-get update
sudo apt-get install oracle-java8-installer


When I type Java -version I receive the following response

@Server8:~$ java -version
java version "1.8.0_144"
Java(TM) SE Runtime Environment (build 1.8.0_144-b01)
Java HotSpot(TM) Client VM (build 25.144-b01, mixed mode)

 

 

Does anyone have an idea as to why I am receiving this error?

 

Edited by Berner

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Our picks

    • This release will:

      Fix login bot after today's game update (Thanks @JoeDezzy1)


      Fix latest in-game world hopping issues (Thanks @erickho123)


      Compact Settings UI and set location relative to TRiBot (Thanks @JoeDezzy1)


      Fix an older implementation of GrandExchange#getWindowState (Thanks @JoeDezzy1)


      Improve the preformance of NPCChat by only searching in certain interface parents (Thanks @JoeDezzy1)



      Upcoming updates:

      Break handler bug fix


      Improved CLI support


      LG support for RuneLite


      Much more



      Note: If you are using LG, please restart both the RS client and TRiBot
        • Thanks
        • Like
      • 10 replies
    • This release will:

      Fix bytecode manipulation in order to prevent the modification of parameters within the Filter and Condition classes themselves (thanks @wastedbro)


      Fix NPE caused by non-null value in GE API (thanks @erickho123)


      Add and fix equals methods for api2007.types (thanks @JoeDezzy1)


      Modify Mouse#leaveGame to make the mouse leave the game from top, left, right, or bottom (thanks @erickho123)


      Add Entrana area to Ships API (thanks @erickho123)


      Fix raid prayers index/settings in Prayer API (thanks @erickho123)



      Upcoming updates:

      Break handler bug fix


      Improved CLI support


      Much more



      Note: If you are using LG, please restart both the RS client and TRiBot
        • Like
      • 29 replies
    • This update will:

      Implement better canvas locking/synchronization mechanism


      Fix small Login API bug


      Remove the requirement for xbooting Java classes


      Use ExecutorService to perform canvas work in parallel


      Add "Account Management" game tab to GameTab API (thanks @Encoded)


      Fix NPCChat#getMessage (thanks @Encoded )


      Fix NPCChat#selectOption (thanks @Encoded )


      Fix Banking API after today's update (thanks @Encoded )


      Fix in-game world hopper after today's update (thanks @Encoded )



      Upcoming updates:

      Break handler bug fix


      Improved CLI support


      Much more



      Note: If you are using LG, please restart both the RS client and TRiBot
        • Thanks
        • Like
      • 38 replies
    • 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
      • 33 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
  • Recently Browsing   0 members

    No registered users viewing this page.

×