Apaec

They know that if they ban all the bots, they would lose lots of players, damage the economy, and lose out on huge profit margins from membership I think they definitely have the resources to know pretty consistently who does and doesn't bot, they just selectively ban people to make the more dedicated players feel better! Edit: I think in the end it is a compromise - if they ban too many botters, they risk damaging the game. If they ban too few, they risk damaging the game

well now you know what not to do!!!!

Do you not test stuff before you push it live

walkPath does not handle obstacles walkPath does not generate a path so presumable less cpu/ram, although neither use a huge amount walkPath is more reliable as it is not required to generate a path Rule of thumb: Use walkPath where possible, use walk for very short distances (i'd say no more than 10 tiles to be safe), use webWalk if the place that you're walking from is unknown.

It looks like MGI has pushed an update to mirror allowing the debug text to be hidden (big thanks!) - as a result, the script should now be compatible with mirror mode. Cheers Apa

Gosh, mirror mode never wants to be happy... This looks like an error with the client walking/run enabling, I don't think I can provide a workaround for this though. I'm not sure what else I can do but pathwalking and run handling alongside that is a pretty vital part of the script, and removing it would be more than problematic. I just ran some mirror tests and was getting internal errors all over the place. It seems mirror mode just isn't happy at the moment, and i'm assuming that due to the lack of replies to my mirror bug reports and the section in general, mirror mode has stopped active development (for whatever reason). Unfortunately there's really nothing that I can do to help if the client is receiving this level of neglect, so you will have to switch over to Stealth Injection for the time being. (It's probably safer / equally dangerous anyway). Cheers Apa Edit: Just spotted that MGI pushed an update to mirror about 8 hours ago, perhaps this might be the cause of some issues. https://osbot.org/forum/topic/129492-mirrorclient-v25/

Hey Please could you elaborate? I've been running with version 3.04 now very reliably, haven't had any issues on either Stealth injection or Mirror. What exactly is the problem you are having, and is it occurring on script version 3.04? Apa

Hey, Not sure what the problem is but this did not fix it for other people either. Sorry I couldn't help! I don't seem to be having any problems though strange that it is happening to some users and not others. Apa

Woo 5th! (:

Hey, Thanks for showing interest! Mind I ask - exactly which script do you wish to trial? -Apa

Sorry I couldn't help ): I'm not sure why the bug report section is closed

Odd I've not been having any problems and my scripts list loads just fine. Try re-downloading OSBot, and if that fails, try deleting your OSBot directory? Apa

Copied reply from: https://osbot.org/forum/topic/129464-script-selector-freeze/

I think a faulty script might be the cause of this issue; try removing all of your SDN scripts and adding them back one by one until you find the culprit! ... or I could be totally wrong. Just a thought! -Apa

Cheers (: Yes, this guide is look overdue a re-write. Hopefully I can find time in the coming weeks to work on it! Apa

Sure, done! (:

Hiya Klix, the script is using the OSBot walking system when resetting. While this system allows some customisation, unfortunately what you've mentioned is not one of them. Short of writing my own walking system, there's nothing I can really do about this. If I were to write my own walking system, I would be sacrificing the stability, simplicity and support that the OSBot system provides so it is something I would rather not do! That being said, I think how people navigate is very subjective. I spam click as you mentioned that you did, however observing streamers and other players, i've noticed many more people seem to walk until their character is almost stationary before continuing, just like the current walking behaves. Either way, I think in terms of bans, that is the last thing to worry about - instead I would focus on botting sensibly with frequent and generous breaks and short daily sessions! (Btw, if you haven't already, be sure to check this thread out: https://osbot.org/forum/topic/124429-preventing-rs-botting-bans-v2/) Cheers Apa

Yeah, hopefully Version 3.04 will fix your problems. Here's the bug report https://osbot.org/forum/topic/129404-bug-characterisunderattack/ . In version 3.04, isUnderAttack is no longer called and alternative methods for determining combat status are in use. It's frustrating, but mirror mode is still in beta and far from being as stable as Stealth injection, so sometimes scripts may not work on mirror as you would expect. Cheers for understanding! (: Apa

I wouldn't play through OSBot if you can help it. You probably won't get banned, but as no-one really knows how jagex detect bots, you're unnecessarily risking your account. As Juggles said, OSBuddy or another 3rd party assistant client!

I've managed to re-create this behaviour... unfortunately it's a pain to test for since there's no way to check if under attack as calling that causes the script not to work in mirror mode -> lots of angry VIP people. I will try and think of a workaround without opening yet another async thread, but that may well be what is needed in the end. Apa

Hi Which refresh issue are you talking about? There are currently two issues out there, both client issues, one specifically on mirror mode. Does your account continuously try and refresh back and forth, or is it completely stationary? If it's the former, i've pushed a temporary workaround fix for it while the developers look in to the issue (Script v3.04). If it's the second, I believe the recent OSBot v.2.4.138 has fixed the issues which were present in 2.4.137. Apa

Heya (: I noticed you have VIP, as a result this script is free to use for you. Check it out! Apa

Hey, Please refer to the announcement below! This is a client issue and the devs are aware. Cheers! Edit: it seems Alek released 2.4.138, hopefully the issues were fixed ! Hmm, I was not aware of this behaviour :o, please could you tell me exactly how I can re-create it so that I can write a check & fix? Thank you Apa Hi, please refer to the announcement in the reply above! Essentially it's a client issue, the developers are aware and the issue should hopefully be fixed in the next client version. Edit: it seems Alek released 2.4.138, hopefully the issues were fixed!!

Awesome stuff, glad it's working well & hopefully you've already made your money back! (: -Apa

Announcement: The client is currently having issues with Random/AutoLogin events as of Version 2.4.137. This means that, occasionally, this script (and all others) will not resume after an event executes. A bug report has been submitted; please be patient while the devs look in to the matter. Meanwhile, please babysit the bot at all times with this in mind. Regards Apa