Alek

So this is my first actual release without any help from the other developers, hopefully I didn't destroy too much. It appears that there were a few problems with the previous versions (2.2.29-2.2.30), all of which have been addressed. First, my API was never tested or even released. Today I did both; here you go: OSBot 2.2.31 @Alek's changes: -Overriden method toString() applied to Area -Added PointDestination class (extends MouseDestination) -Added click(int x, int y, boolean rightClick) -Updated move(int x, int y) -Added GraphicUtilities method isVisibleOnCanvas(int x, int y) -Updated GroundItem hover() to use point destinations Ground item interactions have not been changed -Added getPoint() to Ground Item -Updated Account Settings GUI to include random event solvers -Updated RSAccount class with random solvers Second, I've made a handful of improvements to the GUI: -Updated Script Selector GUI (continue button no longer disappears) -Added "Add Account" button to Account Settings GUI -Removing accounts from the Account Settings GUI updates the account list There have been a ton of changes which I probably didn't mention; I'll try and get the scripters new javadocs (updated API documentation) soon. Edit: Javadocs have been updated! Sincerely, The OSBot Team

I'm aware of the problems. When I get time off from work I promise to fix all these issues.

Click the maximize button on the window. I'll fix this in the next version; I'm aware of this bug therefore I will close this topic.

I will be getting off work in 3 hours, hopefully I can fix all the problems in less than an hour when I get back. None of my changes were tested (I'm assuming).

Once again I'm at work and cannot test my changes.

None of my changes are in 2.2.29.

Hey guys, I'm currently at work so I can/t type everything I want out. I'd just like to let you know that I was not able to test ANY of my updates because I was waiting on the updates from Laz as well. Provided my project is now fixed, I'll test all of my changes and make updates as needed when I get some free time. I'm on 12 hour shifts at work and I don't have a single day off for the next two weeks (in conjunction with uni). Please be patient, and yes random events are the first thing I'll be following up with (hopefully my new GUI made it to 2.2.29). -Alek

OSBot is down.

He had the area defined as a position. I showed him last night the difference between the two.

@dog_ where's the dislike button?

https://www.youtube.com/watch?v=WyVlmTClHPQ This with redbull + jager makes my work so much better.

Makes me want to bot a new pure.

OSBot 2.2.29: https://www.youtube.com/watch?v=W39uh3bCGYI For more information: http://osbot.org/forum/topic/59408-whats-new-osbot-api-developer-log-version-2229

Not a community topic.

Just some short news, the mods have cleaned up a ton of inactive topics; give them a big thank you. In addition, I've decided to do a forum restructure. There were a ton of arbitrary sub-forums and empty/near-empty forums which were consolidated. Hopefully forum users can find what they're looking for faster and/or a new place to make their posts. Some notable changes include: -Combined Magic + Prayer into one subforum -Complete re-work of the development section (which now includes graphics) -New "Support Section" -Spam generalized into "Chill Zone"

Here is some information that should help guide you: http://osbot.org/forum/topic/60660-osbot-1-scripts-and-osbot-legacy-api/

I botted for 13 months. Read my guide under Runescape Bans, I do exactly what I stated in there.

Please post this information on the script topic. You can find the topic by visiting the "Scripts" page and clicking the "Info" button next to the Add/Remove button. Sorry but there is not much we can do to help you in this section as this forum is used to resolve forum-specific issues.

I'll look into making a fix for this.

The walking should be pretty stable, but I would definitely test it before releasing it in your scripts. Let me know how it works for you guys.

It iterates to the positions closest to you, then continues to walk the path. @BotRS123 - It does everything except handle obstacles. @josedpay - I never use other people's code, defeats the purpose of learning

It's the osbot file, the same file which you click on to start osbot. For you it will be called something like osbot-2-2-28.jar or something along those lines. I rename my jar file to "OSBot2".

This update features a handful of new tools for scripters along with improvements to interactions. Additionally, a large portion of the bot has undergone many revisions in support of our future projects. Both scripters and botters should feel the positive effects of this release. If you would like to learn how to script, please visit these tutorials: Setup guide: http://osbot.org/forum/topic/60538-setup-instructions-to-start-scripting-very-easy/ Basic script guide: http://osbot.org/forum/topic/60535-osbot-script-skeleton-the-minimum-code-to-make-a-script/ OSBot 2.2.28 @Alek's changes: API - Scripters Only -Added localWalker methods walkPath(List<Position>) and walkPath(Position[]) -Added localWalker method waitUntilIdle() -Added localWalker method findPosition(Position p); (Finds a position halfway between you and the target) -Added Utilities class --Added utilities method getMinValue(int[]); (Finds the position of the smallest int in an array) --Added utilities method int[] convertIntegers(List<Integer>) -Added MoveMouseEvent(RS2InterfaceChild child) -Added NPC method hover() -Patched ItemContainer hover() method -Patched all Interactable hover() methods -All Interactable hover() methods are now boolean type Notes: The walkPath() method is very inclusive and may contain some bugs on the initial release. All - Scripters and Botters InteractionEvent by default checks if an entity is on screen before attempting to walk to it. Previously if an entity was on screen but met the distance threshold criteria, it would still walk to the entity. Scripters can override the isVisible default check by setting the walkingDistanceThreshold in InteractionEvent. Notes: The InteractionEvent change has been tested but as always, cannot be fully tested until it reaches the masses. Shout out to for all the bug reports! Thanks for using OSBot -The OSBot Team

We will be using the IDE called IntelliJ. Step 1: Click on new project Step 2: Click on Java Step 3: Don't click on template, just click next Step 4: Type in your project name (it will contain all your scripts) Step 5: Click src> New > Java class Step 6: Type in your script name Step 7: Go to project structure Step 8: Make sure you are using Java 8 Step 9: Click on libraries, then click on the plus button, then click on "Java" Step 10: Find your OSBot file (.jar file) - The same file which you click on to start the bot. Step 11: Confirm Step 12: Click Apply/OK. After that you may get a language level message, accept it At this point your IntelliJ is set-up to create scripts. After this point, you will learn how to build the actual script. Step 13: Click Build > Compile Step 14: Find where the file got created, then copy it Step 15: Copy the class file(s) and paste them into your OSBot script folder Step 16: Reload your scripts, and you're done

objects.closest("Bank chest").interact("Use"); This method looks for an object called "Bank chest" and attempts to interact with it using "Use". If you attempt to interaction with the "Bank chest" using "Attack", the method will not work because "Bank chest" does not have the action "Attack". npcs.closest("Guard").interact("Attack"); Lets say you are killing guards, as the method shows above. What happens when you kill all the guards and this method is called? You will get an error called a "Null Pointer Exception", meaning that the method was called but it didn't work because the object reference (in this case the Guard) is null (meaning it doesn't exist). Here is how we would solve that problem: NPC guard = npcs.closest("Guard"); if(guard != null){ guard.interact("Attack"); } Here we create the NPC reference called "guard" and we define it using the npcs.closest() method. Now if npcs.closest("Guard") can't find any guards, "guard" will be defined as null. This information is used in the next line where we check if "guard" is null, meaning if no guards exist. If there is at least one guard that exists (not null or != null), we will interact with the guard using "Attack".