Maxi

yeah i know right like ugh thats jst so damn dumb......... so mch for VIP actually freaking meaning something........ They are not getting VIP, simply unlimited tabs for a couple of days.

Dear community, As the summer is coming to an end things are significantly different than at the start of OSBot almost 6 months ago. In 12 days we will celebrate our 6'th anniversary, on the 2'nd of September. Where we first had no working random events, no SDN support and lots of bugs due the immaturity of OSBot things were looking better and better as time passed and today we have come to the point where OSBot has an API with a rich variety of build in features that other bots don't support and most important a stable product. However with the experience gained over the last 6 months, we know we can improve on various factors of the client and like we announced earlier we will bring a brand new client with those improvements taken in to account from the ground up. The last 6 weeks or so were quite the different ones for me. Where I was able to devote all my attention to OSBot improving it on a daily basis, other roadblocks popped up in real life and my attention was drawn away. I've seen my grandfather die, been on a vacation with my friends and then had other private things going on absorbing my attention, drive and time. Luckily, as with everything in life, things turn around when you want them to and I've battled my way out. Because of my lack of time for OSBot some administrative things were delayed time after time. I'm sincerely sorry for everyone who was victim of this. But let's talk about something positive again. Because we want to celebrate our upcoming 6'th month anniversary we will be doing two things: The first thing we will do is give our developers a 80% cut instead of the usual 70% of the benefits made of their script over the last month to thank them for their efforts. Normally we take 30% for the administrational tasks that need to be done, but as the administrational work has slowed by my absence we will make up for that this way. Until the 2'nd of September we will give everyone unlimited tabs! This will be starting tomorrow. To conclude this thread I want to make a shout out to everyone who has been part of OSBot, whether it being from the beginning or more recently, without you OSBot would not be where it's at today. Thanks for reading, OSBot.org

I just noticed some things listed were not pushed and packed in this release. It will come today.

I honestly don't get your negativity, I understand you are upset by the recent happenings and so are we. We're working around the clock for the past 24 hours to keep everything secure after what happened with Kati. Switching to this new host is something we never hoped for having to do as the costs are nearly a thousand dollars extra a month but we did as we want to prevent those attacks happening anymore. Fact is though that our current host has had many issues that were unrelated to attacks.

Added the following things to the update log in the first post that Laz forgot to mention: Fixed the issue with enabling/disabling the default mouse paint from within scripts. Fixed the is in building mode check. A hacky fix for variable sized wall decoration objects like rifts in the Abyss. Various required features to use resource walking in the future (Brainfree : ) )

At least I'm a penguin!

Can I get a more specific bug report?

Hello everyone, I'm glad to announce that the next OSBot version 1.7.31 has been released. In this version the following changes have been made: Fixed an issue where the bot would not be able to interact with characters that are stacked on a tile, i.e. two npc's on the same tile would cause problems to interact with one of them. This is now working fine again. Wall objects have been hooked for a very long time but a small bug in the core caused them to be not included in the list of objects in the region. They now added properly. A few changes have been made so that the Tab Maker is working again, the Tab Maker will be available again in the store as well The download can be found here: http://osbot.org Sincerely, OSBot.org

The group will exist of approximately 10 people, however this doesn't mean it will be tested by 10 people. Some people might not be able to test certain scripts due to level or quest requirements and not everyone will be able to test on a daily basis. Therefore we will have around 10 people so the process of getting feedback of their tests will be faster, resulting in a smoother and quicker addition to the SDN. We will not require for everyone to have tested a script, everyone who has done some tests will give us feedback which we will use to base our verdict on.

Sell it at Advertising other bots isn't allowed., there is no use for this script here. USA is thinking of converting this script to OSBot btw.

Let me explain the mentioned instancing to everyone who is not in the clear about it: Limiting the amount of bots your can run on one purchased instance will mean that for a certain script you buy you will only be able to run a certain amount of bots per instance you bought of that script. An example would be like this: Script developer X created a script which has a money making method making 500k an hour. However, if a 1000 bots would be botting the method it would make little to no cash anymore, rendering the sales of that script to zero and the method useless. The developer is then able to decide he wants to limit the amount of bots per bought instance to for example 4. If someone, whether it is a goldfarmer or not, wants to bot this method with 8 accounts this person will have to buy the script twice. Instancing will not affect any currently processed sales and will be SDN only and the administration team will not be in charge of those decisions, the developers will be. It will most likely not be applied to most scripts, but if a developer like mentioned in the example has a very decent money making method he wants to protect and control the usage of it we simply have a method of supporting this.

