Alek

private Position[] path = { new Position(3254, 3421, 0), new Position(3256, 3428, 0), new Position(3264, 3428, 0), new Position(3273, 3428, 0), new Position(3277, 3426, 0), new Position(3281, 3422, 0) }; getWalking().walkPath(path); Explanation: The position array listed above will be defined at the top of your script (with the other variables) and getWalking().walkPath(path) will be defined wherever you want to call it (such as in a method, in your onLoop, etc.). Getting positions: Click on the settings gear icon in the client and scroll over "Entity debugs" and then toggle "Entity hover debug". Hover your mouse over a tile and it will show the position of the tile. The third number in the position constructor is the "Z" coordinate, meaning the current plane which you are on. Order: The position array has a list of positions with the first position being where your character will start walking and the last position being where your character will end walking. Add positions in a manner where once your character reaches one position, it can find the next position on the minimap. Additional: If your character starts in the middle of the path, it will not walk to the beginning, it will resume until it reaches the final position. If for some reason your character gets off the path, the walkPath() method will attempt to get back onto your path.

import org.osbot.rs07.script.Script; import org.osbot.rs07.script.ScriptManifest; import java.awt.*; @ScriptManifest(name = "Skeleton", author = "Alek", version = 1.0, info = "", logo = "") public class Skeleton extends Script { @Override public void onStart() { //Code here will execute before the loop is started } @Override public void onExit() { //Code here will execute after the script ends } @Override public int onLoop() { return 100; //The amount of time in milliseconds before the loop starts over } @Override public void onPaint(Graphics2D g) { //This is where you will put your code for paint(s) } }

The recommended video list is always crap like this:

True for koth

Don't worry guys, I'm going to be dedicated purely to the old school client. There's still a lot I'm learning but I think we're in a better position now than we were a few months ago.

Please read the announcement: http://osbot.org/forum/topic/60481-rs-update-september-18th/

message.getMessage() returns the string you are looking for. message is the object.

The scripter was banned again, so most likely no.

We are having the return false for activating until we make the GUI for selecting which randoms you wish to solve.

That isn't Linkin Park. This is:

It could also be the interaction method itself, which I don't think is particularly good. I plan on doing a large overhaul on interaction events soon.

After the release of 2.2.26, we received notification of various problems arising from both the release and from other previously unreported issues. With that said, I'd like to announce 2.2.27 which should fix and stabilize many of the concerns you submitted. OSBot 2.2.27 @Alek's changes: -Added position method isOnMiniMap(Bot bot); -Re-wrote setting method setRunning(boolean run); @FrostBug's changes: -Patched deprecated Spell enum -Patched EntityDestination For scripters, please keep using the Tracker. For the botters/community members, please keep on using the appropriate forums to post bugs, glitches, and suggestions. We may not always reply, but rest assured we are looking. Thanks for your support in making this update happen, we rely on our community to make this bot grow. Kind regards, The OSBot Staff

.

I was waiting for my youtube video and I sat down and watched the full advertisement. http://www.mrporter.com/content/johnnie_walker_blue_label

No you do not. You can still use "Spell.Spell", however it's deprecated. The new method is Spells.Spellbook.Spell.

I'm going to be recompiling all the scripts shortly as well, FrostBug brought to my attention a few errors. This won't require a new download or even a restart. Edit: Most scripts have been recompiled.

Yes, please download 2.2.26. Do not use 2.2.25, there was a merge error and a few other bad things which happened.

Yeah we are pushing Version 2.2.26 in a couple minutes. Read the original post again. Sorry about the double update (again).

This release was mainly to patch up the random events so our executors no longer try and solve them, as they are now optional. In the future we plan on adding a selection screen to select random events which you wish to solve. In addition to random events, Magic got an overhaul to allow for multiple spell books. @Alek's changes: -Disabled random events from activating -Rewrote magic api to allow for multiple spell books --Spell is now deprecated --The new convention for spell is as follows: Spells.Spellbook.Spell @FrostBug's changes: -Patched entity interaction @Xerion's changes: -Added Ancient Spellbook @Laz's changes: -Reverted WorldHopper So just to recap the new API: - "Spell" is now deprecated - Use "Spells.Spellbook.Spell" This update was more of a maintenance update while we are working hard behind the scenes on some bigger projects. Thanks for being a member and like always, have nice day. Edit: OSBot 2.2.26 Released: Patched a few quick things, @Xerion released the ancient spellbook, @Laz reverted the WorldHopper. Sincerely, The OSBot Team

Welcome back redeye. A lot has changed and been added to the API. Make sure to check it out

You should invest into a better car. They lose value but are responsible for protecting your life and getting you to and from work/uni.

"A simple script that farms at all five patches and can run for weeks at a time". You have a lot of ambition but I think for your first script, you should start with something MUCH easier. Farming is actually quite hard (to at least get it right). It seems you are also unfamiliar with the API and how RS botting works (this bot works similar to a few other bots in the terms of general mechanics). You should start small, for instance your explosive potion collector. Despite my strong recommendation, is correct. You would use the child interface of the Magic tab. I was considering adding Lunar's and Ancients, however I'd have to do an analysis of how many scripts would break as a result of it.

We're working on a few things to potentially help with the ban rates. Some instances we are very certain, others we are hypothesizing off of good judgement. No, it isn't injection versus reflection. We're also going to slowly roll out the updates and try to keep it a low profile so the competitor bots don't catch on.

It depends on your account. If you've had your account for a few years they'll let you off with a 2-day, otherwise it's probably perm. You should really read the news articles on the front page of oldschool, they already explained this.

FYI shout-out to for being an active member on the bug tracker. You provide me with a handful of tasks to complete which is really appreciated.