Leaderboard

Hey, This release brings the new ui to stable. Below you can find the entire change log since the previous stable release. API CHANGES: - Removed widget caching from world hopper, quests, logout tab, GE and shop api. Please let me know if you notice a difference and if it's on mirror or injection FIXES: - Plugins work again. - Fix GrandExchange scrolling not working. - Added dismiss all randoms setting back. - Fixed the worldhopper hopping to league worlds & sometimes not hopping. - Fixed an issue where input wouldn't re-enable after stopping the script. - Fixed the configinterface performance issues. - Fixed -autologin cli argument not working without the -login arg - Fixed an issue with quest completion loading - Added a missing break condition check in the worldhopper. - Fixed cli args for script and username/pass not working if there are spaces in the name (Usage of "" is required for names with spaces eg -script "script name":args) - Fixed a bug where the break manager would start during the welcome screen WEB WALKER: - Fixed the issue with trying to interact with obstacles (doors/gates/stairs) that shouldn't even be on the path and getting stuck. - Added PathPreferenceProfile#setAllowQuestLinks to enable/disable quest requirement links (default enabled, fairy rings are ignored) - Added Femi dialogue to the gnome stronghold gate MISC: - various small UI fixes - Break profiles tab has been redesigned. Profiles can now be toggled to be active/inactive and can also be saved. Also fixed a bug where they weren't being activated. - The logger can now be cleared. - Added the option to use the hardware mouse. This has been added to see if using the hardware mouse has impact on banrate. From our testing it's looking promising. It will limit you to 1 tab which needs to be on the foreground at all time. For security reasons, it's not possible to disable human input and pressing the escape button will imidiately stop the running script. Pressing backspace will pause the script. For more information about how this works, check out https://docs.oracle.com/javase/8/docs/api/java/awt/Robot.html - Added a link to the mirror guide on the startup page (WIP). - Minor bug fixes. - The OSBot team

WooWoo

CzarScripts #1 Bots LATEST BOTS If you want a trial - just post below with the script name, you can choose multiple too. Requirements Hit 'like' on this thread

