Leaderboard

As discussed it would be good to see you make a script with a GUI. While it's not required, most users expect it and for anything more complex it'll need to be configurable. You said in discord you were most happy with your agility script so I'll look at that - although your firemaking script is a bit of a joke, it's literally like 4 actual lines of code. Plus if someone just plants flowers or lights a fire or something under a dropped log on the floor you're going to get stuck. 1. You've got a lot of potentially infinite loops: while (!isDistanceFrom(destination, 1)) { General.println("[Rooftops] WebWalking to " + destination.toString()); WebWalking.walkTo(destination); Timing.waitCondition(() -> !Player.isMoving(), 5000); } If the player ever gets into a situation where it can't walk to the tile (e.g it accidentally enters a non-dax mapped region, or the dax walker fails for any reason) then you've got a infinite loop. You do this A LOT in your other scripts, for example the entire run method is filled with them in the bloodcrafter, asking for it to get stuck: https://github.com/sengineer-tribot/SEngineer-BloodCrafter/blob/main/src/scripts/rc/main/SEngineerBloodCrafter.java Just from a glance, this is the biggest problems with your scripts. It's fine until you have 100 users running at 5fps on vps's, then a lot more goes wrong than you might think. 2. You don't check the result of boolean methods: if(SEngineerRooftops.shouldHop) { General.println("[Rooftops] Hopping world as player detected"); WorldHopper.changeWorld(WorldHopper.getRandomWorld(true)); SEngineerRooftops.lastHop = System.currentTimeMillis(); SEngineerRooftops.shouldHop = false; } If the worldhopper was to fail here and return false, your script still acts as if it succeeded. You also don't ever check the result of a Timing.waitCondition call, which is useful because you're usually waiting for something to happen and it if hasn't, you likely want to react differently rather than plowing on. 3. Very static antiban https://github.com/sengineer-tribot/SEngineer-RooftopAgility/blob/ceb3fb177109e70146c63daf50ee5860fdc966f3/src/scripts/rt/support/ABC2Support.java#L71 You're hardcoding this to activate energy every 5 minutes, and other things on static timers. This sounds like a really bad idea. 4. Null checking https://github.com/sengineer-tribot/SEngineer-F2P-Firemaker/blob/6597eaee3c1019ec82faac73774490e0fac7592e/src/scripts/fm/utils/Utils.java#L88 You don't null check things that could be null, the getDefinition` class is notorious for doing this. This'll throw a nullpointer at some point Some more general code things.. 4. The number class https://github.com/sengineer-tribot/SEngineer-BloodCrafter/blob/main/src/scripts/rc/utils/Numbers.java I really have nothing to say 5. Variable shadowing https://github.com/sengineer-tribot/SEngineer-RooftopAgility/blob/ceb3fb177109e70146c63daf50ee5860fdc966f3/src/scripts/rt/courses/Course.java#L93 Doing this is really confusing apart from a very basic setter, I would avoid at all costs. 6. You use protected variables directly from the subclass: https://github.com/sengineer-tribot/SEngineer-RooftopAgility/blob/main/src/scripts/rt/courses/AlKharidCourse.java While this isn't wrong, generally accessing protected variables like this isn't great for a number of reasons, especially because you don't need to. Here I would expect the Course class to have a constructor, and the children to just call super() to set it. Although really this just looks like a place for a Course enum instead - then you could have a CourseHandler class for example which contains your doCourse method and the such. Another point is that you're creating a ABC2 instance for each course variable currently where it's not really needed. It would also make your main getCourse method nicer, as you could just have the level requirement as a field on the enum and loop through them all. 7. Some useless methods https://github.com/sengineer-tribot/SEngineer-RooftopAgility/blob/ceb3fb177109e70146c63daf50ee5860fdc966f3/src/scripts/rt/utils/Utils.java#L92 What's wrong with just Inventory.getCount() ? 8. Just a few crappy bits of code. We all write them sometimes though https://github.com/sengineer-tribot/SEngineer-BloodCrafter/blob/63cf0e82aaf03d3cac4911c17e2034d59b3f9524/src/scripts/rc/utils/Utils.java#L322 - this one's obvious https://github.com/sengineer-tribot/SEngineer-BloodCrafter/blob/63cf0e82aaf03d3cac4911c17e2034d59b3f9524/src/scripts/rc/main/SEngineerBloodCrafter.java#L282 - Ideally would use a enum or something to loop over rather than a massive if-else block. Could also just return false instead of setting a variable https://github.com/sengineer-tribot/SEngineer-F2P-Firemaker/blob/6597eaee3c1019ec82faac73774490e0fac7592e/src/scripts/fm/main/SEngineerFiremaker.java#107- Are you telling me you'll make a constant for the number 1, but not for your item id!? There's more things that aren't perfect but they're not too big of a deal. Don't take all of these as "blockers" for you being a scripter - the main ones I'm concerned about are 1, 2, 3 and 4.

