Jump to content

Recommended Posts

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.

Java 15

TRiBot 12 moves away from the old and dated Java 8 to the latest version of Java - Java 15!

Benefits to users:

  • Improved performance
  • Script writers can use the latest Java language features
  • Smaller installer size

Gradle Launcher

TRiBot 12 kills the dated TRiBot Loader in favour of using Gradle for version management and release distribution. The login now directly uses our Auth0 integration for better security and reliability.

Benefits to users:

  • Faster updates - it is now much easier and quicker for our developers to publish updates
  • More reliable login flow - no more CloudFlare problems during login
  • More reliable dependency management - we spend more time providing valuable updates and less time managing our dependencies

Note: The TRiBot Installer/Launcher does not keep a Gradle daemon process running for those who are wondering.

Modularization

TRiBot 12 starts our modularization journey. This means we've begun splitting up our codebase into separate modules.

Benefits to users:

  • Faster updates - we can create more frequent, smaller updates because the codebase for each module is smaller
  • Increased reliability - de-coupling of our software components mean bugs will occur less often and will be less complex and therefore easier to fix

FAQ

How do you use Looking Glass with TRiBot 12?
TRiBot 12 only supports launching Looking Glass through the TRiBot client and at this time only supports OpenOSRS (https://openosrs.com/). Make sure you download the .jar version of OpenOSRS and have the GPU plugin disabled. RuneLite support is in the works and is in its final stages of development. OSBuddy does not support Java 15 and is no longer supported unless it is updated.

How do you launch TRiBot 12 from the CLI?
You will need to use TRiBot's gradle launcher (https://gitlab.com/trilez-software/tribot/tribot-gradle-launcher). Currently the README is outdated, so check back again within the next couple of days for updated guidelines on how to use the TRiBot gradle launcher.

A large TRiBot logo appears and nothing happens?
When you first launch TRiBot, all of TRiBot's dependencies must be downloaded. As long as the TRiBot logo is being displayed, TRiBot is working correctly. Wait for the logo to disappear and then the TRiBot login or client should display. The dependencies are cached so this process will be much faster after the first time you launch TRiBot.

My accounts, break profiles, and/or proxies are missing?
You can import your old accounts, break profiles, and proxies using the legacy importer tools under the Tools menu.

Full Changelog

User Interface Changes

  • Add TRiBot Light and TRiBot Dark themes
  • Remove all old themes
  • Lite Mode now uses the system's default styling
  • Remove all outdated or non-functional settings, features, and debugs
  • Add search to Interface explorer
  • Add Settings/VarBits explorer
  • Add item selection state debug
  • Add join discord menu item
  • Display proxy port and break profile in tab information
  • Fix store and VIP links
  • Add args label to script selector
  • Add tools to import old account data, proxies, and break profiles

Internal Client Changes

  • Remove use of SLF4J
  • Store client settings, accounts, proxies, and break profiles as JSON
  • Add basis to breaks (more details below)
  • Update hook finders
  • Add --lgpath and --lgdelay args (launch Looking Glass via CLI)
  • Prevent double clicking when an item or spell is selected
  • Replace non-standard whitespace in character names
  • Check if tile is loaded when calculating if it's on screen
  • Remove real integer calculations from RSGEOffer
  • Remove scripter requirement from Script#setAIAntibanState
  • Add catches for RSItem and RSGroundItem to RSMenuNode#correlatesTo
  • Log unconsumed exceptions to file
  • Fix bank pins starting with 0
  • Prevent IllegalMonitorStateException exceptions from spamming logger
  • Prevent NullPointerException from RSItem#getArea
  • Increase clicking new point hover chance
  • Replace incorrect use of General#sleep with Sleeping#sleep
  • Add retries to world list fetch calls
  • Fix longstanding RSObject ID resolution bug
  • Add local third party jar loading
  • Add remote script loading
  • Add bot's focus handler to the game canvas' focus listener
  • Launch using gradle
  • Add Auth0 and Project Loon login
  • Add Java 15 support
  • Rework CLI and Client Starter to work with gradle
  • Add Looking Glass Java 15 support
  • Update Install4J to use gradle
  • Removed --mem cli arg (change the heap size through gradle)
  • Add automation client
  • Add support for external repo files
  • Fix X11Toolkit class cast exception
  • Fix LG OpenOSRS/RuneLite typing JVM crash

API Additions (View the java docs for usage guidelines)

  • Script#getScriptVersion
  • General#println(Object o, Color foreground)
  • General#println(Object o, Color foreground, Color background)
  • General#getProxyName
  • General#setProxy
  • GameTab#getSwitchPreferrence
  • GameTab#setSwitchPreferrence
  • Login#getLoginTimeout
  • Login#setLoginTimeout
  • Login#getTooManyLoginAttemptsTimeout
  • Login#setTooManyLoginAttemptsTimeout
  • WorldHopper#getWorldHopperTimeout
  • WorldHopper#setWorldHopperTimeout
  • Game#getFps

Break Manager Changes

  • Introduction of Basis, the measurement of time that the break is based off of
  • 3 options: Script Start, Previous Break, System Time
  • Script Start: breaks are based on the time since the script was started
  • Previous Break: breaks are based on the time since the previous break, uses the script start time if no previous breaks have occurred
  • System Time: breaks are based off of your system clock (24 hour format)
  • Script#getNextBreakTime will sometimes return -1 during a break due to next break calculations not occurring until after the current break has finished

Final Notes

Thank go out to @Encoded, @Wastedbro, and @Fluffee for their copious amount of hard work with development. Thanks goes out to @Rileyz for his hard work with marketing.

Download TRiBot 12  and start using it today!

Thank you all for your patience and support in making TRiBot the best it can be!

Edited by Encoded
Add FAQ
  • Like 8
  • Sad 1
Link to post
Share on other sites

I have to say, I am really impressed with Tribot 12 performance. My farm is running way more smooth and CPU/RAM efficient, and while I did enjoy the Tribot 11 sidebar workflow, this has made my life much easier. Thanks again for the hard work, and I can't wait for Tribot X!

Edited by scriptoboy
Link to post
Share on other sites
  • 2 weeks later...
On 10/27/2020 at 8:20 PM, TRiLeZ said:

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.

Java 15

TRiBot 12 moves away from the old and dated Java 8 to the latest version of Java - Java 15!

Benefits to users:

  • Improved performance
  • Script writers can use the latest Java language features
  • Smaller installer size

Gradle Launcher

TRiBot 12 kills the dated TRiBot Loader in favour of using Gradle for version management and release distribution. The login now directly uses our Auth0 integration for better security and reliability.

Benefits to users:

  • Faster updates - it is now much easier and quicker for our developers to publish updates
  • More reliable login flow - no more CloudFlare problems during login
  • More reliable dependency management - we spend more time providing valuable updates and less time managing our dependencies

Note: The TRiBot Installer/Launcher does not keep a Gradle daemon process running for those who are wondering.

Modularization

TRiBot 12 starts our modularization journey. This means we've begun splitting up our codebase into separate modules.

Benefits to users:

  • Faster updates - we can create more frequent, smaller updates because the codebase for each module is smaller
  • Increased reliability - de-coupling of our software components mean bugs will occur less often and will be less complex and therefore easier to fix

FAQ

How do you use Looking Glass with TRiBot 12?
TRiBot 12 only supports launching Looking Glass through the TRiBot client and at this time only supports OpenOSRS (https://openosrs.com/). Make sure you download the .jar version of OpenOSRS and have the GPU plugin disabled. RuneLite support is in the works and is in its final stages of development. OSBuddy does not support Java 15 and is no longer supported unless it is updated.

How do you launch TRiBot 12 from the CLI?
You will need to use TRiBot's gradle launcher (https://gitlab.com/trilez-software/tribot/tribot-gradle-launcher). Currently the README is outdated, so check back again within the next couple of days for updated guidelines on how to use the TRiBot gradle launcher.

A large TRiBot logo appears and nothing happens?
When you first launch TRiBot, all of TRiBot's dependencies must be downloaded. As long as the TRiBot logo is being displayed, TRiBot is working correctly. Wait for the logo to disappear and then the TRiBot login or client should display. The dependencies are cached so this process will be much faster after the first time you launch TRiBot.

My accounts, break profiles, and/or proxies are missing?
You can import your old accounts, break profiles, and proxies using the legacy importer tools under the Tools menu.

Full Changelog

User Interface Changes

  • Add TRiBot Light and TRiBot Dark themes
  • Remove all old themes
  • Lite Mode now uses the system's default styling
  • Remove all outdated or non-functional settings, features, and debugs
  • Add search to Interface explorer
  • Add Settings/VarBits explorer
  • Add item selection state debug
  • Add join discord menu item
  • Display proxy port and break profile in tab information
  • Fix store and VIP links
  • Add args label to script selector
  • Add tools to import old account data, proxies, and break profiles

Internal Client Changes

  • Remove use of SLF4J
  • Store client settings, accounts, proxies, and break profiles as JSON
  • Add basis to breaks (more details below)
  • Update hook finders
  • Add --lgpath and --lgdelay args (launch Looking Glass via CLI)
  • Prevent double clicking when an item or spell is selected
  • Replace non-standard whitespace in character names
  • Check if tile is loaded when calculating if it's on screen
  • Remove real integer calculations from RSGEOffer
  • Remove scripter requirement from Script#setAIAntibanState
  • Add catches for RSItem and RSGroundItem to RSMenuNode#correlatesTo
  • Log unconsumed exceptions to file
  • Fix bank pins starting with 0
  • Prevent IllegalMonitorStateException exceptions from spamming logger
  • Prevent NullPointerException from RSItem#getArea
  • Increase clicking new point hover chance
  • Replace incorrect use of General#sleep with Sleeping#sleep
  • Add retries to world list fetch calls
  • Fix longstanding RSObject ID resolution bug
  • Add local third party jar loading
  • Add remote script loading
  • Add bot's focus handler to the game canvas' focus listener
  • Launch using gradle
  • Add Auth0 and Project Loon login
  • Add Java 15 support
  • Rework CLI and Client Starter to work with gradle
  • Add Looking Glass Java 15 support
  • Update Install4J to use gradle
  • Removed --mem cli arg (change the heap size through gradle)
  • Add automation client
  • Add support for external repo files
  • Fix X11Toolkit class cast exception
  • Fix LG OpenOSRS/RuneLite typing JVM crash

API Additions (View the java docs for usage guidelines)

  • Script#getScriptVersion
  • General#println(Object o, Color foreground)
  • General#println(Object o, Color foreground, Color background)
  • General#getProxyName
  • General#setProxy
  • GameTab#getSwitchPreferrence
  • GameTab#setSwitchPreferrence
  • Login#getLoginTimeout
  • Login#setLoginTimeout
  • Login#getTooManyLoginAttemptsTimeout
  • Login#setTooManyLoginAttemptsTimeout
  • WorldHopper#getWorldHopperTimeout
  • WorldHopper#setWorldHopperTimeout
  • Game#getFps

Break Manager Changes

  • Introduction of Basis, the measurement of time that the break is based off of
  • 3 options: Script Start, Previous Break, System Time
  • Script Start: breaks are based on the time since the script was started
  • Previous Break: breaks are based on the time since the previous break, uses the script start time if no previous breaks have occurred
  • System Time: breaks are based off of your system clock (24 hour format)
  • Script#getNextBreakTime will sometimes return -1 during a break due to next break calculations not occurring until after the current break has finished

Final Notes

Thank go out to @Encoded, @Wastedbro, and @Fluffee for their copious amount of hard work with development. Thanks goes out to @Rileyz for his hard work with marketing.

Download TRiBot 12  and start using it today!

Thank you all for your patience and support in making TRiBot the best it can be!

The latest version of tribot is very slow...

Link to post
Share on other sites
On 10/27/2020 at 9:20 PM, TRiLeZ said:

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.

Java 15

TRiBot 12 moves away from the old and dated Java 8 to the latest version of Java - Java 15!

Benefits to users:

  • Improved performance
  • Script writers can use the latest Java language features
  • Smaller installer size

Gradle Launcher

TRiBot 12 kills the dated TRiBot Loader in favour of using Gradle for version management and release distribution. The login now directly uses our Auth0 integration for better security and reliability.

Benefits to users:

  • Faster updates - it is now much easier and quicker for our developers to publish updates
  • More reliable login flow - no more CloudFlare problems during login
  • More reliable dependency management - we spend more time providing valuable updates and less time managing our dependencies

Note: The TRiBot Installer/Launcher does not keep a Gradle daemon process running for those who are wondering.

Modularization

TRiBot 12 starts our modularization journey. This means we've begun splitting up our codebase into separate modules.

Benefits to users:

  • Faster updates - we can create more frequent, smaller updates because the codebase for each module is smaller
  • Increased reliability - de-coupling of our software components mean bugs will occur less often and will be less complex and therefore easier to fix

FAQ

How do you use Looking Glass with TRiBot 12?
TRiBot 12 only supports launching Looking Glass through the TRiBot client and at this time only supports OpenOSRS (https://openosrs.com/). Make sure you download the .jar version of OpenOSRS and have the GPU plugin disabled. RuneLite support is in the works and is in its final stages of development. OSBuddy does not support Java 15 and is no longer supported unless it is updated.

How do you launch TRiBot 12 from the CLI?
You will need to use TRiBot's gradle launcher (https://gitlab.com/trilez-software/tribot/tribot-gradle-launcher). Currently the README is outdated, so check back again within the next couple of days for updated guidelines on how to use the TRiBot gradle launcher.

A large TRiBot logo appears and nothing happens?
When you first launch TRiBot, all of TRiBot's dependencies must be downloaded. As long as the TRiBot logo is being displayed, TRiBot is working correctly. Wait for the logo to disappear and then the TRiBot login or client should display. The dependencies are cached so this process will be much faster after the first time you launch TRiBot.

My accounts, break profiles, and/or proxies are missing?
You can import your old accounts, break profiles, and proxies using the legacy importer tools under the Tools menu.

Full Changelog

User Interface Changes

  • Add TRiBot Light and TRiBot Dark themes
  • Remove all old themes
  • Lite Mode now uses the system's default styling
  • Remove all outdated or non-functional settings, features, and debugs
  • Add search to Interface explorer
  • Add Settings/VarBits explorer
  • Add item selection state debug
  • Add join discord menu item
  • Display proxy port and break profile in tab information
  • Fix store and VIP links
  • Add args label to script selector
  • Add tools to import old account data, proxies, and break profiles

Internal Client Changes

  • Remove use of SLF4J
  • Store client settings, accounts, proxies, and break profiles as JSON
  • Add basis to breaks (more details below)
  • Update hook finders
  • Add --lgpath and --lgdelay args (launch Looking Glass via CLI)
  • Prevent double clicking when an item or spell is selected
  • Replace non-standard whitespace in character names
  • Check if tile is loaded when calculating if it's on screen
  • Remove real integer calculations from RSGEOffer
  • Remove scripter requirement from Script#setAIAntibanState
  • Add catches for RSItem and RSGroundItem to RSMenuNode#correlatesTo
  • Log unconsumed exceptions to file
  • Fix bank pins starting with 0
  • Prevent IllegalMonitorStateException exceptions from spamming logger
  • Prevent NullPointerException from RSItem#getArea
  • Increase clicking new point hover chance
  • Replace incorrect use of General#sleep with Sleeping#sleep
  • Add retries to world list fetch calls
  • Fix longstanding RSObject ID resolution bug
  • Add local third party jar loading
  • Add remote script loading
  • Add bot's focus handler to the game canvas' focus listener
  • Launch using gradle
  • Add Auth0 and Project Loon login
  • Add Java 15 support
  • Rework CLI and Client Starter to work with gradle
  • Add Looking Glass Java 15 support
  • Update Install4J to use gradle
  • Removed --mem cli arg (change the heap size through gradle)
  • Add automation client
  • Add support for external repo files
  • Fix X11Toolkit class cast exception
  • Fix LG OpenOSRS/RuneLite typing JVM crash

API Additions (View the java docs for usage guidelines)

  • Script#getScriptVersion
  • General#println(Object o, Color foreground)
  • General#println(Object o, Color foreground, Color background)
  • General#getProxyName
  • General#setProxy
  • GameTab#getSwitchPreferrence
  • GameTab#setSwitchPreferrence
  • Login#getLoginTimeout
  • Login#setLoginTimeout
  • Login#getTooManyLoginAttemptsTimeout
  • Login#setTooManyLoginAttemptsTimeout
  • WorldHopper#getWorldHopperTimeout
  • WorldHopper#setWorldHopperTimeout
  • Game#getFps

Break Manager Changes

  • Introduction of Basis, the measurement of time that the break is based off of
  • 3 options: Script Start, Previous Break, System Time
  • Script Start: breaks are based on the time since the script was started
  • Previous Break: breaks are based on the time since the previous break, uses the script start time if no previous breaks have occurred
  • System Time: breaks are based off of your system clock (24 hour format)
  • Script#getNextBreakTime will sometimes return -1 during a break due to next break calculations not occurring until after the current break has finished

Final Notes

Thank go out to @Encoded, @Wastedbro, and @Fluffee for their copious amount of hard work with development. Thanks goes out to @Rileyz for his hard work with marketing.

Download TRiBot 12  and start using it today!

Thank you all for your patience and support in making TRiBot the best it can be!

What happend with the looking glass with OSBuddy ?? i can only use OpenOSRS

Link to post
Share on other sites
  • Encoded unpinned this topic

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

    • We've heard your complaints - the TRiBot API could be much easier to use. We've been dedicating our time to improving the scripter experience here and spent the past year working on a new and improved API - the TRiBot Script SDK.

       

      The TRiBot Script SDK is an easy-to-use library for building TRiBot scripts. It is the recommended approach to building scripts moving forward over the old TRiBot API. It contains all the core things you need to build a script, and a ton of additional helpful stuff to get you using your scripts quicker. See the documentation section for everything offered, and check out the brief overview link too.

       

      The SDK was announced in preview here:

       

      It is now officially released. The official release guarantees we will support backwards compatibility for some period of time. See the 'backwards compatibility' section below for more info.

       

      How to use:

      There is multiple options, listed in the order they are recommended.

      1) Use the gradle template mentioned below

      2) Obtain through gradle

      Add this dependency: api("org.tribot:tribot-script-sdk:+")

      Add this repository: maven("https://gitlab.com/api/v4/projects/20741387/packages/maven")

      3) Take from your local filesystem in your .tribot/install folder. For example, on windows, you'd find it at "C:\Users\[user]\AppData\Roaming\.tribot\install\tribot-client\lib\tribot-script-sdk-[version].jar"

       

      Documentation:

      Java docs: https://runeautomation.com/docs/sdk/javadocs/index.html?overview-summary.html

      Kotlin docs: https://runeautomation.com/docs/sdk/kdocs/index.html

       

      Backwards compatibility:

      We will be following a deprecation schedule whenever we perform a possible breaking change. We will deprecate the respective methods or classes and announce it in a topic. It will remain deprecated for some period of time (weeks or months), and then removed. This will give you time to fix anything, if we need to make a breaking change.

       

      Gradle template:

      Easily build scripts with a new pre-configured scripting gradle template

       

      Users of the current API:

      There is no plans to remove TRiBot API. It will still be available. However, non-critical bugs probably won't be fixed. The SDK does depend on some of the API so fixing some things in the SDK will indirectly fix the API. However, bugs that have existed in the API for awhile will likely not be fixed. It's recommended to use the SDK moving forward. Let us know if there's something the SDK is missing.

       

      Brief overview of the changes:

       

      Bug reports:

      Post bug reports in the bug reports section of the forums

       

       

      Let us know what your thoughts are! If you have questions, feel free to ask below or in discord.

       
        • Like
      • 0 replies
    • Support for the gradle launcher is being dropped. Read more about the new launcher here.
        • Like
      • 8 replies
    • What to expect from TRiBot moving forward.
        • Thanks
        • Like
      • 11 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.
        • Sad
        • Like
      • 40 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.
        • Like
      • 13 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...