Zach

The native code was implemented and copies given to certain Script Writers. Immediately prior to public release, it was removed as to not break support for Sponsors and VIPs who may have legitiment uses for having multiple windows. Since then, usage based on server monitoring shows that it isn't as bothersome as we originally believed, so it's back on the backburner. As it's not a particular secret method for detecting Sandboxie, I'm just going to post some of the code. Ignore my camelcase conventions that I tend to use for practially any language. char* sModule[] = { "SbieDll.dll", "dbghelp.dll" }; bool isInSandbox() { for(int i = 0; i < (sizeof(sModule) / sizeof(char*)); i++) { if (GetModuleHandleA(sModule[i])) { return true; } } return false; }

ESET NOD32 had the same problem in early 2012. You can read about it at: http://www.wilderssecurity.com/showthread.php?t=317320 I suspect we're dealing with a similar issue and that it is a false positive.

Since I don't remember any development admin posting, I'll confirm that the bot will remain free (as Maldesto stated above). We have no plans to change the free version of the bot at this time.

It should be working fine now. Laz pushed the fix last night.

I don't think I've gotten any messages from him. If it went to Maxi, he's been busy with other things, so that's probably why he didn't get a response. At the moment, your best chance is to get a hold of either Laz, Kati, or myself.

It is fixed. It was tested and verified by multiple people. In any case, the areas that were previously unclickable work fine now. Perhaps there is another glitch involved or you're attempting to click on an unclickable part of RuneScape.

Fixed unclickable areas on screen glitch. Fixed model heights. Fixed lever ID for prison pete. Added MethodProvider.realDistance(Position) and MethodProvider.canReach(Position). Added Client.isMinimapLocked(). Fixed a bug with interface clicking. Fixed NullPointerException in Frog Queen. Fixed Molly. API uploaded. A downloadable ZIP version of the API can always be found at http://osbot.org/api/api.zip. Sincerely, The OSBot Team

Yea. Fix is underway.

That's correct so far. We do promote people to the rank if their script is good and they want to sell it.

RuneScape stores your username and password. Normally, for security purposes, OSBot blocks scripts' access to this information. Prior to this version, there was a problem with that security system and it could be bypassed by placing the code in onStart() rather than loop() or onExit(). It has now been resolved.

Added closestAttackableNPCListForName(). Some internal changes to reduce CPU usage. Fixed a security issue with scripts. Some anti-random tweaks. Sincerely, The OSBot Team

There were some issues with it, for example, it would fail to return an object you were standing on in certain cases. There were other issues as well. I'm kinda glad Laz decided to afk for a bit and I started debugging. Once he got back, we were able to fix the problem and make sure it made it into this release.

Then it's not in the directory you're trying to run it in. I've done this multiple times and it works fine.

If there is a space in the path of the .jar file, then it will cause the command to file. You can make it work by ensuring that there are no spaces or using quotes.

Could you be more specific? Instead of just posting that it doesn't work, include details (like a log) and where it fails.

Instead of saying "_____ doesn't work", can we start including debug logs? That would be extra nice

The bot works fine. It's the script that needs to be updated as some object IDs (including bank booths) have changed. There is nothing we can do to help you there.

Mordaut doesn't have all of the questions and answers programmed yet.

Ask Jagex. As for the currently not working randoms, we rarely get those randoms, so it's quite difficult to develop them without access to accounts in the random. In any case, @Maxi is starting another round of randoms busting, so we should see some account submissions and improvements. Realistically, the best way to speed up the process is to submit accounts (not to me until next week, I'll be busy).

294 wpm actually. No subtracting 40 wpm! I just assumed that since it was a group of cheaters, everyone was cheating. So, I cheated to even out the playing field :P.

If it makes you feel any better, the bot does consider you VIP.

Congratulations! Enjoy the free month of VIP!

Ah, my bad. http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html There you go!

It's on the homepage like always. But I'll add it to the first post! http://osbot.org/

The issue with misclicks should be fixed now. Thanks to @ProjectPact for helping us test! Download is on the homepage at http://osbot.org/