Maxi

Packing the jar now, hang in there ;). Updated, closed.

RS updated to revision 15 today and normally we would not have to upload a new jar for OSBot as we would simply replace the hooks file and restart the server. Unfortunately some of the callback code was partially broken, so after a quick fix and some testing we had to release a new version. The good new is that our updater had no broken hooks as far as we've been able to test and see, so next time updating will be a matter of 2 minutes . This unfortunately also means that all previous versions prior to BETA v1.4.3 of OSBot will no longer work. Download can be found here: http://osbot.org Remember to refresh the page with CTRL + R if the download still downloads 1.4.2 Have fun, OSBot.org

Alright, I fixed it. Unfortunately we will have to push out a new update, because the fix is in the code and not in the hooks, the hooks seem to be 100% unbroken. I'll walk through the client to see if there is nothing that isn't ready for release yet and quickly finish up, and then release.

Hooks all seem to be fine, however we have an issue with a couple of callbacks, we are working on a fix right now.

I just got home, time to run the updater and see how our hooks did on the update .

IP.Chat will most likely be deployed this week or next week.

That's not yet decided upon, but it will most probably become OSBot 2.

OSBot was released on the 5'th of April with the first public BETA version, over 6 weeks after the release of OS Runescape. The idea for the development of OSBot sprouted on the 2'nd of March, 2 weeks after OS Runescape was released. So it was developed for 4 weeks before it was shared with the public to test and advance it. We are now in BETA for just over 1 month. We hope for OSBot to officially step out of its BETA status by June 1'st.

Our intention is not to ruin Runescape's economy and it will never be. Therefore, anyone who aims to benefit on top of the free tab they have, can clearly find a way to bring together the funds for VIP. In fact, one day of botting with VIP can already return your money on VIP. The only reason I see fit why people might need more than one tab without the purpose of gaining extra benefit over others in Runescape is when you are developing certain scripts that require two accounts to interact with each other. People who need it for developing scripts can see it as an incentive, trial and official script developers get all the VIP benefits by default.

Our vision is as follows: We are a free bot where people can run one bot at a time without VIP. If people want to have multiple bot tabs, they are aiming for benefits in the game in a bigger extend. Therefore, we believe a price can be paid by those people, simply put your benefits can make the price of VIP back in one day on multiple accounts. If you don't like it, you are not forced to use it. There are other old school bots out there that require you to pay a monthly fee to get access to the bot. Others, simply put, will not reach as far as we do and don't and probably will never have the quality we are aiming for. I'm closing this, because there is nothing to discuss here.

Hi everyone, It has come to my attention that it's not clear for everyone how to handle exception in OSBot scripts. Various pieces of code in the OSBot client throw InterruptedExceptions. Everywhere where you have a try-catch block you have to make sure you add specific clause to catch InterruptedExceptions in which you then have to throw, in front of any other catch clause. If you're only adding try-catch blocks to catch the InterruptedException, then make sure you are just adding the throws statement to the method signature and remove your try-catch block entirely. The reason this is important is because the client uses interrupted exceptions to switch behaviour, for example when the bot will switch from the script to a random executor, or when you pause your script. Here is an example: /** * Gets called recursively on the bot's main thread. * * @return The timeout to sleep after running one loop cycle. */ @Override public int onLoop() throws InterruptedException { try { scan(); switch (state) { case IDLE: return 100 + gRandom(100, 50); case STEAL: return steal(); case TO_BANK: return toBank(); case BANK: return bank(); case TO_STALL: return toStall(); } return 20 + gRandom(100, 100); } catch (InterruptedException e) { // <---- VERY IMPORTANT ----> \\ throw e; // <---- VERY IMPORTANT ----> \\ } catch (Exception e) { e.printStackTrace(); return 100 + gRandom(200, 100); } }

What bank issue? Withdrawing works, depositing works. I don't know what you're talking about.

You're an attention whore.

BETA v1.4.2 is hot fix for BETA v1.4.2. The following updates have been addressed in this release: Fixed slow mouse movements on entities Fixed issue with clicking on weird places for example report abuse button Improved walking Extended API with a couple of useful methods Fixed issue with interface misplacement Fixed issue with changing vertice counts for models Fixed issue with main screen clipping intersection Probably more that I can't remember Download can be found here: http://osbot.org Remember to refresh with CTRL + R if your download still downloads 1.4.1 OSBot.org

My story is not a very strange place, but it was scary though. I woke up after a night out in a strange bed with no one around. I had no clue where I was nor could I remember who I went home with. I got out of bed, slightly scared and went to look for people in the house however no one was home and there no note to be found. Eventually I left and figured out where I was using my cellphone's google map. Turns out it was only 4 streets away from where I live. As of today, I still have no clue. Lol.

I would like to request access to an account with a pending bank pin so I can write support to bypass the interfaces when opening the bank if an account has a pending bank pin. If anyone wants to collaborate, please change your password to something that isn't related to anything personal and other passwords you use and send me a pm. Thanks a lot.

Try again @specops5000, I've removed all failed/pending invoices.

That must be script related.

You shouldn't, it's smooth for most people. Just try it out.

Because some of those bugs are encountered by for example only 5% of the people or less. So in my opinion, as long as we are in BETA, we support older versions and release public newer versions for testing. For example, the slow mouse movements, are so far only encountered by 3 or 4 people out the entire group of people who have used 1.4.1. (edit: apparently it happens more often on moving entities like npc's). Using only the script writers would not uncover all bugs. Once we leave the BETA, we will setup a release cycle with release candidates that will be tested before updates.

We are pretty much finished with what we aimed for 1.4.1. I'm waiting for Laz to return from a family event he's attending at the moment, in the meanwhile I'm just playing around, tweaking, trying to score bugs etc. Hang in there ;).

We will release 1.4.x tomorrow unfortunately. We are 95% done, but can't afford to release without having tested the last few things.

All all this can be scripted already.

I'm happy to announce that we expect our SDN to be and running by the end of sunday and with this most, if not all, random events included in the SDN and automatically loaded onto your computers. On another note, I expect BETA v1.4.1 by tonight. My list is still long and there have been many distractions around OSBot that needed our attention, however I will work on v1.4.1 for the coming 9 to 10 hours so that should be enough. Stay tuned all ! OSBot.org

The difference pretty much comes down to one thing (the language differences are neglectable): Groovy doesn't need you to compile which speeds up development, Java allows you to jar your files into packages to be used by the client. I would say, Groovy for development, Java for releases. One can be converted to the other within no time.