Jump to content


Popular Content

Showing most liked content since 11/21/2016 in all areas

  1. 27 points
    The OSRS client had an overhaul of how the game canvas is displayed a few revisions ago. This caused some technical problems with TRiBot, primarily because our client is 100% reflection based and we can't use the simple "canvas hack" like injection bots can. This resulted in me having to redesign the system which renders TRiBot's game image and overlay painting. That is the reason for the delay in getting this update out. I thank everyone for their patience. Summary: Fixed the flicker bug Minor improvement in efficiency / CPU usage Fixed the "null source" bug
  2. 21 points
    a serious video message for @TRiLeZ TRileZ please come back, sunshine! TRileZ don't be so lazy! TRileZ hire more developers! TRileZ mod Butta! Behind the scene:
  3. 19 points
    This release features: Looking Glass fix. LG is not affected by the flickering issue like the regular client is. Performance improvements to the regular client which came about with the latest update to the RS client. Fix for the login bot where it wouldn't recognize an incorrect username or password has been entered. The regular client still suffers from the flickering issue. Fixing this is now my top priority.
  4. 19 points
    This update includes: Fix to destination hooks Updated world list in the world hopper Banking API bug fix Combat API bug fix Magic API bug fix Compensation for the downtime over the past few days as well as the downtime earlier this year is being applied to all current VIP(E) members and members whose VIP(E) expired during the downtime earlier this year. The extension is going to be one month. A new thread will be made announcing the compensation after it has been processed. Please keep all unrelated comments/questions off this thread.
  5. 18 points
    Fixed clicking/uptext/choose option bugs Fixed minimap clicking bug Updated the world hopper
  6. 17 points
    This release contains: Fixed the login bot for the Lava screen. Thanks go to Todd. Added some additional cases for the login bot's message handling system. Small improvement tot he World Hopper thanks to Todd. Looking Glass has nearly been fixed, but we're still working on perfecting the fix to prevent potential problems experienced by users. A fix to the flickering issue will be released shortly after.
  7. 15 points
    Source over at GitHub Example: Debug Paint: Api-Access How to use Api-Key WebWalker.setApiKey(apiKey, secretKey); My web walker will always be free, and the engine will always be open sourced. However, I currently pay 79 per month keeping my computation server up to be able to support Tribot's huge user base. Pathfinding algorithms aren't exactly light on the CPU. I've spent 200+ on the open beta keeping servers up for the past 3 months (40 + 79 + 79). I will try my best to keep the engine updated but I cannot guarantee I will be available to do so. Overtime, there will be more documentation on my walker engine. Feel free to create your own git branches and add features to my walker. If you profit from making scripts and use my webwalker, please consider buying yourself an api key. The public key will hit its call limit if everyone uses it. Funds go towards server costs and development time. Keep in mind that you are paying for the computational server + client-server communication, not the engine which is completely open sourced. Server will be up 99% of the time. I've managed to keep a total downtime of <30 minutes the past 3 months. Contact me right after you bought an api key! 400 Call Limit (~6.6 calls per second) resets every minute Free! - Already Included in source 1000 Call Limit (~16.6 calls per second) resets every minute $20.00/month 3000 Call Limit (~50 calls per second) resets every minute $40.00/month Not a developer? Support my project through Patreon! Public key limit will be raised once I hit the goal! All patrons have access to a developers key.
  8. 15 points
    The latest update seemed to have not broken any hooks from a quick glance, but Jagex has changed the way the graphics are produced which broke some major areas of the client. I've implemented a temporary patch for the non-LG client. The game may flicker every once in a while, but it should work just fine. I'm still working on fixing LG. Since TRiBot is a pure reflection client, we face more obstacles than other injection-based bots. LG should have a patch released within the next few hours. The regular client should have a permanent fix released in the next week or two, but this permanent fix will really only fix the flickering issue. Edit: It turns out there have been multiple hooks which are not working. I've fixed a few of them, but there are also a few more that need fixing. I'll continue working on them tomorrow. Edit2: The broken hooks have been fixed. The regular client is now back in working order. LG is still out of commission and is expected to be fixed later tonight. Edit from Todd: Since this is a temporary patch we are aware there are certain users that will still be having issues. If you are still have issues feel free to leave a comment below in the following format. Operating System: Java Version: Issue I'm Having: What Script I'm trying to use:
  9. 15 points
    Brief overview of what @TRiLeZ said over at the tribot discord chat. There might be an announcement later, but expect a fix to broken hooks soon.
  10. 13 points
    Fluffee's Tutorial Island • Completes Tutorial Island • Supports loading of bulk accounts • Script Argument/Queue/Client Starter support • Tons of customization options • Random account profiling • Full ABC2 support • Post tutorial island tasks • Account Creation • Task based, chose the options for every account Get it here! GUI Instructions Script Arguments Script arguments must be entered as follows (with the following keys): accountPath:;friendsChat:;location:;items:;shiftDropping:;toggleRoofs:; An example script arguments setup can be found below, as well as an explanation of each key. For loading accounts, do not include this line. accountPath:/accounts.txt;friendsChat:Mod_Mark;location:1;items:1;shiftDropping:1;toggleRoofs:1; For creating accounts, do not include this line. emailUsername:[S5][S5][N1];emailDomain:pokemail.net;rsUsername:FTI-SameUsername.;password:PASSWORD;captchaKey:2CAPTCHAKEY;numberOfAccounts:2;noTutorial:true; Script argument explanation: Source
  11. 13 points
    Looking Glass is fixed.
  12. 13 points
    Fluffee's Server Setup 2.0 [BETA] As some of you may know, I released an automated server setup script a little over a year ago. Albeit that script worked well, I was never fully satisfied with it, as I found it to be kind of messy to use. As a result, I rewrote the script, and restructured it, to add more, and stronger support for the different versions of Debian, the different versions of CentOS and the different versions of Ubuntu. However, with so many different Operating Systems being supported, and many different server providers having different setups, it's hard for me to test every possible scenario on my own. Which is why I've been privately handing this script out, and am now publicly looking for help. What does the script do? Similar to my previous setup script, this script changes the SSH port and creates a new user for connecting and using the server and disables root SSH connections; it installs the latest version of TightVNC Server (1.3.10) and sets that up with the desired port and password. It installs JDK 102 (32 or 64 bit depending on the OS), and installs TRiBot and OSBuddy and sets up the appropriate .jar file associations. What operating systems does it support? - CentOS (6.x and 7.x) (32 and 64 bit) - Debian (7.x and 8.x) (32 and 64 bit) - Ubuntu (12.x, 14.x and 16.x) (32 and 64 bit) Does it work? As far as I know, yes it does in fact work, and it works well if I might add. However, given that I can't test every possible setup, there is the potential for differences and issues, which is why I need help. I want to beta test, how can I help? The next time you setup a server, or if you just want to reinstall your old one, use this new script and let me know if you encounter any issues or things that you think are missing. Ideally, after you answer the questions the script prompts you for, you shouldn't have to touch the keyboard again. Therefore, if during installation the script prompts you for any kind of input that isn't the first few questions, please let me know as this is probably not supposed to happen. Also, if things don't work, like TRiBot doesn't open, there's no internet browser, LG won't hook, etc. make me aware of those issues as well, so I can try and fix them! I've found a bug, what do you need from me? A few things, I'll need the operating system and bit type and a description of the bug. I may ask you for SSH access to the server, as well as ask you to reinstall the server a few times, while I attempt to troubleshoot the issue. The issues may only arise on your server, so I might not be able to recreate the issue on my end, as my hosting provider may have a different server setup than your's. I've added in a bug report format below which would be the best way to report a bug, but simply shooting me a PM or messaging me on Skype also work, assuming you're willing to allow me to troubleshoot. How do I run the script? Login as root to a fresh VPS/dedi running one of the supported operating systems. From there run the commands listed below and follow the onscreen instructions. For those who would like to see the script's code, it can be found on my github here. The commands to run are as follows: wget --no-check-cert https://raw.githubusercontent.com/iFluffee/Fluffees-Server-Setup/master/fluffees-server-setup.sh && chmod +x fluffees-server-setup.sh && ./fluffees-server-setup.sh Version History
  13. 12 points
    Compensation for the downtime over the past few days as well as the downtime earlier this year has been applied to all current VIP(E) members and members whose VIP(E) expired during the downtime earlier this year. The extension was one month.
  14. 11 points
    Thread needs to be updated. Basic overview: - ABCv2 - Preset locations - Custom locations - Mouse Key Dropping - Shift Dropping - Bird Nest support - Progressive mode (and axe upgrading) coming soon Become a patreon and help support my scripts!
  15. 11 points
    pls trilez god savior of osrs, producer of mobile bot maybe pls fix so i can eat. real hungry no money 4 food. ty also take long myb compensation? idk wuld b cool
  16. 11 points
    Model grabbing code is now back up to full speed Fixed some client lagging issues Added some RS world IPs to the firewall exclusion list
  17. 11 points
    So here's a dev update as far as I understand it. Runescape updated their client to regularly destroy the canvas of the game screen. This is what causes the flickering effect in some botting clients right now. They also added a request focus for the window, which is also causing some API problems. Looking glass is special in the sense that we have to emulate lots of 'canvas accessories' on both sides. Which is going to be much harder now that the canvas is literally being destroyed every few seconds. We have a plan of attack it just requires time and energy to make sure that everything is 100% human like. What's the point of LG if we shortcut it and make it easily detectable. This will be the only update till probably Wednesday night. Compensation is being discussed i'll have an update for that too.
  18. 11 points
    kidding lol... the owner of this website has a shit computer?? 10 likes and im giving my credits away to a random person
  19. 11 points
    Say it out loud. This may help you understand.
  20. 10 points
    50 hours and 2 gallons of coffee later... How does this script work? Randomly sets a target level between 20 and 30 for the gathering skills and between 5 and 8 for the combat skills. The "processing" skills (cooking, smithing etc.) are trained using the gathered resources (ores, logs etc.), until the raw materials are depleted. The skills are trained randomly. Has a random chance of switching to something completely different. Despite the randomness, certain rules are followed in order to train effectively (e.g. it can only train cooking after we are done fishing. However, after fishing is done, there is no guarantee that it will start cooking or it will go mining etc.). Skills supported now: Starting the script: The only item required, at the time of writing, is a hammer. (You can buy it from the general store.) This will be changed in a later version and the hammer will be automatically purchased. Start the script anywhere, it will automatically gather all the items it needs to complete all tasks. Please do not supply the bot with higher tiers tools, as it currently only supports bronze. (This will be changed soon.) What not to suggest / not bugs: Change the Draynor fishing spot! - No. Even with the occasional deaths caused by the dark wizards, the Draynor fishing spot remains the best place for fishing. An efficient combat fail-safe has been implemented, but even if the bot dies, it only takes ~ 55 seconds to get back from Lumbridge to the fishing spot. Fixed set of levels instead of random-picked targets - No. Thousands of accounts with the exact same levels may not be the best idea, given the heuristic nature of bot detection. Walking is broken! - This script uses webwalking, which is controlled 100% by the client. How does the script work (under the hood) : First of all, I would like to thank @wastedbro for the fair warning. He was 100% right. If you don't have a solid framework, the code becomes ... least to say unmanageable. I guess that's why I had to change the framework 3 times before finally deciding to go with this one. The script uses some variation of @Worthy's node framework (Check out this cool tutorial). However, instead of using the if statement, it uses while so the script will be able to do a task (e.g. fishing) until it hits the target level or until the script randomly switches tasks. The framework is explained in the image bellow. Alternatively, you can check out the source code (link). The actual source code will be released after the testing phase is over, so me and @Cypher can start our spaghetti contest, to see who is the worst scripter. Important notes about the current version! At the moment the script is in testing phase. Bugs are expected. Please report them on this thread. Do not use any valuable account. Combat temporary disabled. An adequate anti-ban will be added as soon as the testing phase ends. Start with a hammer in bank / inventory. - will soon be changed I await your bug reports and suggestions.
  21. 10 points
    I've recently received a PM from a user asking for scripting advice. His code made me contemplate suicide. I'm writing this tutorial in an attempt to prevent this from happening again in the future. Einstein's Scripting Tutorial This tutorial covers the basics and it's aimed at users with very little / no knowledge on this subject. Knowing some basic Java will definitely help, but is not required. After reading this tutorial, you will be able to write your own basic Tribot scripts. Let's get started! What exactly is a script? According to Wikipedia, scripts are "programs written for a special run-time environment that automate the execution of tasks that could alternatively be executed one-by-one by a human operator". Sounds familiar? In our case, the special run-time environment is the Tribot client. Needless to say, scripts written for Tribot will not work outside it. Executing a .class file from your desktop will have no effect. You need to start a Tribot instance and feed it a script in order get things working. So you can view scripts as a set of instructions that you want your bots to execute. Instructions such as: go to bank kill a goblin move the camera chop down a tree Adding rules to the instructions will allow them to be executed when needed, for example: go to bank if the inventory is full kill a goblin if my player is not in combat etc. Let's take a step back New programmers get very quickly overwhelmed by the avalanche of new symbols, keywords, { } [ ] ( ) ; : ... -> ( ͡° ͜ʖ ͡°) (ok, the last one is not part of the Java syntax) Be aware of this pitfall and don't get stuck. Any kind of software, as complex and cryptic as it may seem at first, it's really just a set of instructions. In order to understand how simple programming really is, let's take a step back and abstract Tribot/Runescape. Consider the following script that you probably ran today IRL, without even being aware of it. The comments (green) are ignored by the compiler, I included them just to make matters more clear. ("!" - means "NOT" ) Writing a script that will be executed by Tribot A. The setup: Steps 2 to 5 will be repeated every time you write a new script. Step 1 will only be repeated if Eclipse tries to hack you. 1. Download any Java IDE. If you need a tutorial for this, maybe you should find another hobby. 2. Create new project, the name is irrelevant. 3. Go to Java Built Path (depends on IDE) > add extrenal JAR > navigate to .tribot\dependancies > add "TRiBot.jar" 4. Create a new package called scripts (lowercase 's'). 5. Create a new class, again the name is irrelevant. If your setup looks like this, then you are ready to move on. B. The Actual coding: Now that you finished the setup, you are finally ready to start coding. Simply make your class extend Script (uppercase S). This will generate two different errors. 1. Just use the IDE's auto import shortcut, if you are using Eclipse, it's Ctrl + Shift + O. 2. Click the error warning > "Add unimplemented methods" Things should look like this at this point. The run() method will be called automatically when you press in the Tribot client. The instructions contained within the run() method will be executed in sequence, from top to bottom. If all the instructions are executed, the script will stop. In order to make the script continuously run until we manually stop it, we must add an infinite loop. That's all. Now the only thing you have to do in order to make this script useful, is to add instructions and set rules for them. Refer to the Tribot API for a complete list of instructions. https://tribot.org/doc/ Running the script Your IDE will automatically compile the .java files into .class files. Navigate to your workspace (the location of your project) and copy the .class files. Paste them in C:\Users\User\AppData\Roaming\.tribot\bin\scripts. If you packaged the script correctly, it will appear in the script list when you press . Note: By declaring a script manifest (see below), you will be able to define a custom script category, such as "Testing", "Goldfarming", "Trading" etc. Actual script example I never imagined that I would actually publish this. If I remember correctly, this is my first script. I've modified a few things for simplicity's sake and I've commented every line of code. Note: This modified version is not tested. Edit: Code will soon be modified. Line 51: The null check is not necessary, as potato[0] is guaranteed to be non-null Why did I named the potato-gathering method abuse? Null Pointer Exception / Array Index Out of Bounds Exception Anyway, I think the commented code is self explanatory. The only lines that I would like to further explain are: Edit: Code will be added soon. Thanks @Assume. Two of the most common exceptions you must be aware of while scripting are Null Pointer Exception and Array Index Out of Bounds Exception. They are both runtime exceptions and refer to a very similar thing (NPE: the reference variable points to nothing; index: you are trying to access a non existing index). The idea is that you cannot perform actions upon something that doesn't exist. Consider the following table. If you give a human the instruction "Give me the apple on the table". He/she will tell you that there is no apple on the table. (probably) Give a Java program the same instruction, and it will "tell" you the exact same thing in a form of a thrown exception, a printed stack trace followed by the program's termination. Tips Learn Java before getting into scripting. Read the whole API a few times: https://tribot.org/doc/ The only way to become proficient at this is by practicing. Solve problems as simple and as natural as possible. Don't over-complicate things. Methods should only do one thing. Try to keep them under 30 lines of code. Any kind of non-trivial script requires a framework. Avoid using static variables. Read open source scripts. Write scripts because because you enjoy doing it. Have fun; experiment with code. The end Thank you for reading my basic scripting tutorial and I hope you learned something from it. If you need any help with your scripts, or you just want to harass someone, feel free to send me a PM.
  22. 10 points
    9.305_7: Added new world IPs to the firewall Fixed the bug where the updating process was taking a lot longer than usual Fixed the message listening bug 9.305_8: Updated the world hopper to add the new worlds Fixed a bug in the world hopper where it would occasionally enter PvP worlds
  23. 10 points
    Looking glass able to be repaired? Was said to be fixed that night, I am patient, just wondering when I can be expected to be back at it.
  24. 10 points
    I'm currently fixing an issue where our client painting isn't working anymore since Jagex changes the way the graphics are produced. This shouldn't take long.
  25. 10 points
    With the money he makes here, he should have a few max spec PCs.... lol........
  26. 9 points
    Today I will showcase a new project I've been working on for a while now. This thread is intended for developmental suggestions and questions. There is a free beta available, to check it out, join the Discord server linked at the bottom of this post. =========================================================================== LAN Bot Manager - the next revolution in bot farming. Adds muling support to ANY script available on the repository. Automatically replace accounts that are banned. From an account that has never logged in to money on your mule with one click. Create a progressive mode for any script. Run any number of scripts after each other and quit when you want them to. In short, LAN Bot Manager will run in the background and is capable of starting and stopping other scripts from the repository, it can then decide to pause the script and take back control to do anything it wants. This creates endless possibilities for you and your bot farm. Compatible with ANY script that is available on the repository. Compatible with local & private scripts. Compatible with premium script trials. Proxies and breaking support. It manages your farm so you don't have to. Proxy per account: 'attach' a proxy to an account, so that it will always use that proxy when botting. Pick which accounts do what, for example: you can have 10 accounts on fishing, 25 on mining and 4 on woodcutting, etc. Easily scalable: settings are uploaded to the cloud so adding another server to your farm is as easy as installing TRiBot. No matter what an account does, only a single mule is needed. (but you can add more!) This script is useful from just 1 account to thousands. No external downloads, just activate this script like any other. Data is fetched from the TRiBot account manager, it's easy, recognizable and secure. Client starter support! Boot up your entire farm with one click. The only thing you have to do is add accounts and tell them where to bot! Note: if the script you want to use has a GUI, script argument support is required. Check the script thread or contact the author of the script if you are not sure. This script was designed with the GUI at its core, everything else was built around it to ensure that it is all set up as user friendly as possible. Below you can see some screenshot of how the gui looks. Currently working on: Planned features (after beta): FAQ I don't understand, what does this script do exactly? How do i get this? How much will this script cost? Will this script work with <script name>? How do i know if a script has argument support? How does it select which account it will run? Can i force a different account to be ran? What happens if one of my accounts is banned? How does muling work? Where do i have to park my mule? Can i use this script without muling? GUI Screenshot [ Script is still in development, some things are subject to change ] Feel free to express your thoughts/concerns/suggestions and whatnot below! Join this Discord server to join the BETA, keep track of updates or ask any questions
  27. 9 points
    Updated world hopper Improved CPU usage Improved long-term memory usage Removal of Bot Panel integration TRiBot Bot Control Panel is being shutdown This feature is hardly used and keeping it running requires too many resources. We have decided that the best decision is to reallocate our resources in a way which benefits TRiBot users the most. We plan to re-introduce the Bot Control Panel sometime next year, being better optimized to use less resources, and to provide more working features. But this is low priority. We apologize for any troubles this may cause to the few people whom still use the bot control panel.
  28. 9 points
    http://encodedscripting.com/ Auto Wintertodt Pro subdues the Wintertodt located on Zeah for profitable firemaking experience. This is a dangerous activity. Do not bot with any items you are not willing to lose! Requirements: - 50+ Firemaking Recommended: - 21+ Woodcutting w/ Mithril axe if fletching - 41+ Woodcutting w/ Rune axe if not fletching Current Options: - Fletching - Lighting Brazier - Fixing Brazier - Idling at 500 Points Braziers Supported: - South West - South East Food Supported: - Any item with the "Eat" option, including cakes. - Wine - Saradomin brews if using item id. ABC2 ABCL 10 Dragon axe special attack supported. Purchase: 6 credits/month for 3 instances. 90 minute monthly trial; try it before you buy it! Note: Instances are the amount of accounts that can be ran simultaneously. Click here to purchase. Progress Reports: Dynamic Signatures: Usage Guidelines: Have roofs disabled and camera at max zoom. Food name must be the exact name when inputting it in the GUI. Must have all required items at script start: - Axe equipped or in inventory. - Tinderbox in inventory. - Knife in inventory (only if fletching). - Hammer in inventory (only if fixing brazier). Client freezing when starting the script? Add wintertodt.encodedscripting.com and to TRiBot's firewall always allow. Script Support: https://discord.gg/FDnMbkU
  29. 9 points
    - WHOMEVER scripter or random botter wanting to help assist the scripters with bug trial error runs to test out the script & get this Slayer Bot fully functioning! - I have a team of scripters and testers in the beginning of a project preparing all jets to dish out a Slayer script for the Tribot community! We will need some casual botters & scripters with the passion and optimism to carry this community to greater lengths and overcome many obstacles Jagex puts in our way! I love this community and want to help assist the scripting/botting world behind RSOS. I wont ramble on too much, i just wanted to see if there is anyone to reach out to who are also interested in a working slayer script. Join the xSlayer Script Discord server if you are interested in assisting the project ↓↓↓ by clicking the discord button below ↓↓↓ ⇓⇓⇓⇓⇓ EDIT / CURRENT UPDATES ; 04/07/2017 - I Have successfully gathered a group of individuals including scripters & testers working together in a discord server on a project to create a fully functional SLAYER script in RSOS. __________________________________ 10/07/2017 - The team and i have acquired almost every monster/slayer NPC in game, ready to implement the data. __________________________________ 05/10/2017 - Aquired many more enthusiastic scripters to the team in assisting to make this script very possible! There is progress. __________________________________ Whoever wants a working SLAYER script LIKE THIS post
  30. 9 points
    If you didn't a pea sized brain you would understand its not an issue of money, its how companies work when they have downtime, get off the forums if you're just gonna sit on here and reply making fun of genuine questions. Nobody here probably cares about 80 cents, thats besides the point.
  31. 9 points
    Lord of the Bots: The Return of the King
  32. 9 points
    Update: Compensation has been given, this thread will now be closed. Please refer to the compensation thread located here: As you know, we have recently experienced some downtime, first completely then partially. However, TRiBot is now up and running and you should have no problems going forward. Both LG and the normal client should be working without any issues. If you continue to experience an issue with a particular script then please message that script-writer to test it themselves, they can then open a bug report. Additionally, there are a few topics I would like to address that have been brought up to me in the last few weeks. 1. Compensation We are looking into compensating users for the down-time. This task involves our developers working full time to distinguish proper compensation. This hasn't been possible with the issues with the client. Our priority has always been client first. This will be addressed within the next week or so assuming there are no additional technical issues. 2. Communication There have been quite a few threads mocking the communication between the staff and users of TRiBot. In this, we would like to promote a compromise to our users under the following guidelines. Do not expect your voice to be heard in the unofficial TRiBot discord. Under no circumstances are moderators/admins expected to visit or take complaints/issues in this manner. Please post in the issues forum if you would like us to see the issue. During downtime, we will now be doing daily updates. This update may be a long technical explanation or just a short explanation with an update of the time/date. I will also be starting a new section on updates called 'TRiLeZ Upbeat', which will literally just be direct posts from TRiLeZ that are interesting or informational This has been the biggest break in the TRiBot updater in the past 7 years. Comparatively if you take our average up time we still decimate other bots. First and forth most we are a community and we don't want to lose anybody. We have some cool stuff planned coming soon for TRiBot and we hope you stick around to see it. TRiLeZ Upbeat
  33. 9 points
    First basic computer problems (aka being lazy), and now chronic health issues caused by tribot. Maybe it's time to think about selling tribot or contracting out the development work. Tribot's biggest problem is the lackluster approach of the developers. Tribot could solve 99.9% of its problems if it was treated like a product instead of a hobby.
  34. 9 points
    Go send out some resumes first.
  35. 9 points
    Dude, is that seriously the only thing you can think about? Get a job man
  36. 9 points
    If you right click the account you want to trade there should be an option called "Trade with" good luck!
  37. 8 points
    I decided to stop harassing users, and do something more productive instead. (Hi @Morty123 ) F2P progressive lobsters https://tribot.org/repository/script/id/2503 Does exactly what it says on the tin: trains effectively until it gets lvl 40, then switches to lobsters. It's similar to other progressive fishing scripts, but it has a nice function that makes the setup much easier (explained bellow). How to use this script: Create a new account/ run a tutorial solver. Note: If you want to transfer the lobsters before the 18 hours of in-game time, use a quester to get 7QP. Run the script, then log in your "main" and trade 10k gold to the bot. All trades/ windows will be automatically accepted. Done! From this point on, everything else is automated! Buying fishing equipment... 1-20 fishing... 20-40 fishing... 40+ fishing: Lobsters You can easily transfer the lobsters to your main using Naton's nMule. Didn't test it myself, but based on the feedback on its thread, I think it works really well. (Good job @Naton) Thanks: @fmtrick - I used some bits of code from your feather buyer for the shop part, because I was too lazy to write it myself. If the equipment buying is not working properly, you are the one to blame. @godspower33 - atm the lobster price is hard-coded into the script (lol). On the next update I will use the getPrice(int) method from your Gods_Man_Killer. @auryzas242 - I am still waiting for MY MONEY!! @deva - A huge thank you for the multiple bug reports and suggestions both in this thread and via PM! F2P progressive lobsters - updated to version 2! Fishing in Lumbridge & the combat problem The bot used to get bullied by goblins, spiders or even ducks. This often resulted in deaths and equipment loss. A proper fail-safe has been implemented. More space, more lobsters, more profit The script used to hold the IDs of the fishing equipment in a fixed array. This worked fine, but the users demanded more efficiency. Now the IDs are held in a dynamic list that modifies upon leveling up. The bot drops the equipment that is no longer needed. The auto-buying part has also been rewritten, so it won't buy things that it doesn't need. Inventory at level 40 fishing: The "report-player interface" bug Has been patched. The bot will no longer get stuck if the interface is accidentally opened. Activate the script: https://tribot.org/repository/script/id/2503 User submitted proggies:
  38. 8 points
    Let's make a tutorial on how to not get banned. Age of Account Holder Jagex has stated in their youtube videos/live streams that they look at the age of the account holder to determine how many hours a human of said age would likely to be playing the game. A person below 18 years old is likely to be in school between 8am and 3am. A person between 18 and 22 might be in university/college for many hours each day. On top of school hours, students have to spend their hours doing homework. Jagex knows this fact, and looks at the age of account holders and how often the account is played on. Botting many over weekdays may sway Jagex to think you are a botter if you give them a young age.If the age of the account holder (given to Jagex at account registration) is an age which a person is likely to be in school, do not bot during school hours, and limit the amount of hours botted during weekdays. I'd recommend giving Jagex an age of between 24 and 40 to lessen the chance of Jagex suspecting you of botting.Character Clothes Don't use the default character clothes upon creating your account. Make sure to switch the clothes up. Other players are more likely to report you for being a bot because you look like a common bot.Level 3s Please level up your combat level to at least 10. Level 3 accounts are usually bots. Players are likely to suspect you are botting if your account is level 3, and they will report you.Avoid Botting Long Hours As stated by Jagex, most legitimate players don't play for long hours. Don't bot more than 8-10 hours a day, unless you don't care about your account.Use Breaks Most humans don't have the attention span to play hours without a break. Use TRiBot's break handler, giving your account a break every once in a while.Switch Up Activities Don't bot the same skill/activity every day. Switch up the scripts you use. Try using a woodcutting script for a few hours one day, then switch to a mining script for the remaining hours of the day. The next day, maybe try using a mining script again, then go and use a combat script. Most real players don't do the same skill/activity for days on end. Switch it up.Avoid Changes in Playing Patterns If your account is used solely for botting, and not for playing, then don't play on your account. You personally will have a different playing pattern than TRiBot. Jagex might look at this difference in playing patterns, and could bring upon suspicion that your account is a bot.Try using scripts from the same author. Individual script writers usually have specific ways of handling actions. Scripts by different authors might display different playing patterns.Make sure the same mouse speed is being used in all of the scripts you use.Avoid Scripts with Bugs Scripts with bugs in them can cause your account to be trapped in an endless loop of doing something which looks bot-like. Example: If the account gets stuck outside of the Lumbridge chicken coop and it tries to attack chickens which are in the coop for hours, it will look like a bot. It will keep trying to kill the chickens even though it can't reach it. A human would be smart enough to know to open the coop door to fight the chickens.If the script you are running wasn't developed by an established script writer, then baby-sit your bot to ensure that the script doesn't have any bugs in it. If it does have bugs, you can either use a different script, or baby-sit the bot at all times when running the script.Use Scripts with a High ABCL TRiBot generates unique characteristics for every different botter. These characteristics will hold data such as if the botter should hover the next object/npc, if the botter should go to the next anticipated object/npc location if waiting for an object/npc to spawn, wait times for switching objects/npcs, how often to check XP, and more! By assigning unique characteristics for every different botter, TRiBot will be able to make your character seem different from all of the other botters, thus making it more human-like.If the script has a high ABCL (such as 8-10), then the script implements most, if not all of the unique characteristics available to the bot. Without these More info about ABC/ABCL here:https://tribot.org/forums/topic/31289-anti-ban-compliance/https://tribot.org/forums/topic/31289-anti-ban-compliance/?p=385153https://tribot.org/forums/topic/31969-guide-to-implementing-anti-ban-compliance/Avoid Botting in Areas Filled With Other Bots Try to bot where no other bots are. For one, Jagex calculates playing pattern heuristics. They will compare the heuristics of each player to the other players in the area. If a group of players in the same area all have the same heuristics, Jagex will conclude they are all bots and ban them all. Note: This is what ABC/ABCL was made to combat. ABC/ABCL assigns unique characteristics to every different bot, thus giving them different playing pattern heuristics, which combats Jagex's bot finding methods.Another reason why you should avoid botting in areas filled with other bots is that players are likely to notice a ton of bots, get angered, and report them all. A Note about Bans Delayed Bans Jagex uses delayed bans as a method to prevent script/bot makers from discovering just what is causing their bot to get banned. These delays in bans can be anywhere from a one day delay, to a six month delay.That being said, do not blame the last script or bot you used. Your ban was likely to be caused by a script/bot you used a while ago.Ban Upon Login Sometimes instead of banning an account straight away for botting, Jagex will issue a ban which won't activate until you login to the client. With that being said, don't blame the bot client and say it is detectable. Your ban has been waiting for you, and it just wasn't issued to you until you logged in.IP Flagging If your account gets banned for botting, Jagex will likely flag your IP, and will monitor the accounts which are linked to that IP. If you get banned, try to reset your IP and create a new account on that new IP.Some proxy/corporate IPs are also flagged, so watch out.Avoiding IP Flagging Some users like to avoid IP flagging by using proxies, but many of them still link their account to their main IP.If you are using a proxy to avoid IP flagging, you must create the account while using the proxy. If you create the account with your main IP, but only bot using a proxy, your main IP is still under threat. If you create 10 accounts using your main IP, but bot on them using 10 different proxies, a ban one one account could lead to a ban on the 9 other accounts because they are all linked by the account creation IP.If you are using a proxy, you should also never login to the RuneScape website (or client) using your main IP. If you do, your account will be associated with your main IP.Accounts Which You Don't Even Bot on are Under the Flame As stated by Jagex, if you are caught botting on one account, all of your other accounts may be banned for botting. It doesn't matter whether your other accounts were actually botted on. Be careful.A Note about "Client Detection" Some users claim TRiBot is detectable. However, they are wrong. Users have to keep in mind that I can read the client's code, and I do. With every RuneScape update, I check the client's code for any method which can be used to detect botting clients. So far, no code is being used to detect/search for TRiBot.
  39. 8 points
    Hello, everyone. Recently I've been interested in how Jagex's pattern detection works. I ran a simple easily detected script which opens the GE, buys 1 lobster at 100 GP, waits 30 seconds, then cancels the offer and closes the GE on a loop with tribot's AI antiban turned off. After a few minutes of runtime some abnormal things started happening. Most commonly my input to the game was blocked, meaning I could move my mouse around, but the game server never accepted my input, and as a result my account's actions had no effect on the game world. I've been able to semi-reliably recreate this scenario multiple times on different accounts and IP addresses. It's worth noting that players and NPCs continue their normal action while my account's been frozen, which also indicates no connection errors. The input blockage happens fairly often to the point that it's very unlikely it has anything to do with my network connection or Jagex servers. I believe this is Jagex's first line of defense against bots (or at least one of them). Real players will typically try to perform various actions in-game like arranging inventory, clicking on random tiles or objects, world hopping, and even restarting the client. Bots may repeatedly click the same action (big red flag) or do nothing (moderate red flag) I have no doubt that botters/scripters with more experience than me have noticed this, but this is not a thread about Jagex input blocking, it's about preventing it from happening through pattern breaking. Pattern breaking is centered around the imperfections and variability of the human mind and judgment. Regular player activity does form patterns to some degree, but typically it isn't as pronounced as those of bots. There are two categories of pattern breaking: Large scale More useful for public scripts or large farms Focuses on creating differences between accounts through account preference Different methods of performing tasks Different subsets of antibans per account Each account may be only able to use 7 out of 12 generic antibans available for the script This increases the longevity of the script by allowing less opportunities for Jagex to group accounts via similar actions Different frequencies of antibans per account Account A may perform one antiban more frequently than account B Changes in sleep and delay times per account Accounts all have different run times This is mainly for farm detection, not for public scripts Different accounts running the script in different worlds/locations if possible Unique break patterns per account Different muling cycles Small scale Focuses on preventing accounts from producing patterns through their actions Changes the order of sub-actions within a larger action when order does not matter More useful when incorporated as part of a complex script process Avoid hardcoding script processes as first A, then B, finally C Instead use fluid condition checks to see what action should be performed Then use account preference and probability to determine which of several actions it prefers over the others Action[] actions = getActions(situation); // This should perform action condition checks and return only relevant actions boolean performed = false; for (action : actions) { if (accountPrefers(action) && accountProbability(action)) { performed = performAction(action); if (performed) { break; } } } if (!performed) { performAction(action[General.random(0, action.length)]; } While this may seem excessive, this is how players decide what to do next in a sequence of events Antiban is a large part of pattern breaking Performing actions you don't usually do is an effective way to break patterns Misclicking can be seen as a form of antiban as it's infrequent but deviates from your normal activity Avoid randomization Randomizing everything from antibans to sub-actions within a larger action schedule may seem like an appealing idea While it's likely to work to some degree, it will make accounts on the large scale appear too similar to each other We're trying to get our accounts to operate in the grey area between a well defined pattern and no pattern at all If all accounts operate in this grey area their patterns will be loosely defined but dissimilar from each other The idea of pattern breaking shows promise, however it has many requirements. One of which is account preference which is something Tribot has some support for, but this support is limited. For example a scripter has no way of applying Tribot preference to custom made functions. The solution is to make your own preference system where the account's username and a seed value is used to derive a value from 0 to 100. Below is my own way of doing so: /** * Performs a probability check on the input value. Input a percentage (0 - 100). */ public boolean chance(double chance) { return General.random(0, 100) <= chance; } /** * Scales a value based on its original range so that its position in that range is in the same position in the new range. */ public double normalizeValue(double value, double oldMin, double oldMax, double newMin, double newMax) { double percentage = (value - oldMin) / (oldMax - oldMin); return newMin + percentage * (newMax - newMin); } /** * Generates a username based preference value for the given seed (0 - 100). */ public double preference(double seed) { try { String hash = Double.toString(Player.getRSPlayer().getName().hashCode() * Math.sqrt(seed)).replaceAll("[^\\d.]", "").replaceAll("\\.", ""); String int1 = Character.toString(hash.charAt(hash.length() - 1)); String int2 = Character.toString(hash.charAt(hash.length() - 2)); String int3 = Character.toString(hash.charAt(hash.length() - 3)); return normalizeValue(Double.parseDouble(int1 + int2 + "." + int3), 0, 99, 0, 100); } catch (NullPointerException e) {return 50.0;} } /** * Generates a username based preference value for the given seed, but normalized to match the provided range. */ public double preference(double seed, double min, double max) { return normalizeValue(preference(seed), 0, 100, min, max); } /** * Performs a probability check on a preference value normalized to match the given range. */ public boolean preferenceChance(double seed, double min, double max) { return chance(preference(seed, min, max)); } Hopefully I've included all the necessary functions for the above to work. If you for example wanted to test an account's preference for performing Action A over Action B, you could take the hashcode of each actions, remove all non-integer characters from each, input them into the functions above, and receive a preference for each. I recommend using custom ranges like preference(100, 15, 85), where 100 is the seed, 15 is the min chance, and 85 is the max chance. That way the preference range will always be within 15% and 85% and you won't ALWAYS or NEVER perform that action above other actions. It should also be mentioned that you shouldn't be using these preferences to determine which actions to do, only to determine which actions should be performed above other actions. All actions should be performed as long as they're part of your script. This post ended up being much longer than I originally wanted but it's good to get your thoughts out in writing so I'm glad I spent the time. Going forward I would appreciate a healthy discussion, please add to the thread with your comments rather than just taking up space with pointless nay saying.
  40. 8 points
    Back again with this cursed barrows script, only this time it's been well written from the ground up, updated to utilize my latest knowledge and resources. Today was the first day of full chest runs, but expect some more proggies and information as I finish development. Currently supports: Any mage/range gear Spelling autocasting/Trident/Slayer dart Use of any food/pray restore potions Dynamic brother killing order Fastest method to barrows (including Barrows teletabs and whatever Dax's webwalker decides) Recharging health/prayer at clan wars portal Plan to add: Option to pray OR tank each brother Your suggestions!
  41. 8 points
    Missed out on this weekends P2P trial and couldn't bot as the flicker issue made my scripts missclick too much to the extent where my scripts basically got completely broken in certain areas (etc. by right click and not choosing the scripted option). Missed out on a lot of money due to relying on trilez to fix this within an understandable time. I understand that it might be a hard fix, but then he should he should take help of others (such as paying people who have already fixed the issue, or get the community involved to try solve it) instead of just keeping us in the dark and trying to fix it himself when it obviously isn't going well. Not happy at all right now.
  42. 8 points
    So this has been broken (in a state of flickering/no LG) for a week now and RS just updated again. Are we going to catch up at some point? The last update that your paying customers have been given is that there is no update. I think we're all a little overdue for some basic customer service. I'm sure I'll get responses saying that it works just fine, but your arguments are the same as saying your computer works fine if the keyboard doesn't function because it turns on. Can we get a little bit of clarity please?
  43. 8 points
    Hi everyone, It seems like the TRiBot client isn't loading at the moment. Please post your error logs below and I will update this thread when we have an update. Hopefully we can all get botting as soon as possible! Rabbit hop!
  44. 8 points
    The broken hooks have been fixed. The regular client is now back in working order. LG is still out of commission and is expected to be fixed later tonight.
  45. 7 points
    Hello, I wrote this script at quest release, however I never got around to finalizing and posting it. It is in mostly one class, however it should still be quite readable. It is built using the EnumScript framework which I quite like. Features include: Start the script at any step or anywhere in RuneScape that is supported by Dax's WebWalker. Arguments for house favor and skill lamp selections. By default, Arceuus house is chosen and the skills chosen are randomized. If you provide arguments, it will not randomize. Requirements: Only requirement is to have 1 feather or 2 gp. Arguments instructions: (important for customization!) Script can be found here: https://tribot.org/repository/script/id/2569 Source can be found here: https://github.com/FALSkills/TribotScripts/tree/master/clientofkourend Thank you to @Final Calibur for his ACamera class, and @daxmagex for his WebWalker and included utility functions. Walking in RuneScape would be a pain without you!
  46. 7 points
    Up now. Had to message support and wait to force start server up since I wasn't able to ssh into it.
  47. 7 points
    Back-end problem. Expect a fix in 10 minutes.
  48. 7 points
    I'm sorry i have to be the person to deliver this news Today marks the death of "King Bleat" born December 15th 2016 soon after his life begun i quickly realized he had a major passion for fishing he was a natural born i still remember the nights i would come check on him to see if he was okay and he would've caught 2x the fish as his siblings he loved it. it was the only thing he wanted to ever do, i tried to show him other things but he hated it I'm not sure what went wrong last night i could not get a clear answer but a few witnesses say him and mod wealth got into a fight about a cat or something. R.I.P King Bleat 15/12/2016-10/5/2017 He was a fishing worrier In his life time he achieved Nearly 25 Million XP in fishing Two Pet herons Some PayPal balance for HarmedOreIsLeet Please Press F for fuck Mod Wealthfor respects and to long live his legacy
  49. 7 points
    I see these threads all the time; they post once or twice, then die off after they realize it's not that simple. They make the accounts, buy the gold, set up the method, then realize that their accounts are banned in 24-48 hours of creation. If it was as simple as it seems, everyone would simply make 500 accounts, and bring in 20b+ a month. I do wish you the best of luck, but I'd STRONGLY suggest testing your script/method with a few accounts before you do anything else. It's easy to get caught up in the 'potential' numbers, then realize they're totally un-obtainable. I like to call it the karamja shop fever lol. People realize karamja shop bots can make ~5M/hr if everything ran perfectly. Naturally, people go, hmm.. 5m/hr x 5 accounts (about how many accounts the shops support without interfering with eachother) = 25m/hr x 12hrs/day = $300m/DAY! Then you realize with competition, it goes down to like 2-3M or so per hour. Then you realize you need 40-50m/HR per account in supplies to keep it running, which means tons of gold on accounts that could be banned. Then you realize that they do tend to ban mules too, and you need 2-3B on those mules to maintain a steady supply of items to sell. Then you realize those shop bots get banned frequently, and they take about a month to bot up all the reqs at 12hrs or so a day, and on top of it have to spend ~10 hours questing them. Some of them might get banned halfway through which is frustrating too, and at the end of the day you're worn out, and not profiting much at all. Edit: Yes. I did run karamja shop-bots for a long time. (24/7 for 4 months bringing in like 200M/day in profit -- Man I miss those days) Stopped shortly after they upped the reqs to karamja 3 gloves because of the training required, and more frequent bans.
  50. 7 points
    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.