DylanSRT

How would I go about doing that? Do I put something in my On Exit? I don't know how to control the client, just the script. Thanks

Hey guys, I've noticed that if I stop my script in the middle of a while loop, the next time I try to run the script it is still in the while loop. So it basically runs two instances of the same script at the same time which obviously screws everything up. I would expect that behavior if I paused the script during a while loop and played it, but why does it happen even after completely stopping the script? The only way I can get the script to run normally again is by restarting the client. I'm sure some of you more experienced scripters know a way around this. Thanks!

Fair point, but A. Do you really trust what Jagex says? B. This was likely due to their ability to detect injection. Mirror mode is used by a very small percentage of botters overall I would say. It's just a hassle for many people to open clients manually. C. If you took the number of flagged accounts of people using mirror mode and then further narrowed it down to people that are online at the moment and then even further narrowed it down to people who are in hotspots for botting, I think it would be a manageable number. And they wouldn't come back to an account until they went through the whole list (so maybe it would take a few days or maybe a few weeks to check back up on the same flagged account). D. If they truly had some sort of magic code it would have to be for a popular script. Otherwise, how could you possibly make a code to detect something that you don't even know you are trying to detect. What other information could they possibly code to determine you are 100% a bot other than the client you are using? Even if you were playing for 48 hours in a row, how could they determine that you were botting unless they manually checked? It would explain why many people have gotten away with even using simple mouse macros and clicking on the same pixels over and over again. It all comes down to the client.

I've made 3 other bot account since I noticed this and none of them have been banned still. In the past, almost every account I made using the same exact botting schedule has been banned within a week. But this is the most significant trend I have ever noticed with ban avoidance, and I've made A LOT of accounts to farm various things. I would suggest everyone try it themselves and see if it works for you. Obviously this isn't an exact science and there are possible exceptions. Nothing is 100% safe. Maybe an employee stays late one day and catches you. Maybe they have designated people in America and Australia working so that they have all 24 hours of bot monitoring (doubt it). At this point though it has definitely left the realm of coincidence and become a solid trend for me. Read the new paragraph I added about why it logistically makes sense for them to do bot validation in realtime.

I created 5 member accounts about 6 months ago to test some of the factors that I thought would affect bans. Some of my discoveries have been very helpful for my bots so I thought I would share. All of these are with mirror mode btw. If you are still using injection in this day and age, you deserve to be banned anyway. Developers have openly stated that Jagex has had or might still have a detection method for injection (screenshot below). Whereas mirror mode is like using a mouse macro with much higher capabilities. It is my theory that Jagex has to manually check your bot to determine if it is botting if you are using mirror mode. The only decisive auto-bans (without validation by a Jagex employee) occur when using injection because they can detect your client. As people have noted many times before, botting on new accounts has an extremely high ban-rate. One of my lvl 3 accounts was devoted to botting only 1 hour per day (different scripts every day). And it was still banned within a week. I tried a couple of other things and they did not help avoid bans on a lvl 3. But then, I decided to try avoiding botting during Jagex working hours (8am - 7 pm to be safe). I know people have mentioned it before but I never saw anyone definitely saying if it worked or not. I ran custom scripts on this level 3 account 4 hours per day for 2 months outside of Jagex working hours and had not been banned. Then, I decided to bump it up to 8 hours per day, and still no ban. This is pretty much unheard of on a lvl 3 new account. If you think about it, it starts to make sense. They probably have a couple of employees devoted to just going through the flagged account list all day to determine if those people are botting at the moment. I also think new accounts are automatically added to this list (up to a certain amount of playtime, levels, quests etc). I'm sure they have access to tools and metrics to expedite the process of determining if you are botting in realtime. It would explain why you can get away with botting sometimes for a long period of time. Maybe you were just getting lucky at the times they looked at your account and you were not botting. But, eventually they will catch you in the act. It would also explain why they made worlds to put suspected botters in. These worlds could have different parameters to make it easier for a Jagex employee to determine if you are botting. Logistically it makes sense too because it would take up so much space to collect data or even video of suspected botters. It would be much cheaper to just do it in realtime. So like I previously stated, if you are using mirror mode, I think that your account can definitely be flagged for factors like playing for too long, reports, new account etc. However, even with a flag, it must be validated by an employee manually so you cannot be auto-banned. The only exception to this might be for very popular bots. They could buy popular scripts on this site to create code to identify them and this can lead you to get auto-banned even without an employee validation. I am currently testing the same thing using SDN scripts instead of custom scripts to see if it makes a difference. TLDR: Use custom scripts (non-SDN) outside of Jagex working hours on Mirror mode to avoid being banned on a level 3. Try it for yourself and let me know.

