Maxi

I have added a tiny utility to set your fixed default worlds and start a specific world. This will be available on the next release. Stay tuned! OSBot.org

Updated it to 1.6.3 with a couple of hot fixes.

That was a typo, should have been "when you're not running a script".

Hello everyone, We are very glad and proud to announce that with this release the SDN is finally available for public. Furthermore this version contains a couple of bug fixes for bugs introduced with 1.5.12. Work on randoms that has been done: Fixed lost and found (appendages teleportation random) Modify Molly partially, untested though Fixed freaky forester Fixed maze Work on the OSBot client that has been done: Added SDN script availability New accounts GUI and backend support Random management system Ads no longer pop up when you're not running a script GUI buttons are back to how they were before, like real buttons General bug fixes all over the place Please note that the SDN is still very immature and we might have to update a couple of times in the future to remove bugs that we have missed. To add scripts, go to the store here: http://osbot.org/forum/store/ and check out the scripts you want to add. Then click the refresh button to load them in your script selector. We will be releasing a manual for script developers and for bot users how to use the SDN in the coming days. Also, in the coming days we will start adding scripts to the SDN and give access to the SDN for script developers. Download can be found here: http://osbot.org Sincerely, OSBot.org

It's one or two minor things that were changed that's causing this, I hope to be reverting and testing it today.

0

What are you talking about?

