Maxi

Hi! Enjoy your stay ;)

Please report any bugs you encounter after my updates from yesterday. I ran it for over 4 hours without experiencing any bugs, so let me know!

If you don't like it, use the old theme. If you don't like the colour scheme, change it. Anyways, I hope you will enjoy playing with it while being banned for scamming one of our community members.

I must have missed a couple of bugs in the new softening system. I'm currently looking in to it and I'll update the script in a bit. Sorry for the inconvenience. EDIT: It seems that the bugs are caused by some client modifications by Jagex. I'll go through them and add appropriate fail safes for them. EDIT2: I have updated some things in the script and it runs smooth again now, damn you Jagex. There will also be an update in the client where there are some failsafes added to randoms in the case a bucket or clay is still selected, which will be pushed later tonight or tomorrow. I've ran it for over half an hour now without any issues. I also discovered a minor bug that influenced the clay / hour, it turns out it was calculating a much higher clay per hour than it actually softens. I have added further improvements and fail safes for several scenarios, amongst which for example is a fix for randoms and banking.

Dear community, We're happy to announce the release of BETA v1.7.9. In this version the following updates are pushed: All random events will now check whether you have an item select on activation and if you do deselect the item Some security improvements Freaky Forester has been updated, however not verified For now the dependencies (down)loading has been ditched to fix the loader issue a minority of the community has been facing Sincerely, OSBot.org

First Name: ~ Relationship: Single, sharing my bed with sweet ladies when I go out Stuff you do: Surfing, programming OSBot, Computer Science studies, FIFA, fraternity stuff Favorite Food: Too many to list If you could be anyone (fictional or real) who would you be: Steve Jobs (only for a day) Thing that takes up the most of your time: My fraternity, studies, OSBot, surfing, friends Where do you work: At home What country do you live in: ~ What Subjects did you do at your highest qualification: Computer Science

The script sometimes sits for a while and does nothing, but it will continue after some time. For now you can note it down as anti ban. If people want to, I can remove it. As for the banking, I'll look closer at the code to see if that's the case. For the running, it does run. About lummy basement, don't you need to have done some quests to use it right there?

Ely

It was not exploited and is now patched, so more reason for you to use the latest version ;).

Updated the script, some minor issues fixed.

Clay currently is ~100 ea, soft clay currently is ~280 - 300 ea. Depending on the clay / hour you're getting (will eventually with randoms etc go down to 1.6 - 1.7k per hour), it's around ~280 to ~320k per hour.

Maxi's Super Clay Softener. Simple but effective. Instructions: Start anywhere near Edgeville bank, with clay, without clay, with soft clay, without soft clay, with empty buckets, without empty buckets, just make sure you have enough clay in your bank and buckets in your inventory. Make sure you run the latest version of OSBot. 14 buckets is believed to be the fastest setup. Repository link: http://osbot.org/forum/store/product/30-super-clay-softener/

You are crossing a line here, you're are not allowed to do this.

I have updated the script and will add it to the SDN later tonight. I've also improved the mechanics of the script a lot, boosting the clay per hour by A LOT:

Added on to our list of nice future features.

I won't even start correcting the post directly above me, been there and done that too many times with others, yet I'll summarize it for you. This is all based of assumption and research but one part will never be proved as we don't have Jagex their source code, there are two aspects to this entire story: One, The RS server (up to revision 570-570'ish, this doesn't apply in clients with GPI updating and on) handles its players in some form of collection where it loops through to when creating the update package in order. You login and you will receive the first empty spot in the collection, this can be 1'st, this can be 1000'th etc. Being earlier in the collection will get your player's actions processed first, which is believed to possibly create a gain over the other in interaction (in this case, staking) but there has never been hard prove for this. Two, your internet connection. Data over the internet travels with a limited speed, based on overhead in your router, based on overhead in your computer, based on overhead on the link between two connected nodes etc etc. Obviously, if your connection with the RS server is better than your opponent's, chances are that your data will arrive at the server earlier. This still doesn't give an advantage, unless the following happens: the connection from the opponent is that much slower that it arrives at the server end that much later that it gets processed one server tick cycle later (their server ticks at 600ms). In that case, you see a difference between animations, one player being attacking the other a tad bit earlier giving the advantage. The story about IP's, in all honesty and no offence, is completely wrong. Also, PID = player index.

You could have bought runescape gold man... Why didn't you buy runescape gold?

Hi everyone, I'm posting this thread to give you all a heads up why Laz, Zach and I have not been around for the past 3 days. OSBot will continue with the same dedication, all three of us had to attend IRL duties (family, studies, etc..). Usually this never happens on the same days, but this time it did. Kati held our force strong! Sincerely, OSBot.org

Like Zach mentioned, can we please start including logs from the log file because we can't do anything if we can reproduce your issues, if we don't have your log files.

It was patched on 1.7.1.

Due to the recent update from Jagex and some other important matters I have to delay this devoted day to friday/saturday.

Hello everyone, We are proud to announce that BETA v1.7.1 has been released! Today when I got online RS just updated and we managed to update the bot within no time. There were 2 broken hooks of the 200 we have, these were patched up shortly after. Two days ago we decided to do some research to find a reason as to why there has been a higher ban rate recently which affected several bots. We have made OSBot less detectable. Another interesting not is that we have separated some of OSBot's dependencies from the jar. The client will now download some of its dependencies on startup if they have not been downloading before. This reduced the size of the jar from 14MB to 5MB. Also, the client will now for everyone to run Java 7 to prevent the countless help posts about this. With this version we introduce the usage of a color picker and access to the colors of the canvas in case you need it in specific cases. This can be found in the Client class. Furthermore, world hopping has been added and is very easy to use in your script: worldHopper.hopWorld(world); To continue with awesome features, OSBot now support breaking and is completely handled for you and it's written as a RandomEventSolver to give you easy control over the mechanism from your script if the bot is not ready to break, for example if it's still fighting. And then we also added a fully fledged config debugger to make config debugging as user friendly as it can get: For randoms, due to the recent events of the last couple of days, most work on finishing up the last bits to make them 100% altogether has been delayed slightly. However the following randoms have been updated and have been verified to work: Frog Queen (outside cave) Maze (broke after the update, it has been programmed more securely to survive future RS updates) The issue with the order where random event solver were evaluated in is fixed now. Besides all the aforementioned updates, there have been many more updates that I currently can't think of. Expect us to work on randoms in the coming days to make sure every last one of them works as we expect them to work. Thanks for reading, OSBot.org

I'll look in to it once our main priorities with updating are done

They should use closestObjectForName() methods for everything that has a name and is possible in its current context, this way changes to id's won't affect scripts. Some scripts have no other choice, however they could use information about models for example to catch this.

More like 1 hour after . We will look into the issue of the login screen.