I have a feeling it may be client-related, but I'll continue to work on why it might be lagging for you Mithril Dragons are technically already added and done (I removed them in a previous patch), but I need to make the script use combat prayers before they're re-added, since they're impossible to kill without Piety etc. (defences are too high and accounts just eat food and can't get even 1 kill without being maxed) I use Tribot's abc2-enabled banking class for withdrawal - it's what the creator of tribot designed and intended for scripts to use. I wouldn't be worried, as most of the banking methods are anti-profiled (eg. scrolling the bank is different across different accounts) using abc2 and quite good. I can make it sometimes check the level tab before drinking potions, sure - although almost the entire OSRS community uses Runelite/OSBuddy at this point It's designed to use low dose potions if there are no higher dose potions left. If you want it to only use 4 dose potions, make sure you have enough 4 dose ones before running it People requested it to work this way, rather than just buying new 4 dose potions

Part 1: https://community.tribot.org/topic/78220-cyberwizard-botting-guide-for-users-and-scripters/

A child who joined in 2019 with cringeworthy self-help graphics made from MS paint who makes his entire livelihood from a public Zulrah script that's been on the market for years before he even joined, telling me what to do. My apologies Tribot police, didn't mean to offend your delicate senses. I understand that you probably live and die by Worthy, since it's painfully obvious his very public Zulrah script is the only thing feeding you, but there's really no need to ride Worthy's dick even more than you already are. All those countless instances that you are paying for is already enough for him, I promise you. PS: It's cute that you tried using my gif as some sort of insult, so let me return the favor. When you say "Work hard in silence... Let your success make the noise" does that mean making an obnoxiously hideous banner plastered with tbows and elysian shields and putting in your Zulrah hi-score to show off to the public fit that criteria as well or is that an exception? Lol. Happy Botting!

Did quests and trained stats for his bot account. Payment was received it's been a pleasure working with you thank you.

SEngineer's Progressive Rooftop Agility [New] Gnome Course Added! Start at level 1 agility. This script will train Agility on rooftop courses. It will change to the next Agility course as soon as it is unlocked. It will collect marks of grace between laps. It will hop if another player is detected on the course. You can start the script anywhere. It has ABC2 implemented. It is recommended to zoom out before you start the script. Link to Repository: https://repo.tribot.org/script/id/3700

Holy cow i didn't even think about Botanist & Seaweed.. What a great idea. Thanks for the info! I'm going to buy an auth and use for selling ore to Tzharr shop for tokkul. Thanks

If the issue persists, please follow those instructions:

Doing some quests and skills for my botting account

Can you send me a gif of it banking? Can be via PM. Need to see what it's actually doing for this to happen - maybe it's not depositing the ones from the previous task? (which is on purpose) Sure Option to hop on other players speaking is coming soon

got 99fish with this script. Thanks!

Theres some setting in advanced preferences under methods -> superglass called fast withdraw items or something along those lines which should do that

Sure, will try to address this issue as soon as possible. Thanks for the suggestion.

Hi there, I was using the bot to chop mahoganies and was pleasantly surprised to learn it worked at fossil island hardwood patches. However, the bot uses the agility shortcut running to the bank, but goes all the way around when returning to the tree. Is there a way to make it so that the bot uses the agility shortcut both directions? Thanks!

