Apaec

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

Hey, I think this might be an issue with the latest OSBot version, 2.4.137, where the script executor does not resume... I had this happen as well, for some reason after an event such as a login event, random dismissing event or such ,the script does not resume execution. This did not happen when I was using 2.4.136. There's nothing I personally can do really, since my code isn't even running at this point - I will see if this problem is occurring for other scripts and then file a bug report if necessary. Ugh. Apa Edit: Yep, can confirm that this is the case for all scripts, other scripters are aware and a bug report is pending. Please stay patient!

Update: I've found the problem, it was quite silly really. A simple threshold change fixed it - I've added the fix to the latest version, V3.04, which is awaiting verification before it goes live. Please allow 24 hours for this - you will know when it's live as it will say V3.04 in the paint. Until then, please do not use breaks with the script! Thank you very much for reporting it! Apa

Hey, Not sure why it would do this, as I recently tested the break handler which should take you to safety before breaking. I will run some further tests now... It might be an issue with OSBot 2.4.137 which was made stable recently. Thanks for letting me know.

I'm sorry to hear that, this is the reason Mirror mode is still in Beta!

*Update* With some instability on mirror mode caused by an issue with a combat related API call, this update is a temporary 'fix' to the problem, removing the call altogether until the developers find the time to take a look. Version 3.04 Removed isUnderAttack() calls as these were causing issues on mirror mode. As a result, combat detection will be slightly less accurate, however the script will now *hopefully* work reliably on mirror mode Added CLI support, see main thread for more details! Cheers Apa Edit: Please give up to 24 hours for the developers to verify this update and push it live.

Hey guys So i've looked in to the issue and it seems to be related to mirror mode - the API isn't happy about something. I've posted a client bug report here: https://osbot.org/forum/topic/129404-bug-characterisunderattack/ Unfortunately there's nothing that I can do to fix this directly as the problem appears to be with the mirror client. I'm going to experiment with removing the faulty client call and seeing if the script can get by without it, but that would certainly be a temporary measure. For now, PLEASE USE STEALTH INJECTION! Apa