Alek

Both removed.

I'm looking to remove scripts which have not been working for longer than 30 days from the SDN. I'm also going to be removing repetitive scripts which were pretty much made for an easy Scripter I rank. Script name: Problem/Issue: Last date working (if known): Have you reported the issue on the script thread?:

Since you told me this was fixed, don't blame novice scripting questions as client bugs again. It wastes a lot of my time.

Not a client bug, moving to scripting help.

This means you also can't connect to the website to check the version found here: http://osbot.org/ Check firewall settings, etc. Not a client bug.

Scripts are sorted on each category by: Free -> Premium -> VIP+

When I have time to work on the web stuff again I'll do it. Just like CLI and proxy account management, it may take a while but its in the works.

If you are walking relatively short distances, there is no need to use the web-walker. There are some simple math approaches you can take.

Winners have been posted!

Woodcutting guild was added last night, checking into any specifics for redwood later on today.

Now on the SDN.

To celebrate kCutter's 2 year anniversary, I'm going to be giving away 3 lifetime premium auth codes. kCutter is the longest running script here at OSBot generating massive experience and gold gains. As a botter, you can feel confident that I will continue maintenance, development, and improvements for years to come. I know the stress many of you have as a customer wondering whether or not the script/scripter will be around for the long run. This marks a pretty big milestone for script lifetimes. To submit your name for the free premium auth giveaway, simply post below and you be randomly selected on Sunday (tomorrow). Winners: 1. 2. @razel 3. For more information on kCutter, visit this thread: http://osbot.org/forum/topic/54430-free-premium-kcutter-chop-any-tree-anywhere-intuitive-design-uptime-24-months/

Yes, you can bot 24/7 at flax fields on flagged ips.

Could be a poorly written script. I can tell you that the client runs fairly well with one bot and shouldn't be consuming 80% under normal conditions. Try a different script (or two).

Incorrect, the plane is set to "1".

Small update, patched an issue with setting bot through command-line as reported by @Token. Also there is a new command: -world <worldnumber> You may either use the 300 digit or regular server number (it will just subtract 300). Example: -world 375 == -world 75. With that said it won't load the weird worlds like 666. Various other small patches which nobody will care too much about. Happy Botting -The OSBot Staff

I'm still waiting on mods to tell me what your original name was.

Reading over scripts and coaching each scripter on what's needed to get accepted is very time consuming. I have no problem instantly denying scripts if you want me to move over to that model.

osrsbanrates.com currently says 11.2%

You must enter a pin, that's the usage. Enter a fake pin if you don't have one set.

It's preferred to have separate clients for each bot. I was considering adding a "low-gui" mode where a bunch of components and interfaces won't load to perhaps make a cheap save on some resources (making individual clients more attractive).

Although there are a ton of bugs I should probably be working on, I went ahead and cleared my schedule a bit to release one of the most requested features; full command-line support. As a bot farmer, you can start up a new client with a proxy, start a bot, and start a script with all the settings you want. If you write scripts you will notice a new method at your disposal, getParameters(). I'll explain this a bit below. The two new flags are "bot" and "script". Just to make it clear, "bot" only starts up a new bot and "script" will only work if you have a "bot" set (because how can you start a script without a bot active?). Anyways the flag values for script are: scriptid:params // Will attempt to load an SDN script automatically. Get the script id of your script from the logger when you run the SDN script. scriptname:params // The script name is the name found in the ScriptManifest Issue: If your local script ScriptManifest is using a number as the name, it will be mistaken as an SDN script. So the parameters are totally up to the scripter. For instance: -script 123:bank,loot,warriors It will be up to the scripter to take those script parameters, parse them, and apply the settings custom to his/her script. This will avoid the need of having a user interface which the botter would otherwise need to have settings. Example snippet: java -jar "osbot 2.4.67.jar" -login alek:password -bot alek@osbot.com:password:1234 -debug 5005 -script test:param1,param2,param3,param4 Additionally there were a few other things that were improved in the client, too lazy to continue typing. Enjoy. Version 2.4.68: -Patched issue with prefetchRequirements Happy Bot Farming! -The OSBot Staff

Yeah, and the year is 2012 and we all still enjoy Skrillex.

@Czar - Read the changelogs, I post them every update with a dev build. @Token - That may work for your specific dialogues, but DEFINITELY will not work for everyone. Use the dev builds, we're not getting another stable release anytime soon.