Preventing RS Botting Bans V3 Written by Alek 1. Introduction This guide is Version 3 of my original guide released 4 years ago. I decided to focus more on commonly asked questions and general misconceptions about botting. Many of the topics are very technical and there are brilliant engineers who both bust bots and create them. The majority of botters who come here have little to no programming experience, or very little knowledge in subject areas such as reverse engineering. It’s very difficult to fully explain all key concepts, however hopefully this material will give you a base reference to draw your own conclusions. 2. How to not get banned The secret formula to botting is keeping a very, very, low profile. This game has been around for 15+ years, that is a TON of data to play with. Generally speaking: -Don’t bot more than 4 hours per day -Don’t bot more than 10 hours per week -Diversify your tasks -Don’t use a VPN/VPS/proxy -Don’t bot more than one account -Do quests -Don’t RWT/goldfarm -Don’t bot in hot spots, use places like Zeah You’re going to have a ton of people say, “oh I suicided for 11 years straight, never logged out, I make $500k/year”, etc. They simply don’t. Either they haven’t botted long enough or their claims are baseless. If you want to keep your account relatively safe then don’t bot longer than the times I recommended above. Time played is a key factor into profiling a bot, it’s been even talked about on official livestreams during live bot busting events. 3. Misconceptions The biggest misconception is that the company doesn’t have any automatic detection systems. Although the detection vectors improve over the years, there are official statements claiming that all bans are manually reviewed before being issued. THIS DOES NOT MEAN ACCOUNTS ARE NOT AUTOMATICALLY FLAGGED. Common situation: Suicide bot on the weekend without getting banned, account gets a ban on the following Monday or Tuesday. This is because your account was probably flagged over the weekend, then eventually reviewed for the final determination on the following business days. Another misconception is that if you “survived the weekend”, then you are safe. This is certainly not true, most anticheat will "flag and monitor". This means that you were in fact detected but the anticheat is watching your actions very closely to grab more information about what you are doing. Information from these monitoring sessions are used to quickly detect and ban in the future. For Runescape, one example is the use of bot worlds. Another non-Runescape example is Valve-AntiCheat profiling numerous hacks over the course of months and then issue behemoth ban waves all at once for games like Counter-Strike. 4. Antiban/Antipattern Scripters who include antiban/antipattern methods in their scripts are either naive, new scripters, or are trying to earn more sales by making false promises. Competitor clients further this perpetuation by forcing script writers to implement these methods. It’s a gimmick and overall you’re going to get banned whether you use these "special methods" or not. Some of these “special” (aka worthless) methods are: -Moving your mouse randomly -Checking your exp -Examining random objects -Moving your camera angle randomly -Implementing “fatigue” systems -Diversifying the way you interact with objects One of the special methods I’d like to talk about which was not listed above was randomizing sleep time between actions. This is especially special because there are numerous flaws with it. 1. Your computer doesn’t perfectly execute actions in the same time every time 2. Your script doesn’t perfectly loop in the same time every time 3. Your ping fluctuates causing a delay between the client and server 4. If the top three all remained constant, you could find the upper and lower bounds of the mean and use statistics to recreate the sleep time. Anti-pattern is a bit different, but a lot of scripters have been wrongly claiming their script having “antipattern” when they’re really using the same “special methods”. Examples of antipattern: - Talking to other players (Cleverbot) - Mixing up tasks (perhaps after accumulating X gold, go to the Grand Exchange and sell) The goal of anti-pattern is to reduce the chances of being manually reported by other players for botting. Although “antipattern” is more desirable than “antiban”, there is still no definitive proof of the impact it has in the total picture. 5. Client detection 5A. I’m going to keep this relatively brief because this is probably the most technical aspect of this guide. There is an overarching debate over Injection vs Reflection and it’s pretty silly. Both are detectable because both have different ways you can detect it. In the non-Java hacking world, this would be equivalent to something like ReadProcessMemory versus LoadLibrary. To better put it, reading memory from outside the process versus inside. There are ways to hide it, ways to find it, ways to hide against the ways to find it, and ways to find the ways how to hide it against from finding it. As you can see, it’s really cat and mouse and it boils down to implementation. 5B. Additionally, you can be detected for macroing without even using a client. You can banned for using Gary's Hood or AutoHotKey. Both of these use some sort of Windows API function like SendInput, from protected mode. This is how color-bots also get detected without injecting/reflecting the client. 5C. Mirror Mode adds some protection to users where the normal OSBot client can be detected. Think of mirror-mode as a safety catch rather than a comprehensive antiban measure; and yes mirror mode has genuinely protected users at least on one confirmed occasion. In summary, you will still get banned because mirror-mode only protects you from one aspect of botting and there are potentially hundreds of detection vectors. 6. Conclusion and final remarks Having good botting habits like I outlined in section two, and having a good script which is reliable and not prone to getting baited (locked behind doors, etc), is your safest bet. There are people who do “studies” and “research” but ultimately their results are inconclusive, non-definitive, and certainly only proves a correlation and not causation. There are too many variables to isolate to make any data worthwhile; ip address, computer, scripts, clients, botting locations, skills, account time, bot time, quests, RWT, java exceptions, client detection, the list goes on and on. Too many variables to isolate, too much that we cannot prove. The bottom-line is that the only people who know specifics about the anticheat system are the anticheat developers.

Soo Okay, here i am again. I just made an other account and it got perma banned after running 1,5 hours of Zealmining. i had the breaks on ON and standing on randomize bot/ break time. I think this whole Botting thing turns out to be useless because everytime you try it there is a bann attached. Update the software to their ays of catching people r stop letting people download this bullshit. Don't advertise on faulty stuff

Enjoy!

Sure! Enjoy

somone els having the error that cant login because login server is not aviable ?

got it done

Sexy client is finally main stream

Hey, So far 2.6.1 has been getting a lot of positive feedback This version improves upon the new ui based on user feedback. Download link: http://osbot.org/devbuilds/osbot 2.6.1.jar FIXES: - Fixed an issue where input wouldn't re-enable after stopping the script. - Fixed the configinterface performance issues. MISC: - various small UI fixes - Break profiles tab has been redesigned. Profiles can now be toggled to be active/inactive and can also be saved. Also fixed a bug where they weren't being activated. - The logger can now be cleared. - Minor bug fixes. - The OSBot Team

Sure enjoy!

