Alek

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.

Post in the scripting help section.

Ask the script writer for help. If you're writing the script then perform proper debugging.

I'll consider it.

I didnt do it

@Christopher - It was bad because of the way web walking is designed. 1. There are internal distance checks to the destination which are NOT arbitrary numbers, but based on the pathing algorithm. 2. If he's using an area as the destination, I wrote it so it returns if the player is in the area... not checking distance to some random position. 3. It's kind of spaghetti, not really checking and using events properly. Not trying to bash, hopefully that clears some things up.

Doubt he's going to need the full package anytime soon, he'll be fine with just the JRE.

What do you need INodeRouteFinder for? @Christopher - That's a really bad way to use WebWalkEvent.

Yes, I'm working on the system. It will even start up a script for you.

Version 2.4.65 Release -Patched small issue in Worlds class -Added Client isHumanInputEnabled() -AutoLogin now re-attempts initially with a quick-login (~20 seconds) if you were disconnected from world hopping -AutoLogin various improvements -Boot login flag allows names with spaces. Replace the space in your name with an underscore

Probably the space in your name, thanks for letting me know.

The dev build will become the stable build if there aren't any major issues with it. You can download the dev build right now if you'd like.

First time seeing a ban message? Same copy pasta since 2002.

Version 2.4.64: -Fixed human input enabling/disabling -Removed Antiban class (forgot to last update) -Patched an issue with Chatbox isVisible(), may fix some issues with world hopping

No? It's a dev build.