Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
Buy OSRS Gold

Sign in to follow this  
Sidesteppin12

[SNIPPET] Jaywalker's Banking & GE API

Recommended Posts

Posted (edited)

I decided to create my own banking API that mimics tribots way of implementing the API as much as possible. Basically it would only contain nothing more than just method calls. Simple and easy to use.

This API is a reworked version that is currently in my jHerblore script. I intend to release my GE api as well once I have finished that one up too. The API requires DaxWalker & Wastedbro's Item Price API. Other than that the rest is achieveable with standard dependencies that already comes with tribot.

All of the method names are the same as the ones from Banking & GrandExchange class in tribot, with a few exceptions, the only difference is that these methods are called with different class names such as Banker & Exchanger, so they do not collide with the Banking & GrandExchange class of tribot and cause an ambiguity problem.

 

List of available methods:

Spoiler

Banker.openBankBooth()

Banker.openBankBanker()

Banker.openBank()

Banker.openTab()

Banker.close()

Banker.isInBank() - Should only be used after DaxWalking or other types of walking, otherwise use the standard tribot version.

Banker.isBankLoaded()

 

Banker.depositEquipment()

Banker.depositAllExcept(List<Integer> ids)

Banker.depositAllExcept(List<Integer> ids, boolean depositNoted)

Banker.depositAll()

Banker.deposit(int amount, int id)

Banker.deposit(int amount, String name)

 

Banker.withdraw(int amount, int id)

Banker.withdraw(int amount, int id, boolean stackException)

Banker.withdraw(int amount, String name)

Banker.withdraw(int amount, String name, boolean stackException)

Banker.withdrawNoted(int amount, int id)

Banker.withdrawNoted(int amount, int id, boolean stackException)

Banker.withdrawNoted(int amount, String name)

Banker.withdrawNoted(int amount, String name, boolean stackException)

 

Banker.withdrawByIds(int amount, List<Integer> ids)

Banker.withdrawByIds(int amount, List<Integer> ids, boolean stackException)

Banker.withdrawByIds_Noted(int amount, List<Integer> ids)

Banker.withdrawByIds_Noted(int amount, List<Integer> ids, boolean stackException)

Banker.withdrawByNames(int amount, List<String> names)

Banker.withdrawByNames(int amount, List<String> names, boolean stackException)

Banker.withdrawByNames_Noted(int amount, List<String> names)

Banker.withdrawByNames_Noted(int amount, List<String> names, boolean stackException)

 

Banker.walktToBank()

Banker.walkToBank(WalkingCondition condition)

Banker.walkToBank(RunescapeBank bank)

Banker.walkToBank(Runescape bank, WalkingCondition condition)

 

Walker.walkTo(Positionable positionable)

Walker.walkTo(Positionable positionable, WalkingCondition condition)

 

Exchanger.withdrawGP(int amount)

Exchanger.open()

Exchanger.close()

 

Exchanger.buy(List<Integer> ids, int amount, float multiplier)

Exchanger.buy(int id, int price, int amount, float multiplier)

Exchanger.buy(int id, int price, int amount)

Exchanger.sell(int id, int price, int amount, float multiplier)

Exchanger.sell(int id, int price, int amount)

 

Exchanger.collectBuy(int id, int amount, int timeToWait)

Exchanger.collectBuy(int id, int amount, int timeToWait, boolean trackProfit)

Exchanger.collectSell(int id, int amount, int timeToWait)

Exchanger.collectSell(int id, int amount, int timeToWait, boolean trackProfit)

 

Exchanger.clickOffer(int id, int amount, TYPE type)

Exchanger.getCompleted(int timeToWait)

Exchanger.clickSearchTarget(String item)

 

Some of the features this API offers:

- Methods that incorporate any form of withdrawing or depositing do not need you to first check if the bank is open nor if it is loaded. It will attempt to open the bank if it is not open before returning false, and wait for bank to load if it is not loaded yet.

- Methods that incorporate any form of buying or selling do not need you to first check if the exchange window is open. It will attempt to open the exchange window if it is not open before returning false.

- Deselector. All methods that require the mouse to click somewhere on the screen first check if an item or spell is selected, if it is then it will deselect whatever is selected before attempting the requested action.

- Additional failsafes, not just the deselector. Tribots banking api does not know if what you were trying to click actually was succesfully clicked. Instead it views succesfully calling the click function as a succesfull attempt. It's kind of like playing pin the nail to the donkey game. It does not know if it pinned it at the right location, but as long as it pinned it the function returns true. This is not true for all methods, some methods do actually check if the action was succesfully performed, however they do not reattempt the action if it failed. 1 call = 1 attempt. My api will reattempt any action that might fail, several times, before returning false and will also wait until inventory count is updated. For example using the tribot banking API if you were to deposit all your items and then immediately check your available inventory space before withdrawing items then it might not work as you wish because Banker.depositAll() returns before the action of depositing has finished.