Dear community, It has been a while since we released the SDN and we were happy that we were able to launch the platform. The SDN has many upsides as it provides a secure platform that is easy to access by users of OSBot to buy and/or add scripts to the script selection, but also has some downsides. The major downside of how the SDN is organized is that it requires a lot of contact between developers and the administration team to add scripts to the SDN, mostly through IM services like Skype. But to communicate over Skype people need to be online at the same time and also the administration team has tasks to complete that sometimes require some priority. To summarize the problem, the administration team is not able to schedule their work together with the tasks of adding scripts to the SDN. We have thought about several possibilities to make this process easier. The easiest thing to do would be to write a web interface where everything is automated. You submit your script, a connection is made with a server and the server executes all logic required to add the script. However this would create a solution where there is no verification of scripts leaving a security gap, besides the fact that IPB has made things complicated with encryption and obfuscation of some of their files to certain formats on how to store information in the database. So that thought quickly vanished. It was clear to us that no matter what human interaction will remain required, so we took the road of thinking how to cut out the communication through IM services. And here is what we will do: If you are a developer and you want to have your script added to the SDN, you will be able to go to a webpage where you will provide the necessary information to us to add the script to the SDN. This information will be send as an email to a certain address and any communication will be through email after that instead of Skype. The script will get added to the SDN privately and will not be visible for anyone. When this has happened, an anonymous group of users (around 10 people) will test the script to see if it meets the quality standard sought after. Once enough feedback has brought back in about a script, a verdict will be made and if positive the script will be made public and will be available for everyone in the store to add to their collection. The same will happen for update notification of scripts. We will release a page where you will be able to see all the scripts you have on the SDN. If you require a script to be updated, you can request an update and the system will send an email notification to us. By doing the above we hope to be able to start adding scripts to the SDN at a much higher and efficient rate than before. Besides all of the above, we will introduce the possibility of limiting the amount of bots per script bought at one time for any developer who wants to have a certain control over the amount of bots botting a certain activity. Thanks for reading, OSBot.org

Hello everyone, I have returned and I'm ready to contribute to our fire again. I'll be discussing with Laz to decide on our priorities again and I'll be working on some old work left behind when I was out of the country. Today I will be working on fixing up some scripts that require some attention. After that I will be writing an anti ban mechanism which hopefully will prevent many of the manual J Mod bans and possibly also the reports by P Mods. It will detect moderators in your environment and perform unpredictable behaviour, partially defined by you as a user, which should lower the suspicion. Goals we had before were obvious and they are still present, such as 'Hannibal', the first Titan to completely diminish the concept of web walking. Hannibal is a work in progress but will get a lot more attention now than it did before, simply because of the fact that there is room for attention now. Further automation of our administrative work is another goal which will happen behind the curtains, but most definitely very important for all of us. And we are brainstorming about a much easier way of adding scripts to the SDN, creating a web interface where you can submit everything that will create the Nexus store product, the repository module etc, leaving our only job to double check and confirm the entire product to be safe and working. All cool stuff And last but not least, we will be starting on a new little secret this month. What this is and how long it will take for us to show you publicly is not sure, but it has been us excited for sure. Sincerely, OSBot.org

I'm getting tired of those questions. All scripts on the SDN are verified by our eyes before we give the green light, this is for every update that it gets including it's initial upload.

And it's back to normal.

Dear community, The website will be performing a little bit slower in the coming few hours. This is because I'm currently applying a lot of strain on the sql database. I thought I would let you guys know. Sincerely, Maxi

I've moved this topic, this is not a bug or an error. On topic: You could have been compromised in many ways. It could be that the Advertising other bots isn't allowed. and/or vInsert database gave enough information about you to hack your account (if you used their bot and/or registered on their forums), you could be infected by a virus that logs your keystrokes and/or enables remote access control (then you are infected with a rat) or perhaps you got phished. Download Kaspersky to get a decent anti virus scanner, however remember that freshly written viruses are not in their signature database and therefore no anti virus scanner will always protect you a 100%.

No the bot will be online.

