Zach

That'd be great!

Until I get them or until someone provides an account inside the random.

Updated sprite_index_1 hook. Things that depend on it should work fine now (such as world hopping).

.95 has fixed running away from combat random.

Oops, it's because Jagex decided to split up the GAME stuff. I'll implement an isGame() immediately. You should be able to call message.getType().isGame(). Or if you have a type id, you can call Message.MessageType.forId(type).isGame().

onMessage() wasn't completely fixed in v.90, so another attempt was made in v.92.

The actual list isn't getting released publically to prevent biased reports. Since there were multiple internal methods that were broken, a list of the ones directly editted wouldn't be of much use because it'd only cover part of the anti-randoms that would actually be functional.

.97 Fixed Pillory Cage. Thanks to @Ericthecmh and @darkxor. Link: http://osbot.org/forum/topic/45180-fix-pillory-cage/ .96 Fixed Prison Pete exiting (thanks to @irwtonrs1 for providing the accounts) Added isVisible() check to Bank.isOpen(). March 31, 2014 1:18PM PST: Updated sprite_index_1 hook. World hopping should work fine now (it was broken due to broken logout method due to a broken tab method due to the hook). .95: Fixed running away from combat random. .94: Added Message.MessageType.isGame() to replace "MessageType.GAME" (which has been removed). You should be able to call "message.getType().isGame()" or if you have a type id, you can call "Message.MessageType.forId(type).isGame()". .93: Fixed SurpriseExam exiting. Added MessageType for clan chat. .92: Ok, apparently onMessage() still has some problems with it. It MAY be fixed in this version. Scripters: If onMessage() says that it's an unknown type, please PM what you were doing to me. .91: Fixed onReceiveTrade() (thanks to @Divinity for helping)! .90: Fixed onMessage(), hooks, and some randoms (prison pete thanks to @Ericthecmh).

It's getting transferred to Pandemic as Toph has given him rights to it.

Since you're already basically on the topic, you should bring up Java's evaluation strategy (pass-by-value). A lot of people tend to confuse references passed by value with the pass-by-reference strategy.

I don't think reverse engineering it is necessary, but if someone wants to do it and post their findings, that's fine by me. Just make sure you've got it in an isolated environment or know what you're doing.

What are feelings? In all honesty, I don't like messing with the forums too much, that's why we have Maldesto and Raflesia!

It was always intended to be unlimited for all scripters, but apparently that wasn't the case, so that's why it got fixed today.

I think you're mistaken if you think that a lot of the best programmers care that much about ranks or e-peen. I do agree that there are a lot of the ones in the middle or the younger ones that will care. Working towards a rank just seems outrageously stupid. How about working for the advancement of the world instead?

I tend to agree with that as well. The whole idea of lifetime scripts doesn't work when scripters just abandon scripts all of the time. I'd propose leaving the current scripts "grandfathered" into the current system and making everything from now on based on a monthly fee (or every ___ months or whatever) for ___% of the original price. There needs to be more regulation in the area though, because at the moment, we pretty much allow free market rules to prevail, which apparently doesn't work very well.

v1.7.87 Updated: Prayer configs Added: (hopefully these remain stable) ObjectDefinition: getModifiedModelColors(), getOriginalModelColors() NPCDefinition: getHeadIcon(), getOriginalModelColors(), getModifiedModelColors() ItemDefinition: getUnnotedId(), getModelId(), getNotedId(), getOriginalModelColors(), getModifiedModelColors() Hopefully, hopefully I didn't miss anything.

Just a notice (for anyone that doesn't want to verify everything), all of the fixes made in OSBot 1.7.80-1.7.86 were merged with OSBot 2.

For those that don't already know, OSX 10.9.0-.1 Mavericks has a SSL security vulnerability. Users currently not on 10.9.2 should update immediately (the update was released earlier today). Users running 10.8 Mountain Lion are not affected. This vulnerability essentially gives hackers the ability to intercept SSL/TLS traffic for any software using SecureTransport (this includes most/all Apple software, such as Safari, Mail) provided that they are in a "privileged network position" (e.g. running the network). Chrome and Firefox are not affected as they use NSS instead of SecureTransport. Obviously the consequences of this are far reaching since HTTPS traffic was no longer secure. Generally speaking, the protocol is used to secure information (such as your passwords, credit cards, and other sensitive information) transmitted over the internet. Yes, I know Apple took their sweet time writing what should have been a quick fix. But, that may have been due to merging the other updates in 10.9.2. And yes, I know that if they did a simple dead code search, this problem would probably never have come up. Things happen and we don't know what ultimately allowed such a bug to slip through, so let's not jump to conclusions quickly.

We do listen, but obviously we can't listen to everyone. At least I'm being truthful about it and saying it instead of hiding behind political speeches. It's not arrogance as much as acknowledging limits and prioritizing. Does the President of the US read every message that's sent to him? No, it's filtered tremendously. Same thing here. We prioritize and openly admit it. The only people that should have problems with it are the immature people who have yet to realize that life is all about prioritizing, or just don't know that this type of stuff happens everywhere. Anyways, we listen to the most reliable providers of information that we can find, which usually happens to be scripters. They do get feedback from users on things, including randoms, and if they have issues with it, then we also hear about it. But if it's limited to some reports that have not been confirmed by known trusthworthy sources, then they may not have even bothered to forward it on and there is little point in spending resources on it. That's especially true when our own bots are telling us that there are no problems. Even if we did get reports, our bots are working fine, so there is no way to fix an issue that doesn't exist for us. If they were confirmed/collaborated reports, then sure, we'll see if we can try to get that specific random, but otherwise, it's not worth the effort. Sorry I burst your bubble on how everyone is treated perfectly equally in life, but someone had to do it eventually.

We still get updates from it from time to time. But when none of our bots are running into issues, it's generally assumed to be functional. If you've written a script, then you know how users can somehow report issues that don't really exist. Hence, why we only check from time to time and check if it correlates with other findings.

Truth be told, none of the devs read the Errors/Bugs section unless we're directed to because of the insane amount of useless threads in there. Perhaps the day we get a Noob Error section, we can have a clean section to read. Until then, we rely on information directly from scripters.

And people should also be banned for posting general things, such as something needs updates, fixed, etc. without details. It's worked perfectly for me, so I don't see any need for updates.

Tbh, it should be mandatory that everyone include a version whenever they post a problem.

v1.7.86: Combat tweaks (hopefully it helps improve some scripts having problems with combat) Prayer sprites

One Sith