Maxi

I'll have to check the version number on the SDN later today, perhaps something was confused with updating. My local version has been running for hours. Will get back to you in a bit people.

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

I feel sad for what happened, probably just like you. However, you made mistakes that only you are accountable for and nothing will change that around. Focus on what is important Kati and learn to ignore whatever isn't. You were trusted and you still are in our eyes however there can't be taken any further risks. We appreciate what you did for us in the past and present, you meant a great deal for us personally and OSBot and it's sad to see it end this way. You taught a great deal to people and learned a great deal as well I hope. I feel sad for this day. I'm going to close this now. Farewell. People make mistakes. Smart people learn from them. Hopefully you do as well.

We are planning on adding this.

Read the announcements.

I suggest everyone leaves Clutch alone, he will most likely leave you alone if you do the same. No reason to escalate this. It was known to us that Clutch is who got the database from Kati. Like we said earlier, we will never know the entire story behind this as we will not know who speaks the truth. All you should do is change your passwords here and anywhere else that could be related, secure your emails with 2 way verification and let it go honestly.

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!

Sorry for your loss, be careful with what you download. OSBot does have no access to whatever you store in the client, the information is stored locally and not accessible by us.

Can I get a more specific bug report?

The script now requires to use version 1.7.31+ and is available again for purchase in the store.

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

I have looked at the script today and found the issue. I will make sure the script will be up and running again today.

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

If Laz does not have any time today I'll review the script and fix whatever is going on with it. Can people give me a list of issues? I don't foresee much trouble to fix it, however some knowledge in advance would be useful.

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.

I promise to get on this in the coming week. I'm sorry for the inconvenience, lately with the growth of OSBot I haven't been able to give this much attention.

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 could not trace it back to a forum user and it's from a hosting service by this company: http://www.softlayer.com/ If you have a screenshot you could contact them and perhaps they are willing to find you the person who did this.