Post rewritten after rewritting and updating the code multiple times.
So I decided to give writing my own GE API a go and this is what I've come up with so far, using Exchange#offer(name, price, quantity, buy) will do the following:
If the GE is closed, it will open it and continue making the offer. If the price is set to -1 then it will use the buttons to increase or decrease the price, depending on whether it is a buy or sell offer, until it is at a price that will buy/sell instantly. Otherwise it will use the custom input button to set the price. It will set the quantity using the 1/10/100/1000 buttons. I plan on updating this to randomise between using them and the custom input method shortly. Edit* I hadn't even remembered implementing this until I saw it do it whilst testing the method, and it was beautiful, but if it goes over the buy quantity accidently, in the example I saw it was clicking +100 and clicked it again too fast so instead of stopping before its target of 875 it got to 900, it will then use the custom amount interface to input 875, beautiful. It will prioritise buy offers over sell offers so that if there isn't an empty slot available, or any items to collect, then it will cancel a sell offer, collect it and continue now it has a free slot. If there isn't a free slot available and we are trying to sell something it will return true, this is so that in my scripts it will remove the item from a toSell HashMap and put it back into the bank to sell later because it has bought the items it needs to continue botting. If it is instead trying to buy something and there are no empty slots or sell offers to cancel then it will wait for something to buy and continue once it can collect something and therefore has an empty slot. Update* It will now search for the item 1-3 words at a time checking the first 9 results each time and will choose the item as soon as it is visible as a human would. I might update this so that it randomises more, sometimes entering the whole first word of an items name straight away, because I sometimes do that, most of the time though I enter as few characters as I need to, I think, thoughts? Let me know what you think, the code is probably disgusting to look at for some of you but for others just starting out like me it could be a valuable learning tool, for how not to code All feedback and constructive criticism appreciated.
Thank you to everyone that has read this far, it is appreciated
Rewritten, if you have read again, even more appreciation!
I've written my first, I would say for now basic script for combat training.
One of the main reasons why I chose to use Tribot is because of abc2. But while reading the post on the tutorial on how to implement it in your own code (
) I didn't really understand the method(the way) on how to implement it in code.
Could anyone please send me a personal message with an explanation on how to implement it correctly, or write a reply here.
It would be very nice, if you would include an actual code example of it, that would help me to understand it better.
Thank you in advance.
The script is currently Free/Open Access to all Non-VIP and VIP users.
If you'd like to support me, you can go ahead give me a :thonking: emoji.
- Supports both Molten glass and Soft Leather( Leather).
- Will automatically switch to the next best glass/leather item upon level-up
- Clicks on the closest item to the needle/blowpipe instead of the same item every single time.
Get the Latest Version: Here
Think you've found a bug? I'll happily fix it as long as you say more than "skript broke plz fix".
This script is aimed to bank-standing skills such as Fletching, Crafting, Herblore or Cooking.
It comes with a task-based system that you can set up to train with different items and even multiple skills in one go.
You can create or load from a previously saved file multiple tasks to be executed by order.
A task is complete once you reach the desired amount or level.
A task can also be unfinished if you don't supply enough items for its completion or if you don't meet the required level to execute it.
The rules for script argument are the following:
1. Each task is separated by a vertical bar, "|"
2. Each task setting has an associated key and value, "key=value"
3. Each task setting is separated by a comma, ","
4. Option settings follow the same rules as task settings
5. Not case-sensitive
Available task settings:
skill - the skill you are training with this task. This setting can be ignored if task doesn't give experience in any skill
item - item's amount and name separated by a space. The first and second items will be used on each other. The last item must be the product. E.g. 1000 cookies.
master_interface_id - set master interface id. This setting can be ignored if there isn't any interface after you combine first with second item
child_interface_id - set child interface id. This setting can be ignored if there isn't any interface after you combine first with second item
component_interface_id - set component interface id. This setting can be ignored if there isn't any interface after you combine first with second item
amount - the amount to combine on the task. If this setting is not present, or a number of zero or lower is set, the amount is ignored.
stop_level - the stop level that interrupts the task. If this is not present, or a number of zero or lower is set, the stop level is ignored. Also, this only works if you input a valid skill on "skill" setting
inventory_timeout - the inventory timeout for this task. Value is in miliseconds
Available option settings:
mouse_speed - indicates the average mouse speed to use
save_on_system_update - when set to true, attempts to save the task progress on a .dat file right before an ingame update. The task can then be reloaded on gui
antiban_reaction - enables with value "true" or disables with value "false" the antiban reaction sleep after an inventory has finished
antiban_debug - to print anti-ban actions debug on bot debug panel. "true" to enable, "false" to disable
close_with_esc_button - to use escape keyboard button to close the bank. "true" to enable, "false" to disable
auto_bank_walking - to walk to the nearest bank whenever the player is not on a bank. "true" to enable, "false" to disable
auto_ge_walking - to walk to grand exchange before starting a task. "true" to enable, "false" to disable
disable_mouse_offscreen - disables feature mouse offscreen from antiban to increase efficiency when combining some items
skill=herblore, item=14 avantoe potion (unf), item=14 mort myre fungus, item=14 super energy(3), master_interface_id=270, child_interface_id=14, amount=5000, stop_level=75, inventory_timeout=20000 |
skill=crafting, item=1 needle, item=26 leather, item=10000 thread, item=26 leather gloves, master_interface_id=154, child_interface_id=93, amount=100, inventory_timeout=50000 |
mouse_speed=110, save_on_system_update=true, antiban_reaction=false, antiban_debug=true, close_with_esc_button=true, auto_ge_walking=true
Note: The last item must be the product produced by combining the first and second items.
Exact non case sensitive names are a must.
You must press enter or click on a empty row to set the last row's value on the table.
The setup above has four tasks:
1st. Using a Knife on a Maple logs to produce 27 Maple longbow (u) per inventory. Ends after 500 Maple longbow (u) are made, or a supply is missing from bank.
2nd. Using a Bow string on Maple longbow (u) to produce 14 Maple longbow per inventory. Ends after 500 Maple longbow are made or a supply is missing from bank.
3rd. Using Jug of water on Pot of flour to produce 9 Pizza base per inventory. Ends after 10000 Pizza base are made, or a supply is missing from bank.
4th. Using a Needle on Leathers to produce 26 Leather boots per inventory. Ends after 1000 Leather boots are made, or a supply is missing from bank.
18 April 2017 - Ability to combine two items with same name.
Ability to bypass "make interface" by setting master or child interface id to -1 value.
27 May 2017 - Ability to combine items that require going through a selection interface and then an amount interface.
02 July 2017 - Added script argument.
20 November 2017 - Updated the script to support the new interfaces.
Script argument changed.
06 February 2018 - Changed the script to support more than 2 items on inventory. This will allow the combination of a greater variety of items.
23 April 2018 - Added option to enable/disable auto bank walking and grand exchange bank walking.
Added option to enable/disable mouse offscreen when idling.
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.
Skull icon fix
Improve screen rate and responsiveness of the RS client (both regular client and LG)
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
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.
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!
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
Hint arrow API
Fix player hooks including Player#getSkullIcon and Prayer#getPrayerIcon
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.
Recently Browsing 0 members
No registered users viewing this page.