Alek

Or use localWalker.walk(area.getRandomPosition))? There's no sense in using paths for every scenario when you can have the walking event auto-generate one using DCPF.

<start of first paragraph> <bold this text1>This my first row </end bolding text1> <bold this text2>And this here is my second row, under it should be a picture </end bolding text2> <image> </end of first paragraph> Above is essentially what you are doing. The lines aren't separated because you never separated them. Code is only sensitive in the order in which you placed it. Looking at the above code and what you posted, the output is accurate. To have columns, you might want to either make a table or use CSS. More info: http://www.w3schools.com/tags/

What rows?

Not sure why you are casting NPC or why you are using arrays in the constructors. Try this: NPC monk = npcs.closest("Monk"); if(monk != null){ monk.interact("Talk-to"); //Conditional sleep until dialogues.isInDialogue(); dialogues.completeDialogue("can"); } Dialogues API: http://osbot.org/api/org/osbot/rs07/api/Dialogues.html

Thanks for this report. I have a pretty good idea of what's going on, there should be a fix for this on Friday.

We're not using static interfaces, however this does help me understand a bit on what's going on. I have a few ideas on permanently fixing all dialogues, just going to run it by Maxi.

I could certainly modify the events to permit for a speed setting. Look for an update around the weekend (probably Friday).

You're not being cynical and yes it's one of the many reasons. The other reasons include common disagreement between the parties involved (purchaser and scripter). We simply can't enforce every individual agreement between the two; it's already a full-time job doing so for the market. If you decide to participate in private sales, just ensure you understand that the staff will not help you if the trade goes sour. Also, we normally don't like to punish our members over it but solicitation can warrant some hefty warning points. You know how ridiculous this is right? None of us would even want to look at the code for Timmy's Karambwan Buyer. Private scripts are generally written just enough to work so the scripter can cash out while public scripts require much more maintenance.

By popular request, the Grand Exchange API has been created. With 20+ methods in this new class, scripters are afforded a great deal of flexibility. Since this is brand new API, I'm sure there may be a handful of methods missing so please ensure you make API Suggestions here. To view the Grand Exchange API, click here. @Alek's changes: -Created GrandExchange API @Maxi's changes: - Changed BFSWalkableArea and CircularPathFinder to use an extension of java.awt.Point that uses a custom hashCode() method. - Adjusted Widgets#isVisible to not only check for active root id's but also for drawn childs. - Fixed camera event to turn to entities on the edge of the map viewport (previously it would not work for entities with a distance bigger than 15, it now uses position#isOnMiniMap(). - Fixed WalkingEvent to return if the next tile remains the same for a certain amount of cycles. - Fixed MiniMapTileDestination#isVisible() and #evaluate to actually return correct values - Added a failsafe in the InteractionEvent if minimap walking failed to use main screen walking - Added a failsafe in the WalkingEvent if the minimap walking failed to use main screen walking Have a great weekend and Happy Botting! -The OSBot Staff

This issue has already been resolved in an update from over a week ago. I'm guessing you were only recently forced to download the new update?

For as long as I can remember, the account database where you store your RS Account details and preferences suffered from potential deletion every OSBot update. The reasons are a little bit technical and although it was possible to patch the old system, I decided to make a new one. Please note that just like the old system, the new system will store your information in plain text locally. Never give anyone your OSBot files (store.dat, accounts.dat, etc). For advanced users, you can directly modify preferences by opening accounts.dat. The format is currently as follows: username,password,pin,exp,breaks,avgInterval,avgBreak,intervalDeviation,breakDeviation,dismiss_randoms So for instance: test1@aol.com,password1,9999,MINING,f,2,2,2,2,t I know there are a few "mega-farmers" out there that would really appreciate this. TL;DR: You will lose all your account data this update, but future updates will not affect the new account database. In addition the Settings API is going under a huge re-work. Soon scripters will be able to enjoy the full functionality of everything in-game settings has to offer. Changelog: -New account management system -Added SettingsTab enum to Settings --Contains Display, Audio, Chat, Controls --Added Settings method open(SettingsTab) --Added Settings method isTabOpen(SettingsTab) Have a great weekend -The OSBot Staff

Ah, now I understand. I'll keep this open until I add it. Thanks for the suggestion!

getCombat().isPoisoned() ?

If it's a general connection issue, it will attempt to log in about five times. You might want to get your internet checked out or consider not botting on such an unstable connection.

12 March 2015: Before I worked on the response code callback and listener, I was really interested in having the welcome screen operate purely based off of color. Although a lot of people don't completely agree with me, I would much rather sacrifice speed for stability. I did eventually opt to use response codes for the welcome screen, however my interest in creating an OCR application didn't fade away. Here is a pretty early version of my program analyzing a screenshot of the welcome screen: I want this program to be fully trainable. Currently there are a few other OCR applications out there that are very powerful, but suffer from usability and design. How it works: A folder is a "font pack" and each image in the font pack represents a character; e.png, E.png, a.png, etc. The image is a simple black and white of the character and the program reads it to create points of reference. Training it is very easy but it lacks "character construction". This means that if the letter is not the correct size or is slightly distorted, the program will fail to read it. Scanning documents and reading them is probably out of the grasp for this project, however reading text from games will be very achievable. Some goals: -Attach to applications -Option to detect text without defined color (will be slower) -Process multiple files -Synchronize multiple image processors 20 April 2015: I've finally had a bit more time to work on the project and it's coming along nicely. There are a few optimizations made but as of now the code will remain messy until generating the text is perfect. 21 April 2015: I finally have the complete methodology accomplished, just need to work on some serious optimizations and cleaning up the code. 23 April 2015: I decided to wrap up the project and host it on my site. To download and view the instructions, click here. There are a bunch of features and optimizations I would have liked to add, but as it stands it's sufficient.

Power chopper script with super anti-ban technology: loop: checkStats(); sleep(random(1813,2832); moveMouseSlightly(); sleep(random(2342,3312); moveMouseOffScreen(); sleep(random(981,2231); typeRandomly(); sleep(random(2221,8535); woodcutting.cutLogs(); sleep(random(99923,100324)); checkFriendsList(); sleep(random(1003,4002); examineRandomObject(); sleep(random(3424,9921)); checkAchievementDiaries(); sleep(random(918,3412)); woodcutting.dropLogs();

I don't know what this is about. Could you please link me to your bug report thread?

The Mirror Client BETA testing has been going quite well considering how massive the project is. Thank you to everyone who is making bug reports as we transition from the beta versions to stable versions. @MGI made a ton of patches this release to the mirror client and the list is far too large to contain in this post. Once again, thanks for all the support and continue making bug reports for both the mirror mode and standard mode. Changelog: @Alek's updates: -Added more dialogues -Deprecated InterfaceComparator -Added WidgetComparator @MGI's updates: -Mirror client fixes Edit: There was a corrupt version on the server. If you are having issues please re-download. Happy Botting -The OSBot Staff

It's not a mirror client error, its a GUI error with the updater.

Although I'm far from a mechanic, I'm always willing to try something. With that said, I went to go tighten my AC belt to see if it would fix some squealing noise I was getting. Of course I forgot to loosen the nut holding the pulley in place and the plastic tensioner broke thereafter. The local mechanic shop offered to fix it for ~$200... yeah right! I ordered the plastic piece which broke which came with a new pulley, $10 with shipping. After that the entire pulley came out so I could replace the parts: Thanks to my friend rust, I broke a tool in the process. Fortunately I was able to replace everything: Unfortunately since I broke my tool, I wasn't able to tighten it back in the car. My dumbass decides to drive with it loose and a bolt came loose vanishing onto the German highways. I was going to order the part and wait about 2-3 weeks for delivery (after searching junk yards with no luck), but I remembered a Subaru dealership near me. After heading to the dealership and buying the part for 1 euro (and giving him a 4 euro tip), I was finally able to complete the project: Estimate by repair shop - $200 My costs: -$10 for parts -$5 for more parts -$10 for new tool set Total $25 + new tool set + additional replaced part

Similar to MessageListener that listens for messages in-game, the LoginResponseCodeListener listens to response codes on the login screen. Below are a few of these codes: INCORRECT_USERPASS ACCOUNT_DISABLED GAME_UPDATE FULL_WORLD STOLEN_ACCOUNT BETA_WORLD CUSTOMER_SUPPORT BLOCKED_COMPUTER As you can see, there are a variety of codes that both developers and script writers alike can use to improve your botting experience. Immediate implementation of these codes is apparent in the AutoLogin solver. When attempting to log into the game, the response code listener will check to see if such codes are received. If they are, they are evaluated for the best course of action such as: 1. If the world is full, wait a minute to try re-connecting. Do this a couple times and give up if there have been too many attempts. 2. If your account has been banned, don't try logging back in. 3. Error connecting to the server, try re-connecting in a few minutes. Implementation (for scripters): @Override public void onResponseCode(int code) throws InterruptedException { } Also check the ResponseCode listing. Changelog: @Alek's updates: -Added LoginCallback --LoginResponseCodeListener onResponseCode(int code) --Added constants class ResponseCode -Updated AutoLogin solver to handle various response codes -Updated Dialogues class @Maxi's updates: -Added containingActions to Widgets -Updated Trade API Happy Botting -The OSBot Staff

I don't see a video.

Wrong place, plus it has already been reported.

Nice GUI and paint; I love simplicity.