Zach

That's interesting, I suspect it's a side effect of PayPal now blocking eChecks that are going to OSBot's paypal (like 25% of eChecks were actually legit, so it does make sense). That came into effect some time in the past week, so it's highly possible. I'll have to look into this though.

You can pretty much copy and paste an updater these days. It used to be that having an updater meant something because of the effort/knowledge involved. With multiple open-sourced ones, it's become much easier to just guess a pattern until it works. And that's the reason most of them are unstable.

How dumb can you guys be? That code is used to prevent scripts from running getPassword() method (i.e. prevent local scripts from stealing your password). Learn to reverse engineer. I'll even post the code here.

Would it be a good idea to have an example repository set up? I'm just tossing around ideas at the moment since doing that would require at least some code (unless we just use blank files).

You can have folders inside of your src folder for packaging. If you use an API library, you can store those in your "dependencies" folder (more details were mentioned in one of the threads). If you need more information, just let me know.

Did not expect 2 of those people... You and Maxi don't have auto push??? I assume you guys would even though you don't have scripts. I don't think Maxi really deals with pushing scripts. But, I think not having an SDN script implies that we can't auto-push [our own scripts]. But you're entirely correct that both of us do have access to push scripts. You're probably clean because the code seemed to specifically target Windows machines. The scripts were disabled as soon as we became aware of the possibility. So, the bot will never show you those scripts. You can check the Client Area in the forum to see, but it should still be there provided it hasn't expired or something.

For the sake of transparency, the current people with the ability to automatically push updates to the SDN are: @Alek (duh) @Ericthecmh @Laz (duh) @SXForce @XavierM

You guys can thank beastlymaul/GoldenGate for giving me a PIN, which then resulted in me noticing the problem and moving to correct it ;p.

Wat

Unarchived.

For people having issues with v1.7.47, this version can be temporarily found at http://osbot.org/get/osbot 1.7.45.jar.

@pyroryan Did I guess correctly?

We've always had IRC #osbot on rizon, just that no one uses it these days (it died after chatbox came out).

Identities of the scripters that are permitted to bypass the process will be revealed for transparency purposes once they've all been chosen.

Some of the active script writers have requested the ability to bypass manual pushing and code verification. This has become a burdensome process for some of the active ones, especially since it can take hours to complete the process and update the script on the SDN. I'm happy to say that we've reached a compromise and will authorize certain scripters to bypass the process, enabling their SDN scripts to be updated within 1 minute of them pushing an update. So, what does this mean for the end user? We're sacrificing code verification for our most reliable scripters and giving them the ability to more rapidly respond to any changes. Hopefully, that means more stable scripts for our end users.

Restart it a few times. If nothing works, delete client.jar there and keep trying. I had the same issue and it seems like it had more to do with Jagex's servers.

I didn't. I only disable versions if there is a significant flaw with them. With 1.7.36, you can still run essentially flawlessly using certain scripts. Randoms should generally be about the same between the two versions. So, nothing significant enough to compel disabling it.

v1.7.38: Some API stuff related to messages that XavierM wanted (I don't remember). v1.7.37: Fixed getHealth() (for combat) and selectEntity() (looting issues included). Sincerely, The OSBot Team.

Combat issues and a lot of randoms should be fixed. Older versions are disabled because it's obviously not a good idea to leave something unstable running. Thanks @XavierM for bringing it to my attention. Sincerely, The OSBot Team

Why? Maybe cuz jagex updated runescape? Maybe because there was already v1.7.34 and in 15 minutes, boom v1.7.35. I'm just curious about little changes. 1.7.34 was pushed to server at 11:47. 1.7.35 was pushed to server at 16:44. I wonder how 5 hours became 15 minutes.

I'm not completely convinced this is stable yet, but I'd like some feedback on it. Thanks.

Shutting this down while we investigate a few things. It may take hours, but it's for the better good.

I've already noticed the issues. I should have tested first lol.

I suppose I'll leave up the random stuff for a few hours. Usually I only leave it up for a few minutes.

To Whom It May Concern: This is a letter about stuff. Sincerely, The OSBot Team