Zach

I suppose the code was considered monetary contribution...

Fixed the image tags as requested on http://osbot.org/forum/topic/38853-selling-rs3-main-2400/?p=444729

I fixed it for you, but for future reference, make sure the file extension exists in the URL (jpg, png, etc.). You had a few image tags that didn't have them.

Alrite, I'll look into it to see if anything's changed and update it if necessary. I don't have a lot of time so no promises.

Which script is this? It could be a script issue so being specific does help. I know Ande's fighter has the problem and that's because it hasn't been updated.

Or you start a race to the bottom (worst proggies possible). Kinda like negative posts.

Oops fixed.

Read the post above yours. It isn't the client's fault. It's the script since they implemented their own setRunning().

I said it before, but a lot of scripters like to write their own methods. This is probably a case where they wrote their own setRunning() method instead of using bot client's. So you may have to wait for the scripter to update their scripts.

Then it's possible that the scripter wrote his/her own setRunning() method so that the one provided by the bot is not used. Because the bot client's works perfectly. I know this is true for 's scripts (not calling Mrsdefnerd out here, I'm just giving an example, there are others as well). So you may have to wait for the scripter to update their scripts.

v1.7.84: Fixed setRunning() due to RS update.

I've never had a problem with that, is there a reliable way to reproduce it?

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).

Mumble

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.