cloudbuster

If anyone would like to use code from this script, or contribute code, then by all means go ahead. Please let me know either here or personally though (when you use any code I've written), because I will always feel that in all fairness what we take, we should also give back in some way. Users of the script can always give back to the scripters by taking a moment to give constructive feedback. It really proves your own commitment to working with quality content, and it will always be a win-win for the scripters and general users. From this day on: I will be working on the next phase of the combat system. I don't think I really have to get into specifics for one to figure out what exactly that is. It is an auto ranged script after all. Edit: This might not be done for a while, due to other worldly duties. However I've been working on multiple script projects lately - all of which are coming together nicely. More updates and new content to come; currently only on my Pastebin. Thanks! p.s. I've edited the available copy of the script on the Pastebin, since yesterday. So if you received this content before-hand, you ought to re-copy the small update.

This is an experimental combat script that was birthed from my process of becoming familiar with the OSBot API. I plan on re-gutting the script once again to make it more clean and possibly run faster, but that work will not be happening for a while. I've got every intention to add a standard script GUI and better organization of item looting (based on item values or user-set priorities). So those are new features to come before I consider making a proper public release. There are plenty of other ideas I have for auto ranged related things, because of my intense interest in the skill, and so I also plan to be integrating a more wholesome spectrum of ranged combat capability, after the main combat concept is in proper order. This script should be handled only by those who know how to properly debug and modify/create a functional script. Since there is NO GUI: You have to change the variables inside of the script to run this as you would prefer. With that in mind: consider how tedious that would be. If your in-game character is of a lower combat level and their hitpoints are below 50, then this script is already in a practical setting. The hitpoints range that the script is currently set to eat at is randomly between: 16 to 24 HP. So in order to change this variable, you will have to go within the taskHandler() function (it is generally referred to as the getState() function), and change the if statements within that function. Food support is easy to add to. Just look for the variable int[] food and add the item ID's of choice. To make your ID the highest priority for the script to select (if available in inventory), then make sure your custom ID is at the first index of the array. Just look around the script to see if you would want to use this, and how to use it, and give me some feedback afterwards! Supported features: Can use arrows up to steel. Can use iron knives as the only knife type currently. Certain variables in looting and ammo equipment change if you have a Ava's accumulator or attractor equipped. Take Note: You can add your own ammo variables easily. This script will not (re)equip a bow for you. IF YOUR CHARACTER RUNS OUT OF ARROWS/KNIVES, THE SCRIPT WILL NOT KNOW THIS. There will be some quick fixes soon to take care of these issues. If you actually want to use this for training then equip a ring of life (failsafe) and lots of ammo. This early release is not intended for running the script with total confidence. There are possible bugs and obvious bugs. They may not happen often, but they will happen. This release is intended for: a) study and b) constructive feedback. Thank you. pastebin.com/Fi7ZdaEY

Bot worlds don't seem any more threatening than the obstacles imposed by random events and curious players. For "LaGex"" it is just a way to filter out some statistics for pondering, and it adds more resources for them to take care of and pay for. For us it is another clear indication of when we need to adjust our bot usage routines. There is a lot that be changed, but the resource efficient opposition is through a constant change of the small stuff, and a misleading exaggeration of those changes via community updates. Quite an interesting path that is being made here though. I at least presume that massive gold operations will be slowed, which in my opinion is a good thing. If you tend to bot in only a single log-in session, then I don't see how this could possibly be an effective detection method. (Edit: Upon further enlightenment on the matter: My previous opinion contradicts the actuality of bot worlds, which is that single log-in sessions could lead to being detected. I am silly!) Zartect's idea of using an audio warning is logical. As a side note: integration of scripts and Smartphone apps has been on my mind lately. I consider their potential as a remote control for your bot, and utilizing a phone/tablet for progress reports is of sound logic to me.

Hello. The name is Chris. I am joining OSBot in determination of building my knowledge base on bot scripting. I've been involved in the RSCC ever since the final years of Kaitnieks, where I first learned about the process of creating your own bots. Ever since then I've been an on and off scripter for different Java bots and the Pascal/Lape bots. I am not an expert -- I approach scripting as like a hobby, but of course I am still serious about making a flawless script. I've only recently heard about OS Java-based bots coming back from hiatus. So I jumped on it quickly, but still late hehe. I'll be spending some time studying the API. Thanks for the opportunity OSBot