LightningCrash

there was 1 2 day and another perm ban lol.

Yeah you can continue to talk shit and say this, you will soon realise that you will be chainbanned and then you will eat your words. Jagex can detect any botter at ease. Yeah right, half the people at pest control bank bot magic/alching and the majority of them don't get banned. Also there are tonnes of people botting fletching at the G.E. right now, not banned. I did only use flicking rapid heal. Also you're the one whose a moron, running 4-5 accounts on 1 ip. LOL, any smart botter would tell you that you're absolutely idiotic. I'm not going to sit here and argue with someone since this thread is to do with the script itself, not for people to spam argue with one another so yeah.

Yeah, you tell me why people selling tutorial island accounts are using residential proxies then. And yes, if you're using your main IP, you're more likely to get chain banned. I've run the script for 100+ hours no issues, like I said its only recently that Jagex has taken action. I used prayer flicking and I didn't use breaks. Like I say, its not about doing something wrong. If I did something wrong why would I only get banned after like a 100+ hours of using the script rather than within the first 24 or so (which has what happened quite recently). Its evident that Jagex are able to detect NMZ botters at ease.

I can safely say that this script was running 60-100+ hours straight no bans no nothing but it seems that Jagex mods are able to easily detect when someone is botting NMZ, not sure if this is due to click patterns or what, but I feel that there should at least be something additional added to maybe get maximum potential out of this script and keeping bans to a minimum. There is no break feature included in this script and I think it would be a nice addition mainly because I'm not 100% sure if the OSBot break would be able to detect to finish the NMZ game before taking a break as I wouldn't want a break to interrupt an NMZ game if I am in one.

Ok so if I get a manual permanent ban for botting then you explain to me how Jagex detects what macroing is seeing as you know so much about it. I have used accounts that have never been botted before. Also, you have to also know that botting over the weekends is more likely less chance of getting bans seeing how jagex employees mainly work weekdays. I've only ever botted these two accounts at NMZ using this script. It's only within the last week or so that they've been putting "manual bot busting bans" Also as for you claiming I get flagged and l2bot, I find it incredibly funny considering I bot my accounts using residential IP proxies. And separate residential proxies per account.

I used one account in world 346, and it got a bot busting ban (2 day ban), when I got the account back, i continued using it in the same world and I got a Macroing major ban (leading to a permanent ban). I also used one account in World 343 and that account also received a bot busting ban (2 day). Please note that bot busting bans are always manual bans (meaning they've been given by a Jagex Moderator) whereas a Macroing ban can be either automatically given or given by a J mod. Before these bot busting bans, the script was working pretty much flawlessly running 24/7 with 0 bans. It's only recently that bans have become more frequent. And so adding something which makes it less suspicious to Jagex Moderators is needed to make bot busting bans less frequent.

Hey, so due to the recent bot busting streams and bans, I've noticed an increased rate in bans. Would it be possible for you to maybe add in a feature which allows users to avoid certain worlds. From what I've noticed, some worlds seem to be more monitored than others and, if using the world hop feature, I don't really want to be hopping to monitored worlds when doing NMZ games.

That account is less than 70 defence so it cannot even wear verac's. Next time I run it and it gets to wave 59 I can try and get that for you if you didn't end up fixing it already. I'm just annoyed that I ran it like 5+ times and it always died on that specific wave. It usually safespots the 180s whenever possible but it doesn't on wave 59. It simply needs to run to the nearest safespot possible so it can hit the 180 without taking much (if any) damage.

This script is kinda broken. It got to wave like around 59 multiple times and then started literally running into the level 180 and kept dying. Please fix this... It literally runs and gets hit and dies and it is super fucking frustrating to die and lose millions in supplies due to this stupidity. Image: