Zach

Yes both local and SDN

This is a development release focused on security of local scripts, but also affects SDN scripts. Historically we've been one of the most open and welcoming bots for any new scripters. However in recent weeks, we're aware that there have been instances of malware in the local/downloadable scripts section. This has led us to reconsider our position. To protect our users, we've chosen to begin activation of the security systems we've been developing for both local and SDN scripts. It severely limits the abilities of scripts to damage your computer in a number of ways. For example, it: -Blocks reading/writing any files outside the OSBot/Data directory. So scripts will no longer be able to access files all over your computer and any of their configurations will be limited to that directory. They will continue to have access to the temporary files directory. -Blocks Robot to prevent native use of mouse/keyboard -Blocks full screen capabilities to prevent spoofing your desktop -Blocks creating new classloaders that could further load malicious code -Blocks runtime permissions and native library loading -Etc. We have chosen to continue allowing limited reflection use and unrestricted internet access for the time being. We believe that unrestricted internet access won't be as significant of an issue with the new restrictions, but we will continue to monitor it. If you need additional permissions for something, let us know in the Client Bugs and Suggestions section. Scripters can post in the Client Bugs and Suggestions section or the thread in the Scripters' section. 2.4.55: -Fixed bug with loading local scripts -Removed deprecated constructor from InteractionEvent -WebWalkEvent handles Area destinations -Patched WebWalkEvent spamming final destination tile 2.4.56: -Fixed more bugs -It will now block the attempt and stop the script instead of printing that an attempt could have been blocked. -Please continue to report any additional permissions you need.

You should be able to now, thanks @Maldesto for fixing that.

Strange, someone with the same rank as you just posted a few days ago Could you try again?

I would let the scripters of the scripts you're using know. Keep in mind scripters also add their own links which changes the original webwalker's behavior. So if you're having trouble, the first thing to do is file a report with the scripter, who can then determine the whether the cause is OSBot or the script and forward it onto us. Once we verify it's a bug in the client, then we can fix it. If you're having trouble with it on your own script, then you can file your own bug report here.

Webwalking fixes

Keep in mind the above posts by @Maxi is not explicit approval for the script to go on to the SDN. Maxi merely stated that we would not deny it simply because it combined many skills.

They're being recompiled

Scripts should be recompiling as we speak

Should be up

Boo

Changed thread ownership and author of OP to @Khaleesi.

You were hit with a delayed ban. So, it wasn't the client. Logging into a legit client would have produced the same result.

At least we have the decency of saying it and putting it into a single checkbox. I do think it would have been more beneficial for anti-detection to remain silent about it, but we'd rather be upfront about data collection. We can't reveal too much unfortunately. But I can say that no identifying information related to your RS account is sent.

Added the info, you can go to the launcher's "About" tab and there's a checkbox there for it.

Firstie.

Corrected and extended time by 72 hours

Silent fix

Moved to mirror. A silent fix went out

Version? Steps to replicate? There is a template, follow it unless you can provide sufficient information without it.

Strange, hooks haven't changed so I'm not sure what the problem is. Any thoughts @MGI?

PayPal informed us that there was unauthorized activity on the account and we subsequently removed it. This is something you'll need to resolve with PayPal.

The Area is better. walking.walk(Banks.EDGEVILLE); The reasoning is outlined in here

It is. Have coins in inventory or quest done.

If you guys have a bug report, make a bug report. That way we can track it and assign it accordingly. I'm removing every post associated with general questions or bug reports since this isn't the appropriate place for them. Take that to the appropriate Help section. I'm ok with reports for bugs that were introduced with this version as it is relevant. For people who are unable to open a bot because of the "Session has expired due to inactivity or VIP is needed to run multiple bots..." The latter (background OSBot process) is the most common cause and something you should check before filing a bug report. Submit a bug report in the appropriate section if you feel there is a bug. Thanks for letting us know. The Al Kharid gate will be solved once we finish obstacle handling.