Dear community, Over the past month we have seen a reign of cyber crime across the Runescape botting scene. vInsert was the victim of several Runescape account hacking disputes before its database got compromised in the merger with Aurora. Now Advertising other bots isn't allowed. was defaced as well and its database was compromised as well. This thread is to shed some light on our perspective towards those recent happenings. We have always tried to be in time with warnings to protect you as people, Runescape players and us as a community and succeeded in doing this. But as this wave is continuing we have to give it more attention. In general everything we do is with security in mind, that means our security (both personal and OSBot's) and your security. With the recent happenings we have decided that we will take an entire day to go through each and every security measurement we have and see if there is anything that can be improved without harming any user experience. We feel sad for the victims of those attacks even though they might be competitors in some sort of way, we do not and will never condone DDoS'ing, hacking and any other sort of black hat activity. OSBot itself also has been victim of attacks, may it only be DDoS attacks though. We are increasing measurements taken to automatically mitigate such attacks. If such attacks will continue we will alarm authorities and file a report. We will be collecting network connection logs in case. I'm repeating myself, but we will never condone any cyber crime and black hat activity by ourselves, our community members and others. OSBot is a place where people should feel safe and comfortable. Sincerely, OSBot.org

OSBot is running fine for currently: Session Count: 1889 Tab Count: 1929 User Count: 1694 Are you talking about OSBot or Advertising other bots isn't allowed.? As for Advertising other bots isn't allowed., their database is still compromised containing a lot of information that could be used to hack in to your personal service (email, skype etc) and possibly Runescape as well. They do have Advertising other bots isn't allowed.'s database.

It is encrypted and only stored locally on OSBot. But the point of this announcement was to let you know that their database most likely got compromised and in there is a lot of information that could lead to hackings of your personal services, not only Runescape. We are talking about their server database, which does contain information about you. You should yes.

New update: After contact with our hosting provider it turns out there is a much larger issue at hand at their side. They have a large infrastructure where our traffics gets routed via various ways depending on your location and somewhere along these routes for most locations there is packet loss and therefore the server is seemingly down at time. We have provided them with several routes and they are investigating it as we speak. We will update you soon with more information regarding this issue. One thing we want to make sure is to let you know that it's not an attack of some sorts. For now everything seems to be back up again, but until we get a good answer from the provider it could be that the server will go down once more.

It was down for everyone. More information can be found here: http://osbot.org/forum/topic/6289-dedicated-server-maintenance/

Dear community, Our host had to do some unexpected maintenance to some of their clusters and unfortunately our server was in one of them. We're sorry for the inconvenience, hopefully this won't happen again any time soon. The host has not replied what the exact reason was, hopefully they will. The bot server is back up now. The downtime was approximately 6 hours. EDIT: Sincerely, OSBot.org

Dear community, As time goes by it has been a while that we have shown you what's going on behind the scenes at OSBot. What is going on besides the updates you see on the forums and the bot client itself. The forums have been growing rapidly over the past few weeks and the community has become more complex to manage. However we hope that our decisions still benefit you all in the long run and to keep as many people as possible satisfied with what have to offer. Last week we switched to our new dedicated server which brought significant improvements on the speed of the website. We upgraded our CloudFlare plan to have faster throughput for CloudFlare, together improving the response time of the website. When switching over, we switched to a different web server again. This left us with some tiny bugs in the url rewriting for friendly urls (furls). This made IP.Content working incorrectly and has forced us to remove the link to the repository and the API temporarily. We have been looking in to this issue and identified the problem, we will be spending time on fixing this up as soon as possible. As mentioned earlier, OSBot is now soon to be an official part of a company set up by us. This will give us a lot of legal protection in the future and will hopefully will make it possible for OSBot to stay for the long run. However, with a company a lot of administrative work comes along. Therefore we saw the necessity to create some administrative tools to make the work with the SDN easier and most importantly automate payments to SDN premium script developers as much as possible. This has been taking up most of my time for the past week and is also the reason I haven't been that reachable on Skype compared to normal. I hope to finish up these tools as soon as possible. As for the bot, we've been doing preparations to load definitions from the cache to provide definitions for entities that have 'nulled' names and nulled definitions. For this we will also have to write a cache downloader that will make sure that the entire cache is available for the client before executing any script or logic. This feature will also lead to the next giant improvement mentioned multiple times: the webwalker. The cache reader and downloader both need some updates and tweaks, but once these are done we can implement the dumping of the encryption keys needed to decrypt the landscape files, which we then can use to populate the data set for the webwalker. We will be spending time on this in the coming week. All these updates are more or less happening without you seeing any results, yet. However, the administrative tools might cost us some time now to develop, it will make our lives and eventually yours as user of OSBot easier. Adding, removing and updating of the SDN will become easier, so expanding the script base will go faster. Processing payouts to developers will become easier as well. And once we have the webwalker ready for use, OSBot will become the place where you want to be as a developer AND as a user. I can't wait for the first farming scripts or the first slayer scripts that make use of the webwalker. Stay tuned for amazing things to happen over the summer! Sincerely, Maxi and the OSBot team.