A Pro's Guide to the Ultimate Botting Success (For Users AND Scriptwriters) Part 2. Pretext: To start, this guide will re-iterate much of the last guide, in a more (hopefully) clear fashion. Along with some new updated knowledge. This guide will cover many ways users can improve their success with botting, and will cover how scriptwriters can improve many common issues I see in scripts. I have been botting for over ten years now, with great success. I have recently gotten back into botting, and am aiming to ramp up to the most I ever have in my career. I am currently at the time of posting running two servers with Intel Xeon Core processors, with 25 accounts roughly on each server, with another 4-5 constantly active on my main PC preparing to bot more. I have the capabilities to run up to 10 physical servers, and aim to get there if all goes well. I am sharing this information, because I believe it will give many users onto an insight to why they pressed "start", came back 24 hours later, and got banned, and how they can avoid that the next time. I'm also writing this guide so scriptwriters can pickup on some key features they're missing, that they may not think are important, but will lead to a much better product in the end. This guide applies to people looking to run just one or two accounts, but also (and mainly), people looking to run bulk accounts. Whatever your goal is, pick and choose whatever suits yourself. It is important to note, I have very little insider information from Jagex. My information is sourced from personal experience, talking to many communities throughout the years, many of which no longer exist, and much is speculation. I may be right, or wrong on many things, but I feel I have a strong enough grasp on how things work, that I can confidently share this information, with faith most of it is accurate. Needless to say, most of the information in this article is subjective opinion. If you think I'm wrong, no worries, happy to discuss anything in the comments. Here is my current account I'm working on, besides my bot farm: Jagex's Bot-Detection System (How I think it works): Jagex's bot-detection system (in my opinion) works off a series of flags, levels, and "elevations". I believe there are invisible Jagex Moderators paid to "Flag" or "Escalate" accounts, for advanced view by the "system". From years of trial and error, I notice patterns. When you first start a basic bot-farm (example fishing, woodcutting, etc), even if you have a good premium, or private script, with good randomization, there is still a good chance, that between a week and a month from when you start botting, you'll start to see a lot more bans, than when you first started. This I believe is due to Jagex's data collection. The game collects much data that is unknown to the public, and in my opinion, it collects data such as how many shrimp are fished in Lumbridge swamp, how many willows are cut in Draynor village, etc. I believe that there are certain flags in place, where across all worlds, if a certain threshold of resources are gathered, for lack of better explanation, it triggers a flag in the Jagex system, for a Jagex Moderator to scout worlds invisible, flagging accounts they think are bots, for further review. That being said, of course I think most bans, primarily come from a nearly fully automated system. Any accounts banned by the system will be "Macroing Minor", or "Macroing Major". Any accounts reviewed manually by a Jagex staff member (likely the system thought they were a bot, but could not fully verify (probably 5-10% of botting bans)), will have a "Bot Busting" Minor/Moderate/Major ban. I do not believe Jagex Moderators directly ban accounts in game while invisible. That being said, I think if your account is botting, and a Jagex moderator comes by invisibly and "flags" or "escalates" your account, in my opinion, your account is likely done for. I think the "flag" or "escalation" as aforementioned, works by placing the accounts on "levels", that are temporary. I have a not completely certain belief also, but fairly certain belief that it goes as following; The first level is normal, human, nothing special. One up, "level two", is a semi-unimportant level, where after a player repeatedly clicks on something a bit longer than usual, is stuck moving, doesn't move camera or moves it in bot-like manner, or other "flags"/"escalations" are triggered. I believe this to be a basic system, like mouse delays theoretically are. I think that it simply looks for flags based primarily off time, possibly actions, then puts them up to "level two". After this, I think there may be a separate anti-cheat system, more advanced, that looks deeper into how the account is actively playing (I don't think it compares past play history/style to present in its analysis). I think this "level three" system, has the ability to ban accounts it thinks are bots, after it analyzes play-style. I think there's not a specific time-frame on the analysis + ban, but I believe for obvious botting plays like spam clicking something, someone has no purpose spam clicking, it can be as quick as 10 minutes to be detected and banned, basic botting on a bad script with poor anti-ban roughly 30-120 minutes for detection, and a quality script, hours, to possibly never, depending on the configuration the user setup. Jagex will not ban all bots they find, due to the fact bots pay a massive amount of membership, and bring more money to Jagex than take, but they still must maintain the persona that they're anti-bot, and cannot let the game fall fully into ruin, so they will ban a percentage, and leave some unbanned. Jagex also must have the mindset that they should not ban a single legitimate player with their system, because that could, and likely would, be a PR nightmare. I believe if the system has any "clear indication" in its "flag" or "escalation" logic, that an account isn't a bot, or it can't absolutely verify with all the needed flags, it will not ban the player, due to the fact they "have to be safe, rather than sorry". That being said, I believe that if the system is near absolutely-certain an account is a bot, but one flag will not trigger, and the account has been running suspect for a while, it is forwarded to "level 4", for manual review by a Jagex staff member (Likely this will be the Bot busting ban, rarely macroing major). I believe a large part of determining if an account will receive macroing minor, or macroing major, is primarily based off of if it runs detected for more than 16 hours straight, how many accounts are being run on the IP address, and how far the account is. I know for a fact that the amount of playtime, is not a factor Jagex takes into account when looking into bots. Breaks are a complete waste of PC resources, and time, when botting. Why Tribot Over Others? There are many different bots available, and in my opinion, Tribot, is the best in functionality, which matters the most to me. I'm not sure if this still holds true, but last I checked a few months ago, OSBot for comparison, did not support middle-mouse camera movement whatsoever still. Tribot has had this for years. Tribot's developers are striving constantly to update the bot itself. I'm ignorant to Tribot X, but it's some big project they're working on to advance things further, Tribot 12 was released recently too, which runs very stable, uses very little CPU (massively important when bot farming), and has very functional GUI. You can access what you need quickly (Disable graphics, block user input, start/stop/pause script), you can configure things to be more efficient (I lower RAM usage to 386MB from 512MB, enable "Lite mode"). Tribot has a strict application process that vets any premium scriptwriters, and it's easier to be denied than accepted. Tribot may lack in the quantity of scripts compared to other bots, but the scripts it does have, are very professionally made, and maintained as one would expect. Tribot has a policy in place to protect buyers of scripts if a scriptwriter does not update & fix bugs as they should for a paid product as such. It's obvious that those on Tribot like @TRiLeZ, @Einstein, @Dentist, @Optimus, @Aropupu, @Laniax, etc, are dedicated to the products they provide, and in my humble opinion, they're miles ahead of scripters on OSBot, RuneMate, and other bots. The staff on the Tribot moderation team seem much more humble, patient, and professional, than the staff I've seen on other sites to. Tribot's development team actively pushing the technology further, with makes for a much higher quality product. How to properly start botting; Whatever you're looking to bot, there's some basic principals you should be following. To start, I typically look for a script that has been updated within the last month. Some scriptwirters may argue that "Nothing has broke, my code is flawless!". That may be an accurate case, in some statements, but more often than not, when I trust that argument from them, I find bugs, or not-working features. A recently updated script ensures new features are being added (even small anti-ban tweaks to keep things fresh), and bugs are being fixed. Sure a scriptwriter may push a fake update to just make it look recently update, but I have more faith in the Tribot script developers than to do that. Next up, no free scripts. Now that that's out of the way, since Tribot has limited quantity of scripts, this may not be an issue, but in case it ever is, if you see two different scripts of the same category (two fishers for example), look at the description of the scripts. Which scriptwriter has more information on the features of the script? Go to the Tribot Premium Scripts sub-forum. Which scriptwriter has a better thread on their script? Which scriptwriter is responding to, and fixing recent bug reports on the most recent comments on their script's thread? Take all of these into account, when making a purchase decision. If both scripts look equal in quality based off the aforementioned, I typically used to go by the "Active user count", and go with the script that had less active users, as it has less people using that scripts specific anti-ban configuration, which in some cases, may reduce bans noticeably. At the time of posting this, you can no longer see this in the store, so just go with whatever script you find is best based off research. I also at the time of posting just found out script trials were removed. (mods if you change(d) this and are reading this PM me i'll update thread, imo, not the best idea), The main thing you should look for in a script is configurability. You want a script that has the maximum amount of changeable settings, from mouse speed, to how often the camera moves, how the camera is moved, modification to the ABC2 delay, etc. An ideal script lets the user manually configure and tweak as many settings as possible. Some scriptwriters argue that "Tribot generates it's own unique anti-ban profile..." bla bla. The uniquely randomized anti-ban profiles of anti-bot, can only go so far, and to force certain variables in certain ways, can allow for randomization in different ways, that in my experience, leads to a much better result when it comes to not being banned. If you're running multiple accounts, it's ideal to have a different configuration with manual variables, every roughly 5-10 accounts, to keep patterns more unique. Whenever you start botting, you should start with once instance of the script, on one account. Find a time that you can watch a TV show, do some work and check the PC every 15-30 minutes, or something like that, and run the script. Check to see if there's any bugs, if so, report them to the scriptwriter. You should never buy a script, press start, and come back 6 hours later, for the first time you run the script only. After you verify it works, run it for as long as you want. I believe that getting around 20 quest points will help keep an account more "under the radar" in the Jagex anti-ban system. It's best to avoid having multiple accounts botting in the same world, if possible (although I run 50+ accounts so that can be difficult sometimes). It's also better to log into lower population worlds, with the lowest ping relevant to your location, for maximum efficiency. If you have one account you want to max, manual intervention goes a very long way. Every few hours pause the script, move the camera around, click a skill guide, etc. I run the account I'm trying to max 24/7, with no manual intervention other than typing in chat. I believe purchasing membership with a credit card or PayPal yeilds a higher chance at a temporary ban, over purchasing with bonds or Twitch. I don't think it has anything to do with how much the Jagex system looks into the account though, just the consideration on punishment. Do not bot Tutorial Island, as I believe accounts are monitored heavily there, and I've had much greater success on accounts I did Tutorial Island manually on. Things you should configure in a script if possible (Scriptwriters please consider implementation, applicable to all scripts, Users take note); *Note, these should all be optional, with the assumption "Let Tribot Decide" still exists. Some of the below may seem extremely silly, or minor, but if the assumption that Jagex's system uses flags is true, we want as much randomization in the script as possible. Such a stupid feature as "Scrolling through quests", could be something that no other script does, and completely throws off the Jagex system. It's worth configuring anything you can. This isn't a complete list of configurable anti-ban's, only a suggested list that be configurable/configured. Variables (X resenting a configurable number): -Mouse speed X to X (Script variable up and down between the two) -Slider (starts in middle, default position) to modify how often Tribot moves the camera (5 options left and right each direction, to reduce/increase the frequency of camera movement). ( +/-1 50% more/less, +/-2 100% more/less, +/-3 150% more/less, +/-4 200% more/less, +/-5 250% more/less ) -Slider (starts in middle, default position) to modify how Tribot ABC2 delays are handeled (5 options left and right each direction, to reduce/increase the length of delays). ( +/-1 50% more/less, +/-2 100% more/less, +/-3 150% more/less, +/-4 200% more/less, +/-5 250% more/less ) Shout-out to @Aropupu and his aAgility script for having this function in a very similar form. -Scroll camera in/out X to X clicks every X to X second(s) -Keep camera zoom within X clicks of original camera zoom -Move mouse off-screen every X to X seconds -Scroll through Quests randomly every X to X minutes (ideally this would just click a random spot on quest tab, or achievement tab, or click list of mini-games if that tab is open, and just "look" at them for a brief second). -Turn on Run at X to X percent -WorldHop every X to X minutes -Worldhop when X players or more nearby -Go AFK (in a safe area only) every X to X minutes for X to X seconds -Switch music tracks (only unlocked ones, randomly) every X to X minutes -Join X Clan chat and message every X to X minutes (This would in theory join one of your bots private clan chats, and send random messages from a list of messages the user can customize) -End script after X minutes of not being able to complete expected action On/Off Toggles: -Moving mouse off-screen does not interrupt script actions (Only use when idle, click back to game as soon as/before action happens) -Option to use Middle-Mouse camera movement only, Keyboard only, or both -Use "Escape" key to close interfaces (Script should detect if setting not on, and enable it, if this is enabled) -Shift drop, with pattern options (Vertical, Horizontal, Zig-Zag vertical, Zig-Zag horizontal, Bottom-top Zig-Zag Vertical, etc) (Script should detect if setting not on, and enable it, if this is enabled) -Use "Function" (F) keys to change through menus -Disable Camera movement -Only hop to ✓(USA) ✓(UK)✓(GERMAN)✓(AUSTRALIAN) ✓(P2P) ✓(F2P) worlds (toggle which worlds it will hop to on/off) (Script should detect total level and only hop to those worlds if requirement is met) -World-hop when someone speaks -Use Stamina potions when running -Use ✓(Runes) ✓Teleport Tablets ✓(Rune pouch has all runes?) to teleport (This setting the three are toggle-able, and when teleport to varrock/camelot/falador/lumby etc is done, it will do via the selected method(s)) -Hover next action (if applicable) Private Scripts: Private scripts are a gold ticket to success in the botting world, if done right, and if money is put out to maintain them. A private script, for those ignorant, is a botting script that you pay a scriptwriter to write for you, and typically only you. The cost for a basic shark fisher with banking support may be around $200.00USD, something like a fully automated Zulrah script with gold-farming and Grand Exchange support could range upwards of $3,000.00USD or more. If you're considering on making a long-term bot farm, that you hope to make profit from, a private script is worth every penny. Whether it's fishing or Zulrah, a private script will almost always make its money back, if you specify what you want well, and have a competent scriptwriter make one. I have explored having "friends that know java" try to take a look at Tribot, and it's not worth it. If you want a private script, pay for an official Premium scriptwriter on Tribot to make one. You're not paying some Venezuelan to do a quest for you, the upfront cost will be substantial, because you are paying for a professional to go completely out of the way for your benefit. Working politely with a premium scriptwriter will yield you the best results. Proxies: Proxies are a benefit if you are running multiple accounts. Jagex will not directly ban you for playing 12 accounts on one IP, but it will absolutely make their system look into the accounts like a hawk. I have had a friend banned who was playing 15 accounts at once legitimately (crazy friend who played 16 hours a day, he never botted, not one of those "he said he didn't" stories. I run some accounts one account to one IP address, and many accounts two accounts two an IP. Even at two accounts to an IP, I see a very slight increase in bans, so I suggest no more than two accounts to one IP. Purchase your proxies from a reputable source, I personally use Virmach.com for proxies, their website is absolutely one of the most terribly designed i've seen in my life, and the web developers should be shot, but their proxies work great, at a fair price in the end. Don't look for cheap sketchy proxies, a private socks5 proxy will cost around $2-$4/month. In Conclusion: The best way to be successful when botting, is to differentiate yourself from the rest. Take the time initially to figure things out. Test a script, watch it for a bit to make sure it doesn't error out, and configure options to make the accounts run in a unique fashion. Communicate with the scriptwriters, on Tribot, from my experience, the scriptwriters are completely open to hearing about bugs, and do their best to fix them in a reasonable timeframe. Don't waste your time with breaks at all, use proxies, etc. That's enough for now, so please feel free to ask any questions in the comments, or simply leave your thoughts if you'd like Have a fantastic day y'all. Thanks, CyberWizard

Good read. Bump

Hi! There were a few issues in the latest version of tribot to do with loading the inventory correctly. I believe Fluffee has resolved this this morning so it should be working fine now. Feel free to leave me a message if you're having any further issues.

Tried the script again, no luck, restarted Tribot and launchend the script again, success! Must have been the TriBot update.

for LG (VIP-E) it will add up meaning if u bought vip now u will have 32 days of vip-e for scripts u will have 2 instances 1 which will end after 12 day and the 2nd one will end after 1 month starting the sec u buy it

There are currently some issues with tribot's CLI from their update last night. https://gitlab.com/trilez-software/tribot/TRiBot-Issues/-/issues/554 https://gitlab.com/trilez-software/tribot/TRiBot-Issues/-/issues/553 https://gitlab.com/trilez-software/tribot/TRiBot-Issues/-/issues/552 There are known issues with proxies, world selection, and providing only a login name (not a password). This should work as expected when those are resolved.

v1.3.4 Add tab support - theres two ways you can use this, auto batching or with the client column, both described below Add auto batching accounts to tabs (ex. if launching 20 clients and have auto batching enabled with 5 tabs a client, it will generate 4 clients each with a tab for the respective account) (heap size will be the sum of the heap size of all accounts in that specific client) Added client field column (all accounts with the same text in the client column will be launched within the same client as tabs, so the naming of the client is arbitrary and you can decide) Massive performance increase when editing the accounts table. Before it was refreshing the entire table on every change unnecessarily which caused some delay with large tables. This performance increase may increase usability enough to warrant upgrading to this version even if not using any of the other features. Fix numerous issues with proxy manager Add action to select inactive accounts under tools Moved proxy manager to tools rather than preferences Add importing accounts from tribot's account manager Add exporting accounts to tribot's account manager Add 'autocomplete' popup to account table column text fields to show values imported from tribot, for example account names or break profiles (note that you must enable this at under Preferences) Add 'check proxies' to proxy manager Add 'restart closed clients' which will restart any client that closes. This can be helpful if you ever experience your tribot clients crash, it will immediately be restarted. Note that you will want to make sure to disable this option when you actually want to close your clients or they will just restart. Add double click launch warning, if you launch twice within ~5 seconds Add exporting to text file (with choice of delimiting character, ex ':') Only scan for tribot path after loading initial save file (before it was scanning on every start up even if it already had a path in the initial save) Cache tribot path scan result Various small code imporvements/cleanups https://github.com/Naton1/Graphical-Client-Starter/releases/tag/v1.3.4 Will add some settings documentation section to the forums thread Note that a tribot update was released last night with changes to the CLI. There may be some tribot CLI specific things broken that I am not aware of. You can let me know of anything and I can look into it but I have already opened to issues regarding cli bugs https://gitlab.com/trilez-software/tribot/TRiBot-Issues/-/issues/553 https://gitlab.com/trilez-software/tribot/TRiBot-Issues/-/issues/552

Probably very low. Congratulations @Dentist on the script, good luck with future development.

Thank you very much for the update the scirpt starts perfectly now with an argument.

https://community.tribot.org/announcement/75-purchased-scripts-not-showing-up-here-is-how-to-fix-it/

Update: I've ran this script a few times now, major pog. Absolutely outstanding and efficient script, flawless, Dentist is King.

@CyberWizard Awesome, thanks for the shout out, and congratulations on your achievements!

Hello Everyone, Recently, I created a couple gradle project templates that can be used to start scripting with Tribot 12. Features: Automatically uses the latest tribot JAR. No config needed. Has automated tasks for: Compiling script to the .tribot/bin folder Deleting the bin Packaging your script as a .zip for repository upload Has a run configuration for debugging your script in Tribot. Prerequisites: At least know what Gradle is IntelliJ IDEA An understand of how scripting for Tribot already works Links: Single script template: https://github.com/WBScripting/tribot-script-template Multi script template: https://github.com/WBScripting/multi-script-template Video: Note: The error I got near the end of the video while building has since been fixed via the template FAQ Q: Can I add other gradle/maven dependencies from the internet? A: No. Those dependencies will not get properly built or packaged correctly to run in Tribot Q: Is this required to script for Tribot? A. No, it's simply a convenience tool

@Nukem updated

I've started to archive the source from as many former scripter applications as possible to provide an easy to access resource for new scripters looking for source to read. It's not complete, and some scripters have already deleted their source so it'll be impossible to recover. But with any luck new scripters will find this helpful as an excellent place to get started Get the source here!

Creating this thread to provide an easy way for me to link new users to my tutorials, as well as have them all in my Signature, without making it obnoxious. -- Fluffee's Ultimate Guide to Botting Series -- -- General Tutorials -- -- AutoHotKey Releases --

EDIT ->>>>> okay the script works fine now i dont want refund sorry

ah yes back when prices were fair

still work ?