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

Sell OSRS Gold

Leaderboard


Popular Content

Showing content with the highest reputation on 09/07/2018 in all areas

  1. 5 points
    Pie's ArdyCloak Does all steps needed to unlock Ardougne cloak 1 and completes the quests that are required for it! (Plague city, Biohazard, Rune mysteries). Will buy all the items needed off the GE if none of the quests have been started/completed and no progress has been made in the Ardougne diary. Repository link: https://tribot.org/repository/script/id/2919 Features: Does all steps required for easy Ardougne diary. Completes quests if needed for some of the steps. Buys item off the GE if account are fresh-ish. Requirements: 5 thieving Rusty sword Some GP in the bank or items listed below Items needed (if there is progress in the diary/quests, will buy items off GE itself if no progress has been made) (items purchase off GE support at any point of progress will probably be added later on): Diary: Plague city: Biohazard: Rune mysteries: If you have all the required items, just run it and watch it go!
  2. 2 points
    Just pushed an update All bows, cross bows, ammo types are now supported
  3. 2 points
    It does, but the connection will be tunneled through the specified proxy after TRiBot hooks onto the regular client. Don't login into the game before this happens, as the client is originally started on your computer's IP address. Read more here:
  4. 1 point
    Catches (almost) any fish, (almost) anywhere. Universal Fisher is a free fishing script with minimalist design and basic functionality. It's very easy to use and the GUI can be configured within seconds. Features: Anti-Ban Compliance v2 fully implemented Support for different fishing techniques Bank or Drop the fish Custom area: constructed around the player at start-up Run-time information displayed in the paint How to use: Have the required fishing equipment in the inventory Start the script in the desired fishing area Enjoy!
  5. 1 point
    This tutorial will teach you how to use an IDEs debugging to utilize break points to debug your TRiBot scripts. This tutorial will only show how to do it with Intellij, but that same thing should apply to other IDEs. Setting up Intellij to run TRiBot 1. We must set up the project dependencies. You can get here by using Ctrl+Alt+Shift+S or going to File -> Project Structure Once you are here, click on Modules and select the dependencies tab. Debugging Tribot requires you add the following files to your dependencies. To add a dependency, click on the green + next to Scope and click JARs or directories. tools.jar You can find this in your jdk directory. Example: C:\Program Files (x86)\Java\jdk1.8.0_101\lib substance.jar You can find this in your %AppData% Tribot location. Example: C:\Users\Your User\AppData\Romaing\.tribot\dependancies trident.jar You can find this in your %AppData% Tribot location. Example: C:\Users\Your User\AppData\Romaing\.tribot\dependancies bin You can find this in your %AppData% Tribot location. Example: C:\Users\Your User\AppData\Romaing\.tribot\bin 2. We must setup a new Run/Debug Configuration. You can get here by going to Run -> Edit configurations Once you are here, create a new Application configuration by clicking on the green + and clicking Application. The new configuration will be created and we must edit the settings now. I named my configuration Tribot. Main class: org.tribot.TRiBot VM options: -Xmx386m -Xss2m -Dsun.java2d.noddraw=true -XX:CompileThreshold=1500 -Xincgc -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -Xbootclasspath/p:"C:\Users\Spencer\AppData\Roaming\.tribot\dependancies\xboot860.jar" -classpath "C:\Program Files (x86)\Java\jdk1.8.0_101\lib\tools.jar";"C:\Users\Spencer\AppData\Roaming\.tribot\bin";"C:\Users\Spencer\AppData\Roaming\.tribot\dependancies\substance.jar";"C:\Users\Spencer\AppData\Roaming\.tribot\dependancies\trident.jar";"C:\Users\Spencer\AppData\Roaming\.tribot\dependancies\TRiBot.jar"; Make sure to switch out the directories to what they are on your computer. Program arguments: TRIBOTSESSIONID MEM384 OLDSCHOOL Replace TRIBOTSESSIONID with your session id. You can find this in %AppData%\.tribot\settings\startup.ini PLEASE NOTE: if your session id does not start with SID, add it to it. Example: ccaa-das9fg87ad9fg7a98df7ga98df7g2aead32kjhhj13k You should place: SIDccaa-das9fg87ad9fg7a98df7ga98df7g2aead32kjhhj13k Hit apply and you are ready to go. Using breakpoints to debug your script. Breakpoints are extremely useful for debugging your program. They allow you to stop the program during runtime and see what is happening. Lets use this simple script as an example. I'm having an issue. Even though I'm near the Oak Trees my script is not clicking the Cut option. We can debug this by adding a break point and stepping through the script. To add a breakpoint, you click on the empty area next to the line numbers which will place a red circle. This red circle is a break point. While debugging, any time your script hits said circle, the script will stop and you will be able to interact with it. Now that I have a break point setup, its time to debug it. We can launch the TRiBot client by going to the Run menu and clicking Run -> Debug 'Tribot'. If this option is not available, you can click Run -> Debug... and select the correct configuration. Once your client has loaded, you can run the script you are debugging. When a breakpoint is triggered, your script will pause and options will be available within the IDE. A blue line represents the current line you are debugging. You will notice that your client has frozen while you are interacting with a break point. To prevent this, right click on your break point and change Suspend All to Suspend Thread. Now when you encounter a break point, your client will no longer freeze but you can debug the script. Now about the real problem. Why isn't my script clicking Cut on the oak tree?!?! Well we have a few options here. We can use some nice features down at the bottom in the debugger. will rerun the program. This will close your current client and open a new one. will continue the program until it encounters the next break point. will stop the program, ending your tribot client. will "step over". This will run the line of code and go to the next one. It will not go into any method calls. will "step into". This will run run the line of code, stepping into any method calls that are made. The reason debugging is extremely useful is you can see in real time what each line of code is doing. In this program, we can "step over" all of our lines, and see the line 17 will gathers all Oak trees in our area. If there is more than 0 Oak trees in the array, it will attempt to click the Cut option on the first one. By repeatedly clicking step over, we can see what happens. Now why can't it cut the tree?? Lets "step over" so we are on the trees[0].click line. If we right click we can see an option that is Evaluate Expression. Click it, or press Alt-F8. This will bring up a new window that looks like this. This allows us to run code that doesn't even exist in the script!!! Lets try running trees[0] and pressing Evaluate. We will see some stuff that doesn't really make sense, but at least we know that there is a tree that we can click on. By typing a . on that line, intellisense will prompt us with valid things we can type. Lets look into the objects definition. We can do this by typing trees[0].getDefinition() Well, that brings up some more values that don't really make sense for us. By looking at the Tribot API or even typing another . to see what are valid things we can type we can see that trees[0].getDefinition().getActions() is valid. Lets try that. Hmm, it tells us that Chop down and hidden are valid options for interacting with this tree. I think I found my issue. Cut is not valid and Chop down is. By evaluating this, the result is true, and in the TRiBot client, the bot successfully clicked on the tree!! This is just a small introduction on what you can do with debugging. For more information on what you can do while debugging, consider consulting google.com.
  6. 1 point
    The mouse speed is determined by ABC2 and I don't intend to change its behavior. The time it feeds the kitten is every 13 to 18 minutes. Since the script doesn't know the last time the kitten was fed, it feeds it on script start.
  7. 1 point
    Nice release! That sounds very useful
  8. 1 point
    all u got to do is right click the tab at the top and set ur proxy
  9. 1 point
    Looks like I won't have the rewrite out tonight. It's about 98% finished. Just need to fix a couple minor bugs still.
  10. 1 point
    In the Tribot Client go to File -> Settings -> General Settings And at the very bottom there should be a checkbox called "Enable Tribot firewall" If its check marked try Unchecking and and running the script again
  11. 1 point
    Would be useful if the Tribot client enabled the user to toggle different anti-ban features. This way the user could customise it towards their legitimate play style. I am noticing that some new premium scripts are giving their users control over the anti-ban settings, which to me is a step in the right direction.
  12. 1 point
    Wow you actually finally decided to do something useful.
×
×
  • Create New...