Has anyone actually noticed a decrease in bans if avoiding botting during Jagex business hours? Is this a real thing?

Hey @Maxi, I'm using the following the stream to identify an NPC but keep getting a weird exception occasionally while interacting with it. It only happens sometimes and it can usually be fixed by pausing and unpausing script. It has also happened to me while interacting with Ground Items and Entities as well. I am also 95% sure that it is caused by right click interactions only. So that might be why it is less common. Also, I know the script worked fine at one point (like a month ago) but I'm not exactly sure which update caused it . Token suggested that it is a Mirror mode issue. Could you take a look? Thanks private Predicate<NPC> myCat = n -> n != null && n.isVisible() && n.hasAction("Chase") && !n.isAnimating() && basement.contains(n); cat = npcs.getAll().stream().filter(myCat).min(new Comparator<NPC>() { public int compare(NPC one, NPC two) { return Integer.compare(getMap().distance(one), getMap().distance(two)); } }).orElse(null); if(cat!=null){ cat.get().interact("Chase") } Error executing event : org.osbot.rs07.event.InteractionEvent@348ff5 java.lang.ArrayIndexOutOfBoundsException: -2922 at org.osbot.rs07.api.NPCS.getLocalNPC(dn:178) at org.osbot.rs07.api.Mouse.getEntitiesOnCursor(tj:401) at org.osbot.rs07.api.Mouse.isOnCursor(tj:65) at org.osbot.rs07.input.mouse.EntityDestination.evaluate(pg:286) at org.osbot.rs07.event.InteractionEvent.IIIIiiiiIIii(zi:185) at org.osbot.rs07.event.InteractionEvent.execute(zi:349) at org.osbot.rs07.event.EventExecutor$2.run(le:246) at org.osbot.rs07.event.EventExecutor.execute(le:171) at org.osbot.rs07.api.model.Character.interact(pl:464) at RatCatcher.onLoop(RatCatcher.java:131) at org.osbot.rs07.event.ScriptExecutor$InternalExecutor.run(bp:22) at java.lang.Thread.run(Unknown Source)

Nope, I never use stealth injection =/ . My guess is you are right though. Do you think whoever works on mirror mode can take a look at it? It's not just NPCs. It happens when interacting with Ground Items as well.

