hello people, robots and other species
since a couple of days i run into the problem that, somehow, when any bot at all goes to Draynor Village using the AoG teleport.
the bot just stands there like a idiot who forgot where he wanted to go...
it looks like its because the bots cant find the coordinates to click on or something...
is anyone else experiencing this? and how do i fix this
As many lines as you want to autotalk (will scroll down indefinitely) Custom time interval delay ABCL 10 Auto Accept Trades Alert with a popup window the accepted trade (perfect for leaving the bot running and doing something else, while it talks and accepts trades. It will then alert you a trade has been established, and you can take over).
Make sure to select the Trade tab when logged in:
Click to add:
I'm a gold reseller across many games mostly using ebay and EpicNPC. I'm mainly looking to forge partnerships with reliable and trustworthy suppliers.
Here's my profile, if you need any proof that it's me then feel free to message that account on EpicNPC or the Skype/Discord linked to it:
You can contact me at:
I don't check my messages here much, it's more lurking that I do here so please message me on the above for quickest replies.
I am using exBuyer and when the bot is hopping worlds, sometimes it hops too fast and gets kicked out and sent to the log in screen. The bot then makes no attempt to try to log back in even though I set up my account on the account manager and I selected my account when I started the script. I also tried selecting the Auto-Relog option but that did not work either. I cannot get Tribot to log me back in whatsoever so if anybody has any idea on how to fix this, that would be really awesome. Thanks for the help.
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"
Java docs: https://runeautomation.com/docs/sdk/javadocs/index.html?overview-summary.html
Kotlin docs: https://runeautomation.com/docs/sdk/kdocs/index.html
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.
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:
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.
Support for the gradle launcher is being dropped. Read more about the new launcher here.
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.
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.
Recently Browsing 0 members
No registered users viewing this page.