Jump to content

Recommended Posts

As some of you may know, we've been developing a new launcher for a while now. While the Gradle Launcher we introduced last year solved many of the problems with the previous launcher, it introduced quite a few more. Therefore, we set out to do another iteration of the tribot launcher where no corners are cut.

Today I'm announcing a beta release of this launcher that you can use right now if you wish. This will serve as a good alternative to users who have been experiencing issues with the Gradle Launcher as well as those who want to help us as we cross the finish line on the full release. 

Unfortunately, this beta only includes the JAR launcher, which requires java to run. The native installers for this launcher will come soon.

Instructions:

  • Ensure you have Java installed on your machine. Any Java version will work. I recommend this one: AdoptOpenJDK - Open source, prebuilt OpenJDK binaries
    • The new launcher is smart enough to automatically download and use the correct Java for tribot even if you launched it with an incompatible Java version.
  • Download the new Launcher JAR here: Tribot Portable Launcher
  • Execute the new launcher

This launcher supports command line arguments. Simply use the format:

java -jar tribot-splash.jar [args]

to execute the launcher with the desired args. It will detect this and pass them to the tribot client while skipping the launcher GUI. The actual command line arguments are the exact same from the current version of tribot. 


Things left to do before release:

  • Make the launcher GUI look amazing
  • Make the launcher settings save automatically so you don't have to set them each time
  • Add code signing to the native installers which will mark them as trusted software

Notes:

  • Whatever the new launcher downloads/updates will be stored in your .tribot folder under the "install" directory, which includes our software as well as Java versions and stuff.
  • The launcher has automatic self-updating in every regard. You should never have to manually redownload our products. Even this beta release will automatically turn into the full version.
  • If the launcher JAR is executed with Java 15, it will automatically detect it and use it to launch tribot instead of downloading its own.
  • Like 5
  • Thanks 1
Link to post
Share on other sites

The speed of this new launcher is much better than the gradle version

@Nullable however I cannot get any of the CLI args to work? As soon as I specify any arguments to the process it checks/updates dependencies then quits without any output telling me whats wrong

image.thumb.png.e29a235f1147b7fc21132203c839d72f.png

 

Hopefully I am doing something stupid and the fix is obvious, please let me know ;)

Link to post
Share on other sites
1 hour ago, maclof said:

The speed of this new launcher is much better than the gradle version

@Nullable however I cannot get any of the CLI args to work? As soon as I specify any arguments to the process it checks/updates dependencies then quits without any output telling me whats wrong

image.thumb.png.e29a235f1147b7fc21132203c839d72f.png

 

Hopefully I am doing something stupid and the fix is obvious, please let me know ;)

You can use the --fulldebug argument to see the output of tribot itself to see why it's crashing. Go ahead and do that and let me know the output.

Note: you don't want to regularly use that command. It will keep the launcher processes alive.

Link to post
Share on other sites
30 minutes ago, Nullable said:

You can use the --fulldebug argument to see the output of tribot itself to see why it's crashing. Go ahead and do that and let me know the output.

Note: you don't want to regularly use that command. It will keep the launcher processes alive.

It is the --stacktrace and --mem options that cause it not to launch (as below)

I will happily remove --stacktrace if it is no longer supported, but is there a new argument for specifying memory going forwards?

 

 

image.png

Edited by maclof
Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Our picks

    • What to expect from TRiBot moving forward.
      • 10 replies
    • TRiBot 12 Release Candidate

      The TRiBot team has been hard at work creating the last major version of TRiBot before the TRiBot X release. We've noticed many problems with TRiBot 11 with a lot of users preferring TRiBot 10 over 11. We've heard you, so we took TRiBot 10, added the new features introduced with 11, introduced some other new things, and created TRiBot 12. So without further adieu, here's TRiBot 12.
        • Like
      • 39 replies
    • Gradle is a build tool used to accelerate developer productivity.

      We recently setup a Maven repository (TRiBot Central) to make it easier for scripters to create scripts. Check it out here: https://gitlab.com/trilez-software/tribot/tribot-central/-/packages

      Furthermore, we've released a simple Gradle project to make it easy to run TRiBot and develop scripts for it. Check it out here: https://gitlab.com/trilez-software/tribot/tribot-gradle-launcher

      The goals of TRiBot Central are to:

      Deliver updates to TRiBot faster


      Better organize TRiBot's dependencies (AKA dependancies)


      Make it easier to develop scripts for TRiBot


      Make it easier to use and run TRiBot


      Note: TRiBot won't be able to run scripts from within this project until TRiBot's next release.
      • 13 replies
    • Hi everyone,

      I'd like to thank everyone for their patience in this transition period. Since last week, we've worked out the remaining bugs with this integration.

      Some users have still been having issues with connecting their forums account to their Auth0 account. To resolve this, we've imported all forums accounts into Auth0.

      Unfortunately, the accounts which were imported today were using an unsupported password hashing algorithm. Hence, random passwords were set during the import.

      What does this mean for me?

      If you've previously linked your forums account to your Auth0 account, you don't have to do anything. Nothing changes for you.


      If you haven't logged in via our new login yet,

      Try logging in with your forums email address and the last password you used


      If you are unable to login, please use the "Forgot password" tool on the login page:
      Follow the instructions to reset your password
       
      • 17 replies
    • Hello everyone,

      Last week we tried to roll out Auth0 Login, but we lost that battle. Now it's time to win the war!

      Important changes

      When logging into the client, you'll now have to enter your Auth0 account credentials instead of your forums credentials

      Note: 2FA is still handled through your forums account (for the time being)



      Changes for existing users

      You'll have to link your Auth0 account to your forums account here: https://tribot.org/forums/settings/login/?service=11


      Auth0 accounts have been created for most existing users. Please use your forums email address and password to login.



      Important notes

      Make sure to verify your email address upon creating a new Auth0 account


      When we mention your Auth0 account, we mean your account used for auth.tribot.org as displayed below
      • 81 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...