I'm using the following the stream to identify an NPC but keep getting a weird exception occasionally while interacting with it. It only happens sometimes and it can usually be fixed by pausing and unpausing script. I'm pretty sure it is something wrong with the API because I did not have this issue earlier. Can anyone deduce what is going on or suggest a fix? private Predicate<NPC> myCat = n -> n != null && n.isVisible() && n.hasAction("Chase") && !n.isAnimating() && basement.contains(n); cat = npcs.getAll().stream().filter(myCat).min(new Comparator<NPC>() { public int compare(NPC one, NPC two) { return Integer.compare(getMap().distance(one), getMap().distance(two)); } }).orElse(null); if(cat.isPresent(){ cat.get().interact("Chase") } Error executing event : org.osbot.rs07.event.InteractionEvent@348ff5 java.lang.ArrayIndexOutOfBoundsException: -2922 at org.osbot.rs07.api.NPCS.getLocalNPC(dn:178) at org.osbot.rs07.api.Mouse.getEntitiesOnCursor(tj:401) at org.osbot.rs07.api.Mouse.isOnCursor(tj:65) at org.osbot.rs07.input.mouse.EntityDestination.evaluate(pg:286) at org.osbot.rs07.event.InteractionEvent.IIIIiiiiIIii(zi:185) at org.osbot.rs07.event.InteractionEvent.execute(zi:349) at org.osbot.rs07.event.EventExecutor$2.run(le:246) at org.osbot.rs07.event.EventExecutor.execute(le:171) at org.osbot.rs07.api.model.Character.interact(pl:464) at RatCatcher.onLoop(RatCatcher.java:131) at org.osbot.rs07.event.ScriptExecutor$InternalExecutor.run(bp:22) at java.lang.Thread.run(Unknown Source)

Actually only since Sept. Here's a post from when it first happened after an OSbuddy update. The weird thing is, if developers have the ability to make their client incompatible with osbot, why doesn't Jagex itself try to do it too lol.

It's been like that for like a year now haha. You must have been taking a hiatus. Only official osrs client works with mirror mode atm

If you used Paypal, you can manage any preapproved payments on your account and cancel anything at any time. It's really convenient to see all of your monthly bills in one place and have the power to end any agreement. I don't know what the limit is for non - VIP is but it's pretty hard to be able to run more than 4-5 bots at once on one PC. It leads to a lot of memory storage problems and bots won't be able to run for a long time. Four is a good number imo.

@Explv This script might be the best money I have ever spent on this site. So simple yet so useful. The map integration is genius too. Makes questing on low levels so easy especially ironmen. One really easy thing you could maybe add is a way to disable running. That way one can slowly walk somewhere and go take a shit or something and have 100% energy when back ?

@Token Amazing script, inspiring. Ran 15 quests the other day without a flaw and the only reason it stopped was because of Christmas event which changed the npc's dialog. While I'm here I had a quick question. When we make changes to a script on the SDN, do we need to notify you in anyway after committing changes or is it automatic? Thanks

Hey @liverare, Thanks for the advice. I actually do have it in a separate class for my own but like I said I wanted to make it super-noob proof in this post since many people start off with just the basic script skeleton. I'm glad your post is up now so they can learn how to use separate classes. Btw your two GUI tutorials basically taught me how to make GUIs so I'm a big fan !

I suppose so, but in other areas they have still been sharp (if not sharper) than they have been in the past. For instance I've noticed it has become very difficult to bot on a new account without like 2 weeks worth of actual and productive play time. I never had so many bots banned at low levels as I have recently.

I always thought NMZ would be easy detection by Jagex for bots so I avoided ever using it until about a month ago. I had a spare bot testing account leftover so I was like fuck it I'll just make a quick script for NMZ to see how far I can get him. I wholeheartedly believed it would be banned in a day or two because I was going to push it.... Fast forward one month and not only have I maxed Att, Str, and Def , but also ranged with addy arrows lmao. This entire time, I pray flicked at a rate of 600ms without any variance. So literally the bot would click every 600 ms on the dot for hours only stopping when it needed another dose of overload. I was getting close to 135k xp/hr towards the end. I got 6 hour logged at least 25 days in the past month so I basically suicided it but not a peep from Jagex. I could understand that it would be hard to detect human vs bot if I was only clicking to overload every 5 minutes. My hypothesis is that for this reason, Jagex just stopped monitoring NMZ altogether. You can get away with anything in there. Despite using 5 very low points bosses, buying herb boxes every day, and not turning on zapper or recurrent damage, I still ended up with a fuck ton of points: Have you guys had the same experience? I should note however that this account was low-lvl but it had been made about 2 years ago. So it may have avoided bot detection due to it's age. I had three different relatively new accounts banned WHILE this bot was running at NMZ rofl. Like they actually got disconnected and were banned while this bot was running on the next tab. And that happened three different times. They were all doing much less obvious stuff. This is why I know for a fact that they don't IP flag. Their detection is truly befuddling. It explains why some people have had better luck with mouse macros than OSBot, and I believe it. It seems like the most obvious stuff easily slips under the radar. One thing I know for sure is that if you have any old accounts laying around, use those to bot instead of a newly created one. It seems to have a big impact.

@Czar @Eagle Scripts Thanks boys, that means a lot to me coming from two legends !

I got tired of creating paints for every bot so I decided to created an AIO paint script with the goal of minimizing input needed to customize a paint for a certain script. I also wanted it to be noob-proof and easy to implement into any script. I know I could have used something like this when I first started making scripts. If you use this template in a SDN script, I would appreciate it if you left my signature in the paint. I spent a lot of time creating this topic when I could have easily kept it to myself. Features: Automatically detects exp gain in any skill and adds it to paint (if using a script which does not gain XP, it will automatically hide this window) Displays current lvl, starting lvl, XP gained, XP per hour, % to next level, time to next level, and has a progress bar to next level Automatically self-optimizes window sizes to fit required text based on only two inputs - font size & text padding Displays script name, time ran, current world, and number of current players on map by default Has easy input for custom counters and automatically adds them into paint Hide button to hide paint & Reset button to reset the XP counters Displays big warning indicator when other players use certain keywords (bot,reported,etc..) 10+ Optional color and font settings Demonstration of Paint, Hide, Reset, & Warning Indicator: How to implement into any script: Please follow these directions carefully. Use Spoiler 1 (Script Skeleton) as your guide. This will show where user input is required and where to paste code from other spoilers (indicated by %%%%%%). The default settings of the paint will come out looking like the paint in the video. Spoiler 1 (Script Skeleton) Spoiler 2 (onStart) Spoiler 3 (onPaint) Spoiler 4 (onLoop) Spoiler 5 (Used methods) Spoiler 6 (Additional Variables) Adding Custom Counters: In addition to the default features of the paint, I made it very easy to add in custom counters. You can do this using customInfo settings in the Script Skeleton. They will appear underneath the "Time Ran:" timer. Just add the String you want in the caption and the Variable it is referring to into this Array in the same manner as this example. You have to make sure your counter/state variable is properly initialized and updating information in your onLoop. Make sure to set customInfo=null if you don't want to add anything. Don't just delete it. By default, the counters will not reset when the Reset button is pressed. If you want them to reset, you need to add some code to the MouseEvent in the used methods spoiler. Going along with the example above, this is what you would need to change it to: Font Size & Text Padding: These settings are the only inputs you need to use to control the size of the paint. Below are some pictures of different combinations: baseFontSize=14 & textPadding=5 (Default) baseFontSize=10 & textPadding=1 (the Space Saver) baseFontSize=20 & textPadding=10 (the IDGAF) - You can see this option would actually push the paint out of the bot with the skills paint activated, so this would mean that you need to reduce your size. However, this could be a viable option for bots that don't train XP.

Yeah, but it just popping up out of the blue could also mean that Jagex changed something in their client. Perhaps something that can only be triggered by a Java script and therefore they can tell you are botting. OSbuddy and Runelite don't even work with OSbot. If you were working at Jagex to bot bust, wouldn't you rather lay some mines in your client to catch people. I have taken all Object streams out of my scripts for the time being because that seems to be trigger. I would advise everyone to do the same.

Be careful with that exception. I got banned on one of my very safe botting accounts soon after I got that on a custom script. I was testing out detecting some objects in tithe farm that the Entity API couldn't pick up. I honestly think it might be something that Jagex bot detection can pick up too. Maybe they are finally deciding to put up a fight against Mirror Mode. Hopefully someone with more Java experience can enlighten us. @Token any insights on this? I had like 10 other accounts botting much more rigorously on the same IP, but for some reason only the account which I used to test this script got banned after I started getting the exception frequently.

You are probably using Osbuddy or Runelite. You have to use official RS client from OSRS website. Don't have any OSBuddy or Runelite clients open when adding a bot either.

With mirror mode, they have no way of detecting from the client that you are botting. Basically, it is like using a mouse macro but with much higher capabilities. So really the only way you can get banned is if you over-do it or people report you and a mod manually looks at it. With client injection, just using the client can give you away and this has been my experience with many bots.

Notice how he says "less bans" which leads me to believe that the detection flaw is still possible, but reduced.

I can't believe you've done all of this and still haven't realized that client injection is your problem.. Mirror mode nearly maxed on iron, almost everything botted except for slayer. Alek even said that he recently patched a flaw in the client injection that was causing detection by Jagex. I still wouldn't trust it though. Don't even log into your account once on client injection, use purely mirror mode and watch you will not get banned. They can detect you if you use injection even if you are not botting. Don't even log in to play legit on injection. A couple of times when mirror mode was broken, I made the mistake of using client injection on one of my pures. They always got banned, but the accounts that were exclusively mirror never did. Even with same ip.