Leaderboard

It has come to the attention of the OSBot Team that the main developer of vInsert, Discardedx2, was involved with logging all usernames and passwords of his community. We'd like to warn anybody who was registered with vInsert and used the bot at all to change their passwords immediately. We'd also like to state that OSBot is a professional operation. We are soon going to be a registered company in the Netherlands and that we would never engage in something as low as hacking our own members. However, due to the recent hacking, we are going to be increasing the security we have implemented in the OSBot client itself to make sure that a situation such as this one would never be able to happen on OSBot. This includes implementing multiple styles encryption such as MD5 and RSA to protect your passwords. Moreover, to reassure your security, all of your passwords are encrypted and salted using MD5 on our database. This means that we do not know anybody's passwords, rather, when you are logged in, the MD5 hashes are compared for authentication. The developers of OSBot, Maxi and I, are reputable members of Rune-Server. I'ed like to say that honestly hacking our own members accounts would not benefit us in anyway. We hope that now that vInsert is dying, OSBot will become the #1 bot for OSRS. tl;dr: Change your password if you've ever used vInsert. Sincerely, Laz and the OSBot Team.

its cool. If you keep people informed then i doesn't matter if the update get delayed... And we understand that the personal life have an impact on the bot...

I'm sorry for the delay of this release. I have spend more time than initially calculated to do a couple of these updates, and today and yesterday our country was completely in party mode because of the crowning of the new king, an event I of course had to attend. I will work as hard as possible to get this release out within 2 days.

Here's a method I wrote: public int experienceForLevel(int level) { double total = 0; for (int i = 1; i < level; i++) { total += Math.floor(i + 300 * Math.pow(2, i / 7.0)); } return (int) Math.floor(total / 4); } You can then use this to get the xp to level: int currentAttLevel = client.getSkills().getCurrentLevel(Skill.ATTACK); int currentAttLevelXp = client.getSkills().getExperience(Skill.ATTACK); int nextAttLevel = currentAttLevel + 1; int nextAttLevelXp = experienceForLevel(nextAttLevel); int xpToLevel = nextAttLevelXp - currentAttLevelXp; And then just a simple xp/hr if you need it. int attExpHour = (int) ((3600000.0 / runTime) * attExp); int defExpHour = (int) ((3600000.0 / runTime) * defExp); int strExpHour = (int) ((3600000.0 / runTime) * strExp);

I developed some paint for a friends script, suggestions on what to do with it to make it better would be much appreciated. V2:

Looks better.

You're welcome.

I noticed that a few people have been complaining that the scripts have to be written in Groovy. Groovy is based on the Java Virtual Machine so that means that you can use the same syntax as you could with Java and place it inside the groovy file. This simply means that you would take a normal Java Class file and create a regular script such as the demonstration below and you would simply change the extension on the file from .java to .groovy. The downside of this is that you will obviously not be taking advantage of the additional features that Groovy has but Java does not. The only file that needs to be a groovy file is that file that is a subclass of org.osbot.script.Script. Below is the old tutorial beacuse I wrote it in two seconds. This will be a simple short tutorial since people are complaining about how we have to write scripts in groovy and blah blah blah. Groovy uses the Java Virtual Machine so obviously almost ALL Java syntax will work correctly with groovy. Now basically what you will want to do is create a groovy file. and have something like this inside of it import org.osbot.script.ScriptManifest;import org.osbot.script.Script; @ScriptManifest(name="ScriptTest", author="Billy", info="An awesome test script.", version=1.0d)public class ScriptTest extends Script { @Override public int onRun() { return 0; }} You can use normal java syntax and create additional class files that are used inside of it. The only file that has to be a groovy file is the file that is a sub class of org.osbot.script.Script otherwise it doesn't matter. Sorry this is in a rush I'll add more to it later.