Welcome to TRiBot Forums

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.

TRiLeZ

Administrator
  • Content count

    3,344
  • Joined

  • Last visited

  • Days Won

    134
  • Feedback

    100%

Everything posted by TRiLeZ

  1. Delta Woodcutter Delta Woodcutter is a feature-rich woodcutting script with an anti-ban compliance level of 10. It comes with pre-defined support for the common areas, along with custom tree/area support. Features: ABCL 10This script has an anti-ban compliance level of 10. This means that it performs most, if not all, anti-ban methods in TRiBot. These ABC (anti-ban compliance) methods aren't your standard anti-ban. 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.Ability to Upgrade AxesIf banking is enabled, the script will upgrade to the best axe in the bank when it reaches the level to do so.Ability to Upgrade TreesAll trees which require a lower level than the best tree your character can cut will be removed from the list of trees to cut.Ability to Pickup Bird NestsIf banking is enabled, the script will pickup birds nests.Ability to Use Custom Trees/AreasThis script has a very flexible framework. To use a custom area, just add one with the GUI. All you need to specify is info about the tree, and where it is located. TRiBot will handle the rest, even banking. You don't need to bother defining a custom path to the bank. High Quality ScriptNobody knows TRiBot's API better than myself. I know exactly what methods to use to ensure that the script is fast, smart, efficient, doesn't screw up, and doesn't die because of bugs/exceptions.Ent DetectionThis script will avoid ents as soon as they appear.Easy Axe WithdrawalIf you start the script without an axe, or if the bot somehow breaks or loses its axe, it will go to the bank and withdraw a new one.How Much Does it Cost? Delta Woodcutter costs $4.00/month. After purchase, this script can be run with unlimited instances.How do I use It? Purchase it on the TRiBot Repository.Run the script.Fill out the GUI.Click start.Any Upcoming Features? Script stats per user.Changelog (Current Version: 1.07): Progress Reports: Let me know if you have any suggestions or questions, or if you experience any bugs.
  2. Hello community, I have started working on a new project aimed at making TRiBot's mouse movements as human-like as possible. To do this, I plan to implement real mouse movement data, replacing TRiBot's pseudo mouse movements. Real mouse movement data will be generated by users, clicking strategically placed circles, all with different sizes. The data recorded will be movement locations and timings. After enough data is collected, I will work on analyzing the data and implementing it in the client. That's right, TRiBot's mouse will use real, human mouse movements. We will be able to further throw off Jagex's detection systems, especially because Fitt's Law will be used along with the human mouse movements. We are currently in the data collection stage, where I need the community's help. The details for providing help are listed below. What will you be doing? You will need to run a certain script. The objective will be to click ~628 red circles, which will take approx. eight minutes. After finishing, a file will be generated. You must upload the file in an attachment in a post in this thread.When should this be done? The sooner the better.Will you receive compensation? After you submit the required amount of files, you'll be given access to bot using the Human-Based Mouse (with your collected data). This will make all of your bots seem more human-like.How many data files are needed per user? I need between 20 and 22 data files per user. The higher, the more human-like the mouse will be. Instructions: Open TRiBot's Mouse Data Collector tool via "File > Mouse Data Collector" Read/do: You will be clicking the solid red circles, one after another. Your goal is to click each circle quickly, and to only click once per circle (try not to misclick). Your clicks need to be as accurate as possible. If you can, set your mouse's reporting rate to the maximum. Set the client delay to the lowest. Do all of the clicks on one sitting. Do not do anything else other than clicking those circles for all of the ~628 circles. This will take approx. eight minutes. Post all of the data files under a single TRiBot account. If you use multiple TRiBot accounts to post the data, your data will be ignored. Do not post the same data files twice. I can tell if you do so. After clicking all of the circles, a file will be created, and the location will be stated in the debug box. Upload that file to a post in this thread.The system to integrate human mouse movements is complete. All we need now is mouse data. Thank-you, TRiLeZ
  3. Would have fixed this earlier but I was out of the city all day. Working on the fix as I write this.
  4. Delta Cooker Delta Cooker is a cooking script with an anti-ban compliance level of 10. It comes with support for cooking single items as well as making wine (which is 300k xp/hour). Features: ABCL 10This script has an anti-ban compliance level of 10. This means that it performs most, if not all, anti-ban methods in TRiBot. These ABC (anti-ban compliance) methods aren't your standard anti-ban. 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.Ability to Specify Items to Cook by Name, or By Selecting a Pre-Defined FoodWhen the GUI pops up, you just have to click on the items you wish to cook from an already made long list of food. You could also enter the food by name if the list doesn't include the item you wish to cook.Wine MakingThis script has the ability of making wine, which is the fastest way to achieve 99 cooking. The method is 300k xp/hour.High Quality ScriptNobody knows TRiBot's API better than myself. I know exactly what methods to use to ensure that the script is fast, smart, efficient, doesn't screw up, and doesn't die because of bugs/exceptions.Script StatsEach user will have the ability to show their script statistics in his/her signature. (The image/url is still to come, but stats logging is active).What locations are supported? Al KharidCatherbyRouge's Den** Wine Making supports nearly all banks.How Much Does it Cost? Delta Cooker costs $1.00/month. After purchase, this script can be run with unlimited instances.How do I use It? Purchase it on the TRiBot Repository.If you are wanting to cook in the Rogue's Den, please navigate to the den before starting the script.If you are making wine, please make sure to have jugs of water and grapes in your bank.Run the script.Fill out the GUI.Click start.Changelog (Current Version: 1.02): Progress Reports: Let me know if you have any suggestions or questions, or if you experience any bugs.
  5. This thread addresses common TRiBot Loader problems. Problem: Gets stuck on updating substance.jar Solution: Delete the files in %AppData%\.tribot\dependanciesUninstall all previous Java versions, then install the Java 8 JRE from http://www.oracle.com/technetwork/java/javase/downloads/jre8-downloads-2133155.html Problem: The TRiBot Loader says it was successful, but TRiBot does not show up Solution: Delete the files in %AppData%\.tribot\dependanciesUninstall all previous Java versions, then install the Java 8 JRE from http://www.oracle.com/technetwork/java/javase/downloads/jre8-downloads-2133155.htmlYou may need to remove the old versions of Java from your computer, or just remember to select the correct Java from the drop down menu. Problem: Solution: This error means that Java 6 was used to boot TRiBot. TRiBot is not compatible with Java 6. You may have the latest version of Java installed on your system, but the problem is that you are selecting Java 6 for use. You must select Java 8 or 7 in the drop down menu of the TRiBot Loader. I also recommend that you uninstall all of the old versions of Java from your computer, and install Java 8 from here: http://www.oracle.com/technetwork/java/javase/downloads/jre8-downloads-2133155.html
  6. We are not currently able to accept bitcoin payments as Coinbase closed our account for a reason which they denied to specify. We are working on a new solution to accept bitcoin payments.
  7. 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.
  8. Is this still happening with the latest release, which came out Thursday? It contains the fix for this.
  9. This update features: Fixed the combat API issues. Deprecated RSCharacter#getCombatCycle, RSCharacter#getHealth, RSCharacter#getMaxHealth because of the recent health bar changes. Added RSCharacter#getHealthPercent and RSCharacter#getHPBarCycle. I apologize for the long delay in getting this update released. To compensate for this delay, I am going to extend all current VIP users' VIP subscriptions by two weeks.
  10. Hello community, I am extending the previous Reaction Timing Data Collection Project to record much more data than before. This new project will collect data on reaction times, more reaction time factors, how the player interacts with interfaces/items, and much more! The aim of this project is to study how real players interact with the game. With this knowledge, we will build upon TRiBot to reflect human-like gameplay based on real human data. If scripts successfully implement new playing mechanisms based on the data collected, I suspect that there will be a drastic positive effect on the ban rate. This is where you come in. I need many users to take part in this data collection program. The details are listed below. If you care about bans and would like to avoid them, then please partake in this program. This project is TRiBot's most important project regarding fighting bans. The data collected from this will re-shape our current antiban, and will lead to a new generation in human-like scripts. The data collected has the potential to cut bans to a small fraction of what they are now. Please contribute to this project. Do You Qualify? You can either do woodcutting, mining, fishing, combat, or cooking (via range only). Reaction times currently won't be collected for any other skills.You must play for at least 2 hours straight. If you can play for longer than that, please do so.How Do You Participate? Activate and run this script. Play RuneScape like you would normally. Make sure to only do one of the activities listed above. Feel free to tab out / watch youtube / watch netflix / text your friends / take bathroom breaks if you want. Your aim should be to play normally. Try and play for at least 2 hours straight. Don't split those 2 hours into 30 minute sessions here and there because I'm not able to study human fatigue if you do that. After those 2 hours of playing (or more) are up, stop the script. Once the script has stopped, TRiBot will print something like " Wrote data files to "C:\Users\TRiLeZ\AppData\Roaming\.tribot\reaction_times\1422335835540"." This is the directory which TRiBot dumped all of the data. Upload the data (all 8 files) to a forums post in this thread. Include a comment about what activity you were doing while collecting the data, and the respective skill levels.Note: This is not a race. Do not aim for having the lowest reaction time possible. Please relax and play as you normally do in order to ensure reliable data.
  11. The fix for this issue was released in today's update.
  12. Released.
  13. I'm currently fixing a loading error with LG. Once fixed, I can release it.
  14. As you all know, TRiBot has been down for the past few days, which I deeply apologize for. On Thursday I was performing maintenance on the server to increase its throughput, storage capacity, stability, and speed. The first road block which I hit - a minor problem with swapping the server's drive - led to having to temporarily route traffic away from TRiBot while I fixed the issue. This was only supposed to take less than an hour to fix. In the meantime I had to unfortunately deal with some home network downtime causing me to re-locate and work from elsewhere. On top of this, I had to factory reset my phone causing me to lose two factor authentication (2FA) info for many sites. While I was able to quickly recover access to most of the accounts which were protected by 2FA, some of them required a more lengthy process which is where most of the downtime occurred. I've already ordered a dedicated hardware 2FA device to prevent the situation of being locked out again. I'm also working on implementing an auto-scaling, distributed computing network so that if one cluster server goes down, there will be others to take its place. This will be phased in within the next month. Once again, the staff at TRiBot deeply apologizes for the downtime. To compensate, we will be extending all VIP/E and script subscriptions by 7 days. Sincerely, The TRiBot Staff
  15. Looks like it's just a bad multiplier. I just need to test some things before the release.
  16. Looks like the ID hook is broken. Should be an easy fix. The API actually doesn't use the NPCDefinition class. Everything is read from the cache. Edit: Actually, I don't call that class NPCDefinition b/c it doesn't follow the same scheme as the other definition classes. But we are talking about the same class.
  17. Are you able to upload the head dump by any chance? How big is the file after compressing it?
  18. Thanks for your input. Fun fact: We are often with with large layer 7 DDoS attacks which are sofisticated enough to by-pass CloudFlare's DDoS protection ranging from 10Gbps to over 100Gbps but nobody releases this because the custom DDoS protection software I've written is usually able to completely block the attack within a few minutes. And when it even gets past that, it's very rare for a DDoS attack to actually bring down our servers as they are capable of withstanding the attack while I manually mitigate the attack. When we first became popular, there was someone who tried extremely hard to shut us down with a 100+ Gbps attack which persisted for over a month. Yet here we stand. If I weren't suffering health issues I'd be much more active in the community and would be releasing a lot more frequent updates. I'm trying my best to bring myself back to my prime. Before you mention it, yes we're already expanding our development team. Also, I improved our fraud detection system to be much less restrictive so you will be able to purchase credits via Stripe and PayPal now. The reason why the system was like that in the first place was to stop the 20-200 monthly credit card fraud cases which were able to pass Stripe's and Visa/Mastercard's fraud prevention systems because of a many people using stolen credit cards. As for the issue with Coinbase, it was completely out of my control. I was given no notice from Coinbase whatsoever. Not being American adds much difficultly to being able to find suitable payment processors to be able to accept international orders. Anyways, I'm closing this thread to stop the bickering.
  19. Hello, We are pleased to announce the release of the TRiBot Bot Control Panel. The TRiBot Bot Control Panel is a user-web-interface which allows users to control their TRiBot clients via a web browser. Users are able to see how many clients they have open and what scripts are running on those clients. Users also have the ability to start scripts, stop scripts, re-run scripts, and request a client image within the TRiBot Bot Control Panel. This feature will be free for the next 7 days. The cost of the feature afterwards will be released at a later time (although it's only a small fee). The TRiBot Bot Control Panel can be found here: https://tribot.org/botpanel/index.php Cheers, TRiLeZ
  20. Here's what I can mention: There's a ton of updates for TRiBot which need to be released, but I'm still in the process of tweaking ABC2 timings to make them extremely accurate in comparison to humans, and less predictable after long periods of time. I need to finish up with the ABC2 modifications before I can release everything else.
  21. I'm ten months I could finish my AI auto-responder which learns how to communicate with RuneScape players off a vast database of conversations between legit players, implement an AI web walker based off terrain deta and from a large amount of data from legit RuneScape players traveling from place to place, implement LGv2 which could quite possibly be 10-100x faster than the current version of LG depending on if everything falls into place like it should, and implement the 2-5 of the cloud services I'm considering implementing if I think they are worth it, which will be helpful for developers, scripts, security, and users. If you want an ETA, I'll tell you this: patience. 10 minutes from now? A day from now? A week from now? A month from now? 4 months from now? The release will be a surprise with some strategic timing.
  22. Another thing I'll mention: This is the kind of beautiful design I'm looking for. This probably won't be what the repository/bot panel books like in the feature, but I'll look just as amazing.
  23. Our web walker can generate a path from the very top right most corner of Runescape to the very bottom left corner of RuneScape is under a second. I've seem other bot devs talk shit about each others bragging about how much faster each others were when it would take seconds to generate paths of distances much less than half my distance (not going to name names). The base of our web walker is very solid and efficient but it's just not very flexible and doesn't have specific areas mapped out nearly enough. Plus I know there are some scripts which modify certain settings which makes the script kill the web walking process and restart it which can create heaps of problems. I only ever run my own scripts and it's very rare for me to experience any malfunctions with the webwalker where other scripts seem to have many problems in the same areas my scripts operate in. Another thing to consider is that I mapped out half the the entire RuneScape map in a mere 2 days so some areas weren't mapped enough where as other botting clients spent months or years designing their web walker. It is getting a complete re-write though, right after I finish up with the project we've been working on for over a year is completed. Yes, some clients are catching up to our client, but there's an update coming soon which will completely blow TRiBot out of the water. Imagine if TRiBot were to run 50 clients at less than 20% CPU usage with 0ms paint delay and less than 2GB of RAM on my very out-dated 3770K prcoessor at clock speeds with more features than ever, and if it were written with high concurrency and anti-ban at its highest priority while having none of the bugs it currently has today. Oh, and the scripters aren't in-active. They're just waiting for a certain update.
  24. 1. We already have enough premium scripters. And if premium scripters are finding they aren't making much money anymore, then they should have actually listened what myself and Usa has been telling them for years - not to sell unlimited instance lifetime scripts. Let me reference the user who runs the most concurrent accounts here at TRiBot. This user has an unlimited lifetime script which we bought for less than $100 a long time ago. This user runs between 2-5k accounts concurrently, 24/7. For this, the user pays $8/month for VIP. That's it. There are many other users who run over 1k or hundreds of accounts concurrently 24/7, and they are all paying between $8-$50/month. The premium scripters who allow this to happen (note: not all of them do) do so because they think it's making them more money, but in the long term they are screwing themselves and others over. Also, there's a reason not many scripts are being produced right now, but those are private matters. 2. The forums don't need spam to increase engagement. Intellectual debates are a better option. 3. I have scripts which haven't been touched since 2014 and they still work perfectly fine. If you find a script which doesn't work, report it. 4. Teasers will come when they come. I've seen bots come and go barely leaving a mark, I've seen bots rise and fall, and I've seen TRiBot climb from 15 active users and no paying customers to 8k+ paying customers when OSRS was at it's prime, even after reading a Powerbot admin/moderator said TRiBot would never go anywhere (Many, many, many years ago. I don't recall who so don't ask). Now we are close to taking the top Google rank for "runescape bot." I will always keep pushing botting to new levels, and I plan to stick with my methodology.