Zach

Seems to still have a <1% chance of screwing up with the mouse (at least with my limited test scenarios anyways). I'm testing a fix currently.

Seems like there was an issue with the mouse changes where it would think it failed when it didn't, I'm pushing out .83.

I spent quite a bit of time tracking down some obscure bugs and some of them were fixed. v1.7.86: Combat tweaks (hopefully it helps improve some scripts having problems with combat) Prayer sprites v1.7.85: More mouse optimizations and @PolishCivil reasons. v1.7.84: Fixed setRunning() due to RS update. Previously (after RS-update still), if you had data orbs enabled, setRunning() would work. However, if data orbs were disabled, setRunning() would mostly fail. If setRunning() still fails, the scripter uses their own method and you'll have to wait for them to update the script. v1.7.83: Fixed an issue with the mouse changes where moveMouse() thought it failed when it did not. v1.7.82: Fixed a few issues causing freezes. setRunning() now uses data orbs when orbs are enabled, otherwise, it continues to use the settings tab. A couple other obscure issues were fixed. In general (for .82-.83), if you're not affected by a bug that causes scripts to freeze, there is no need to update. Thanks to @FrostBug, @pitoluwa, and @TheScrub for their assistance.

We're handling this in a PM.

v1.7.81: Fixed issues with closestAttackableNPC() that was causing the bot to click on recently killed NPCs (thanks @Swizzbeat and ).

v1.7.80: Mandatory update due to changes in RS. v1.7.81: Fixed issues with closestAttackableNPC() that was causing the bot to click on recently killed NPCs (thanks @Swizzbeat and ).

Just Do It

The "main class" of every jar (if one exists) is stored in the manifest, so you can find it. And you can just do java -jar anyways.

We haven't been stuck in a random for a while now. I've asked around and the idea that randoms are broken doesn't seem to be the case. So, unless you've got something more specific than "broken randoms" when most of them have already been confirmed to be functional, we're not going to take any actions. The talker worked perfectly fine when we were testing the bot for 24+ hours. There is no bug in that anti-random that we know of.

v1.7.79 Slight tweaks to walking. Some minor changes to internal threading (working on the crash bug, I haven't been able to replicate it since with 2 hours of testing, so provide feedback on this).

I haven't been able to replicate the setRunning() bug in .78 (which was when I tweaked it), so I'm going to consider it fixed until otherwise informed.

Hmm, I guess someone didn't push his fixes for that. Doesn't matter, I fixed it and I'm uploading it as 1.7.78. Edit: Uploaded.

Worked fine for me. Such as?

I don't work on OSBot 2 beyond helping when asked. So I have no idea what the progress on that is.

Some fixes with this version. v1.7.77 Withdraw-X should now select the option if it already exists (or enter in a value if it doesn't). Prevented a few infinite loops associated with logout. Character.isUnderAttack() modified so that it now checks for a valid attacker (using isFacing() and HP > 0). I don't know if this is going to cause some problems with bosses, so if it does, please let me know. v1.7.78 setRunning() fixed. v1.7.79 Slight tweaks to walking. Some minor changes to internal threading (working on the crash bug, I haven't been able to replicate it since with 2 hours of testing, so provide feedback on this).

We're doing our best to make sure these fixes won't delay the OSBot 2 release. But either way, it's quite near!

Maldesto has the same permissions on ACP as I do. For non-ACP stuff, it's more programming oriented or secured by multiple layers, so I usually have to get involved at that point.

Not going to happen. There are enough idiots trying to get ranks and it just wastes time. Besides, we generally already know who is good and deserves it. And pretty much everyone that applies would be underqualified so there isn't really a point.

Sorry, but I must ban you now.

The move to the new system basically only transferred auths that were given by Maldesto, Alek, or myself. I believe a new tool is going to be released that will be in compliance with the new system, but I have no ETA on that at the moment. If you purchased it, you're fine.

It could in theory happen, but without a security manager in place, the chances of it happening are about zero.

There is nothing to push, so I assume Alek took care of it.

The entire idea of an updater relies on patterns. How else are you going to do it? Manually? Even doing it manually relies on patterns. Your brain recognizes specific patterns of loops and such and puts it together to form a bigger pattern. In short, every single strategy that's been used in an updater is going to rely on patterns. Using a reflection explorer is perfectly acceptable, but keep in mind that it's still limited in capability compared to direct refactoring. It's a good starting point nonetheless.

v1.7.64 only contains a hotfix for people having trouble loading up the game. If you're not having problems, there is no need to update.