You literally just got banned with your last account for agility which is one of the most dangerous skills to bot and without breaks enabled. On next day you make new account (I assume you made that on the same IP as IP where you got banned?) and next day you start, I suppose on fresh account with level 3? Don't you think its weird? Also I don't want to say anything bad towards to the free scripts, but they are free and they aren't as powerful as paid ones. For me, I used Perfectminer by @Czarand botted with it 10+ hours a day without breaks (if i can remember right) and never got ban for it What break times did you use this time? Please also read: https://osbot.org/forum/topic/124429-preventing-rs-botting-bans-v3/

Time Ran: 20h 43s | Current Lvl: 87 (+3) | Profit: 3.2M (158.8K/hr) | NPC Caught: 3106 | Exp Gained: 877.2K (43.8K/hr) | Time TNL: 8h 54m 53s

Have fun!

yes it was win 7, I changed computers and it is running ok. I have run it previously on win 7 on that computer so I dont know what the issue was. I have them on win 10 machines now.

I know, I was just thinking how the year is almost over already 0.0

240 on 120 off proggy with slight random variation

May I have a trial?

couldnt wait had to buy it XD

OMG this looks amazing and i get trial thanks!

Hey Czar, I must say this has been my number 1 FAVORITE script for years. It is generally amazing and flawless, I have one request as of now with the new League game mode. Is there any chance we can add the crystal of memories to the teleports? There are so many areas where this item would be useful in!

This can be simplified very nicely RS2Object trapdoor = getObjects().closest("Trapdoor"); if (trapdoor != null && trapdoor.interact("Open", "Climb-down")) { Sleep.sleepUntil(() -> !trapdoor.exists(), 5000); } Once you are in the dungeon, the trapdoor no longer exists, so the sleep condition covers both interactions.

is there a feature where it will auto log in the wilderness when a player is around, if not will it be implemented? is there a feature where it will auto log in the wilderness when a player is around, if not will it be implemented? (if safe spotting)

he actually wasn't the one who did it, we hid 3 other posts before and it brought it to the top.

How can I buy this script? It does not appear to me in the shop

Was just giving an example. Just check if the object still exists in that case ^^ No need to make things hard, keep it simple and stupid. Never use Onmessage for this kind of things, not very reliable.

The bot leaves the game before getting the rewards for no reason and banks. Is there a way of getting a refund for this script paid for it when it first came out and havent been impressed with it at all.

looking forward to free trial!!

there is an iron man mode, check the description, its f5 i think? also if you have x item in your bank that is required to start the quest it wont try and buy it

Can i have a trial period, really wanna try this script out before committing to it. mining script ofc

May I get a trial? Will most likely purchase.

can i get a trial please

Can i get a trail please?

I have the script set up to stop when slayer task complete but it doesn't. Bot keeps attacking monsters which is not good in slayer only areas. Is there a fix? Also it doesnt high alch specified loot while i have the runes in my rune pouch. Is the rune pouch supported? if not could you add it?

W10, i5 3.4ghz, 16gb ram. Hiding paint doesn't seems to change anything. Tried spinning wool at lumbridge and crafting necklaces at edgeville, same thing, one bot uses around 40% cpu lol idk why. And if I make task to spin wool till level 5, then go to egdewille craft necklaces, after bot reaches level 5 goes to bank, opens it and whole client just freezes, can't acces logger, have to kill process

Could you also add the feature of eating to full health at the bank, then withdrawing food?

Which ever one is easier to implement, and an option would be great. Thank you!

Well. I managed to Unban 2 accounts. Both at 94 Crafting xD. Theyre currently doing something else. But plan on getting them back to crafting on Monday. Providing the Dev Version is fixed for breaking.

Hey bro, one thing I noticed that botting on fresh account is almost a guaranteed ban, a fresh account usually stays from 2 days to 1 week. Also, when botting try to bot at places where there are no people around and try to do some progress with other things don't just bot melee for a whole week. Of course, scripts are important factor, i recommend using Khal and token scripts. Don't take breaks like a 15min break every hour I find that stupid. I usually bot for 4hours no breaks then log off for 2-3 hours, and bot for another 4 hours doing different activities. Never bot at night, you never know what's going to happen. I know most of these things seem known, but the biggest factor that worked for me is the age of the account. I think fresh accounts are heavily monitored on the first weeks of creation. no matter how safe i bot i get banned a week later, i managed to get 1500+ accounts just relying on the age factor alone. hope this helps. (OH one more thing, I'm not really sure about botting botting on an update day, but i usually avoid it.. u know, better safe than sorry).