Hello everyone, Here is a heads up on what I have been working on the last two days. I have written the random management system, which will allow script writers full control over how to handle randoms. For example, let's take the case of an autofighter. You get a strange box and you're in combat and not in a safe zone. The programmed random solver for the strange box will recognize the strange box and try to solve it, but it will close the interface constantly because you're under attack. Your autofighter won't any longer be in control, so eventually you will die. Here is where the random management system comes in to play. In this case you want control over what happens before and after solving the strange box, more specifically you want to make sure you are out of combat and in a safe zone when solving the random, you want the random to be solved as programmed by default after that and you want to finish by walking back to your fighting spot. Here is a simplified example of how that would work with the random management system (note that the onLoop doesn't have to be overridden at all here, I just put it here for example purposes): @Override public void onStart() { this.actStartTime = System.currentTimeMillis(); randomManager.registerHook( new RandomBehaviourHook(RandomManager.STRANGE_BOX) { @Override public boolean shouldActivatePreLoop() { return myPlayer().isUnderAttack() && !myPlayer().isInArea(SAFE_AREA); } @Override public int preLoop() { walk(SAFE_AREA); return gRandom(600, 300); } @Override public int onLoop() throws InterruptedException { return super.onLoop(); } @Override public boolean shouldActivatePostLoop() { return myPlayer().isInArea(SAFE_AREA); } @Override public int postLoop() { walk(FIGHT_AREA); return gRandom(600, 300); } } ); } Furthermore, I have been working on a new GUI for accounts and a fresh system on the backend of it. One reason for this is that the accounts system simply wasn't user friendly and intuitive, another reason is that there were bugs occurring with it sometimes. Accounts are ordered in alphabetical order and you can now set your preferred experience rewards chosen when encountering a genie lamp or book of knowledge per account. Here is a picture of the new accounts GUI: These updates will be fitted in the next release. Sincerely, OSBot.org

The client says 23, but those are the files that handle the random events. From the 23, are 3 built for bank pin, login and welcome screen. But from the other 20, there is one that handles like 6 or 7 randoms.

Why would you want to force a right click?

There are minor bugs in certain randoms that cause them to not be finished. I've seen freaky forester, drill demon and molly occasionally not finish the random but perhaps like 70-80% of the time. We will make sure this becomes 100%. Also, I have yet to add Evil Bob, luckily I've collected all the data for it, and fix up the lost and found random. Today we will also release the random management system.

http://osbot.org/forum/forum/88-vip/

The other ones are not added at all so that's why. They will get added in time, for example I have been gathering data for the Maze random event. Freaky Forester shall be fixed asap btw.

If you have an account in the Maze and are willing to let me gather the much needed data to write the Maze random event solver, please drop me a private message. Thanks, Maxi

I still love unreal tournament 2003 occasionally.

We won't support GP as we rather not get involved with RWT.

Hi everyone, As I was studying this morning for a test I have on Tuesday, I figured I should write you all a little behind the scenes story of what is going on behind everything you see on the forums and in the bot. As you know, we try to stay as transparant as possible to you all! After we released v.1.5.x containing randoms, we sat together to map out the next few weeks and what we plan to get done and release. Besides fixing existant randoms and adding missing randoms, we are prioritizing the SDN whilst maintaining other little bug fixes and extensions to the API to make our work a little varied. Tonight I ran a hunter bot, written by Xerion, which is planned to be released on the SDN as a premium script, for over 8 hours without getting stuck. This proves randoms have made giant progress a long the lines since their release. We have a new batch of fixes ready for the next release when it comes to randoms. But other than the SDN, we aim to keep excelling OSBot to that point of perfection we aimed for the day we started development. When we started developing OSBot we aimed for a working prototype to start with, one with some design in mind for the core which runs everything, but for the API we didn't make a design plan and we just went a long with what we needed and added it somewhere seemingly appropriate. This was fine for the BETA, however as with all software development, design is very important for extension and usage, especially if it involves hundreds of users who want to use the API to script. So looking at our current API, we realized it's organized poorly. When building on a poorly structured API, it will of course end up in getting structured more poorly and poorly, so you got to tackle this early on. With everything running a lot smoother than a month ago, we believe it's time to do this now. With the SDN getting ready to release, randoms getting more towards 100% with every day, we thought it's getting time to step out of BETA and come up with the official release of OSBot 2 soon. For this, we will be restructuring the entire API. The API will be structured in a way it will feel as if it's a static API however it won't be. You will be programming with it as if it is, but it's not. We will do this transformation, and release a version so everyone can update their scripts before we finally officially release it and abandon support for any versions earlier than 2.x.x. We think, and it will, that this will create a much user friendly scripting environment for everyone. You will find the same methods and the same feel whilst executing your scripts, however the API will be much more intuitive and user friendly. Another thing we will be doing is getting some of the hooks some of the script developers have been asking for. This are maybe like 5 or 6 hooks, but they are getting higher on our priority list as we have to keep our script developers happy . But that's not everything. We feel that the release of OSBot 2 needs something special. We are not sure if we can manage it in time, but for some time early in the release stages of OSBot 2 we plan on releasing a web walker. The one and only Brainfree, his name might suggest he has no brains but he does!, has been developing a web walker for the past few weeks. With our help, we will give him most of the data of the entire world map, to make his web walker walk across the entire map without any problems and little manual work. Teleporting? Fairy rings? Portals? Just walking? Doors, ladders, gates? It's all planned for to be working. This will definitely be one of OSBot's most useful features, and will allow to write bots beyond believe. Slayer you said? No problem. Farming you said? No problem. Died somewhere and you need your script to go back? No problem. So for now, we are still focusing on the SDN and the randoms. But once we get closer to finish both, we will start the restructuring of the API and get ready for OSBot 2. In the meanwhile, we will get everything ready to provide Brainfree's web walker with all the necessary data to traverse the entire world map. So what do you think of that? It makes me excited to see OSBot grow everyday, and with these updates in the near future, I'm wondering where we will be in another month's time. I want to shout out thanks to everyone who has been caring and supporting OSBot till today, and to everyone who will continue doing so in the future. Spread the word to your friends, we will be here for them! Sincerely, OSBot.org

I see your point but nobody said VIP is a donation. It's a sale where two parties agree to exchange items, in this case privileges/otherwise restricted access on the forums and bot in exchange for money.

There is nothing with us buying or selling in general, with the exception that we make the rules. We can sell VIP and Sponsor ranks accompanied with their privileges. Rules are that you can't sell scripts as a script writer, unless it's with the written consent and approval of the owners of OSBot. Once the SDN is available, people will be able to sell their scripts through the SDN. Anyone caught ignoring this, is breaking his software license and thus we are granted permission to eliminate all further access to OSBot and if done at a large scale, take legal actions. This guy you are talking about, claimed to not 'sell' his scripts, however before he would share the script, he would charge a donation before he would trade over the script. This isn't a donation, this is a sale, and therefore got a warning and will be banned from our forums if ignored.

Exactly.

I keep encountering people who have not read this, so please read this: http://osbot.org/forum/topic/2063-important-osbot-golden-scripting-rule-exception-handling-in-osbot/ Sincerely, Maxi

I've checked his script, it's clean so it can't be him. You must have been infected in some other way. What are the scripts you have been using for the past weeks, since you started to use OSBot? Let's carry on in a private conversation.

Why are you using 3 accounts?

It's being found in dllhost.exe, where and what is that? It's not our bot, but dllhost.exe is only supposed to be in your system32 directory, not there. You must have a virus right there, because dllhost.exe not in system32 is for sure a virus. What is the list of scripts you have been running lately? Could we get a package zipped up from those. It could be there is something malicious in any of those scripts.

They won't anymore.