- When banking, closes GrandExchange window if it is open.

- When buying/selling, closes the bank screen if it is open.

- Support for withdrawing items in noted format and with or without stack exception. Stack exception is basically if you wish to draw X amount of items in your inventory but you only had Y left, then you can choose if you wish to draw these items or not. Also supports depositing of noted item ids if you happen to pass a list with of items that contains items of unnoted item ids, but the item in your inventory is a noted version of the item in your inventory. Also will not deposit equipment or items if you have none equipped or in your inventory. There is a total of 4 different depositing methods and 16 different withdrawing methods.

- Unique dynamic sleeping method, all methods that should sleep already have sleeps implemented so you do not need to call a sleep after executing any of the methods. Involves random varying sleeps but will occasionally, every so often, in a irregular pattern, sleep a bit longer. I use this because I prefer it over General.sleep(). Feel free to replace it with whichever method you wish. Remember before running the main loop in your script to call:

jGeneral.get().generateSeed();

This will create a random number between 0-100 that will be added to your dynamic sleeps in milliseconds. This is so no bot has the same average reaction/sleeping time.

- When buying items on the GE, if the bot does not have any money or too little money in the inventory, it will check if you have enough of the missing amount in the bank and withdraw that amount.

- Custom buying method that checks for an exact string match of the item you wish to buy and chooses that one from the returned items in the buy window search box. The standard GE api does not do this and will for instance click the wrong herb when it searches for "Guam leaf" in the grand exhcange, this is because more than one item contains "guam leaf" in their name. Such as Grimy guam leaf and so on.

- Profit tracking when buying/selling items on the GE. This is optional.

 

GET THE SOURCE HERE!

 

UPDATES:

- Pushed new updates that fix some of the methods that I've tested a bit for now, bit of logic and efficiency improvements. Also added 2 new depositing methods. Remember to replace the old java files with the new ones.

- Pushed even more updates. Fixed interface problem for withdrawing noted items. My GE api is now also been released to the public. Enjoy! :)

Edited by Sidesteppin12

Share this post


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.

Sign in to follow this  

  • Similar Content

    • By sslippi
      I want to start by saying I'm new to programming.
       
      I'm trying to make a basic script that completes Druidic Ritual. I'm trying to withdraw all of the quest items and teleports needed with Banking.withdraw().
       
      Like this:
      Banking.withdraw(0, 2138, 2136, 2132, 2134, 8007, 3853); I'm wanting to avoid adding a static wait just so I can get good practice with implementing anti-ban. How would I go about making this method not spam click the items when trying to withdraw them?
    • By dax
      Click the spoiler for more progress reports!
       
       
       
      Posting a BUG REPORT
      Please read this and submit the report here.
      You can buy Credits with RSGP instantly here!
    • By ScriptsForMains
      https://tribot.org/repository/script/id/3461
      Start the script in the area you want to gather resources. Follow the prompts in the pop-up boxes and type exactly what's needed (pay attention to caps!!).  Uses ABC2 timing and custom antiban.  Lots of safety features (will log out if unsuccessful at banking, if experience hasn't been gained, if it can't click on its target, etc etc).  

      Supports mining, woodcutting, fishing, thieving (with coin pouches!!), and some hunter animals (can't remember which ones, it's been forever since I've used it for hunter :P).  I recommend using low ABC2 reductions for slower things (fishing or high level resources) and higher ABC2 reductions for stuff like power mining.  For slower things, this will make you move the mouse a lot less when waiting for your character to stop doing something and is much more realistic.  For faster things, you'll be standing around a lot less and getting more exp.  

      Uses Daxwalker to bank...  Right now I'm just using public keys so if it's not working it's likely because Daxwalker is busy.  
      It can also power level.  Just tell it what to drop!!

      Used this to get my stats up to Drag slayer 2 requirements...  Simple program but very effective.  

       


      Troubleshooting:
      If you run into any problems with the default file, delete it (it's in the AppData -> Roaming -> .tribot folder) 
    • By fl0shizzle
      Hey guys.
      Trying to accept an incoming trade but whenever I try to get the chatBox interface it's always null? It's definitely visible on the screen?
      My code is simply (where CHAT_PARENT is 137):
       
      When I use the following code to see if the interface is there, its not shown:
      Any ideas?
       
       
    • By NeuroGenix
      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.
      Exchange Class
      GEInterfaces Class
      GEConditions Class
      InfoHelper Class
      Thank you to everyone that has read this far, it is appreciated
      Rewritten, if you have read again, even more appreciation!
    • By drunksigma
      I get nothing as output even though my bank  is open.
      @Override public void run() { while(true) { sleep(200); RSItem itemarray[] = Banking.getAll(); for(RSItem index : itemarray) { General.println(index.name + " ID: " + index.getID() + " Stack: " + index.getStack()); } }  
    • By Flamo353
      Description:
      I thought some new scripters might find this useful. So I rewrote @TehRhio's old shop api since it's #getAll method was outdated.

      Original Thread:
      Snippet:
      import org.tribot.api.Timing; import org.tribot.api.types.generic.Condition; import org.tribot.api2007.Interfaces; import org.tribot.api2007.Inventory; import org.tribot.api2007.types.RSInterfaceChild; import org.tribot.api2007.types.RSInterfaceComponent; import org.tribot.api2007.types.RSItem; import org.tribot.api2007.types.RSItemDefinition; import java.awt.*; import java.util.ArrayList; import java.util.Arrays; public class OSShopping { private static final int MASTER_ID = 300; private static final int FRAME_CHILD_ID = 1; private static final int ITEMS_CHILD_ID = 2; public static boolean isShopOpen() { return Interfaces.get(MASTER_ID, ITEMS_CHILD_ID) != null; } public static String getShopName() { RSInterfaceChild frame = Interfaces.get(MASTER_ID, FRAME_CHILD_ID); if (frame != null) { return frame.getText(); } return ""; } public static boolean close() { RSInterfaceChild frame = Interfaces.get(MASTER_ID, FRAME_CHILD_ID); if (frame != null) { RSInterfaceComponent closeButton = frame.getChild(11); return closeButton != null && closeButton.click("Close") && Timing.waitCondition(new Condition() { @Override public boolean active() { return !isShopOpen(); } }, 2000); } return false; } public static RSItem[] getAll() { ArrayList<RSItem> itemList = new ArrayList<>(); RSInterfaceChild itemsChild = Interfaces.get(MASTER_ID, ITEMS_CHILD_ID); if (itemsChild != null && itemsChild.getChildren() != null) { for (int i = 0; i < itemsChild.getChildren().length; i++) { RSInterfaceComponent itemComponent = itemsChild.getChild(i); if (itemComponent != null && !itemComponent.isHidden()) { final int garbageLength = 11; String name = itemComponent.getComponentName(); Rectangle bounds = itemComponent.getAbsoluteBounds(); if (name != null && name.length() >= garbageLength && bounds != null) { RSItem item = new RSItem(name.substring(garbageLength).replace("</col", ""), itemComponent.getActions(), itemComponent.getIndex(), itemComponent.getComponentItem(), itemComponent.getComponentStack(), RSItem.TYPE.OTHER); item.setArea(bounds); itemList.add(item); } } } } return itemList.toArray(new RSItem[itemList.size()]); } public static boolean contains(String... names) { return get(names).length > 0; } public static boolean contains(int... ids) { return get(ids).length > 0; } public static RSItem[] get(String... names) { ArrayList<RSItem> items = new ArrayList<>(); for (RSItem i : getAll()) { RSItemDefinition definition = i.getDefinition(); if(definition != null && Arrays.asList(names).contains(definition.getName())) { items.add(i); } } return items.toArray(new RSItem[items.size()]); } public static RSItem[] get(int... ids) { ArrayList<RSItem> items = new ArrayList<>(); for (RSItem i : getAll()) { if(Arrays.asList(ids).contains(i.getID())) { items.add(i); } } return items.toArray(new RSItem[items.size()]); } public static int getCount(String... name) { int total = 0; for (RSItem item : get(name)) { total += item.getStack(); } return total; } public static int getCount(int... id) { int total = 0; for (RSItem item : get(id)) { total += item.getStack(); } return total; } public static boolean buy(int amount, String name) { RSItem[] items = get(name); RSItem item = items.length > 0 ? items[0] : null; return item != null && item.getStack() > 0 && exchangeItem(amount, "Buy", item); } public static boolean buy(int amount, int id) { RSItem[] items = get(id); RSItem item = items.length > 0 ? items[0] : null; return item != null && item.getStack() > 0 && exchangeItem(amount, "Buy", item); } public static boolean sell(int count, String name) { RSItem[] items = Inventory.find(name); return items.length > 0 && exchangeItem(count, "Sell", items[0]); } public static boolean sell(int count, int id) { RSItem[] items = Inventory.find(id); return items.length > 0 && exchangeItem(count, "Sell", items[0]); } private static boolean exchangeItem(int amount, String action, RSItem item) { if (amount >= 50 && action.equals("Sell")) { return item.click(action + " 50"); } else if (amount >= 10) { return item.click(action + " 10"); } else if(amount >= 5) { return item.click(action + " 5"); } else { return item.click(action + " 1"); } } }  
    • By AliveInMe
      Many beginners fail to understand how to navigate API's. Today I am going to show you how to navigate and understand TRiBots documentation.
      I. Open TRiBots API by following this link: https://tribot.org/doc/
      Your main screen should look like so:

      Don't be alarmed it's actually pretty easy to follow! I will begin by discussing the three main sections of our current screen.
      II. 3 Section main API page
      a) The API Packages: 

      Here is where you can find select classes per package and then broaden your search for a specific class in that package.
      *Helpful for import finding!*
      For the next screenshot, I clicked on org.tribot.api .
       
      b ) Here is where we can search a specific class available from all of the combined packages the API documents has to offer.

      Selecting a class will introduce the methods and descriptions associated with them.
      c) Finally, Here is the overview panel where we can use the navigation bar to our liking and also see class documentation! 

      You can search the Class Hierarchy, Deprecated Methods, Index, and Help section!
      Importance of the Index section
      The Index contains an alphabetic list of all classes, interfaces, constructors, methods, and fields. Which is helpful for searching a specific method in the API documentation!
      For this GIF example, I select the Index section and followed the alphabetical list to search for the getHealthPercent() method.
      https://i.imgur.com/JxnRL5p.gif
      III. Part A: Class Documentation

      For the following information, I will select the class RSNPC   from the classes section shown in  II. b .
      Your overview panel should now show the RSNPC class documentation as follows

       
      This is the classes name and associated package.
       
      This is the classes implemented interfaces *If applicable*.
      Implementing the methods that allow us to get the RSNPC#RSTile, and RSNPC#Click methods.
       
      This shows the classes that it extends 
      Allowing us to use the methods associated with RSCharacter .  Some classes also show the description of the class as shown here .
       
      II. Part B: Class documentation Method Summary
      Scrolling down will show us the Method Summary .

       
      This section shows us the Method & Description and the return types each method returns.
      1st column = data type of the method
      2nd column = Method and Description of that method
       
      Clicking on any of those methods it will bring you down to a more in-depth explanation of the method.
      For this picture example I chose RSNPC#getDefinition()

      Marked in RED is the Name
      Marked in GREEN is the  DataType, Method Name, and Possible parameters a method could have
      Marked in BLUE is the description of the method.
      Marked in YELLOW is the return type of the method.
       
       
      I hope my tutorial helped some of you. If a topic needs a better explanation, please feel free to address it to me in the comment section.
      Thank you,
      AliveInMe
    • Guest
      By Guest
      Hi,
      Does anyone have an API for the Grand Exchange they don't mind sharing with me, or giving me a few pointers on creating one myself, as the current TRiBot API seems to be having some issues with Interface IDs
  • Our picks

    • 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
      • 9 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
       
        • thonking
        • Like
      • 15 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
    • To better support the upcoming changes (TRiBot X, new repository), we're switching our login handler to Auth0. Instead of logging in with the standard form, you'll now be required to login through our Auth0 application.

      All existing accounts which have been used within approximately the past year have been imported into Auth0 using the same email and password combination which has been stored on the forums.

      What does this mean for users?

      Your account credentials are now even more securely stored


      You'll be able to login via Facebook, Google, and others in the future


      Is there anything users have to do differently now?

      Existing users: You'll have to login with the standard login, open your Account Settings, then link your Auth0 account


      New users: You'll be redirected to our Auth0 app (auth.tribot.org) where you'll be able to create an account


      Why was this change made?

      The new apps we are creating (such as the new repository) aren't able to use the forums to handle user logins


      To centralize all user accounts in one area


      To ensure that the client login doesn't go down when the forums are having problems


      To speed up our development


      Other considerations

      There's no documentation or official support for using Invision Community combined with Auth0, so there are still a few kinks we're working out


      We're in the works of creating an account management panel specifically for Auth0 accounts (ETA August)


      It's not possible to change email addresses for the time being (this will be resolved this August)


      Changing passwords is a weird process for the time being. To change your password, you'll have to use the "Don't remember your password" tool on the Auth0 login page
        • Like
      • 11 replies
    • Over the past month, we've been working hard on TRiBot's new repository - a much needed update. This change has been deemed necessary for TRiBot X, and will allow us to really speed up development of all aspects of TRiBot.

      Today we are going to share what we've been working on!


      Now you must be wondering what kind of features the new repository will have.... well, you'll have to be patient for a little while longer. We're still figuring out various technical aspects so we can't provide answers to all possible questions. We're also focusing on development rather than writing about it so that everyone can get access to our latest developments at lightning speed. I will however answer a few users' questions.

      We're planning on a release of this early to mid August, giving users some goodies before TRiBot X's release.

      Thank you all for being patient. I hope everyone is excited as much as I am!
        • Like
      • 17 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...