Maxi

It was not exploited and is now patched, so more reason for you to use the latest version ;).

Added on to our list of nice future features.

I won't even start correcting the post directly above me, been there and done that too many times with others, yet I'll summarize it for you. This is all based of assumption and research but one part will never be proved as we don't have Jagex their source code, there are two aspects to this entire story: One, The RS server (up to revision 570-570'ish, this doesn't apply in clients with GPI updating and on) handles its players in some form of collection where it loops through to when creating the update package in order. You login and you will receive the first empty spot in the collection, this can be 1'st, this can be 1000'th etc. Being earlier in the collection will get your player's actions processed first, which is believed to possibly create a gain over the other in interaction (in this case, staking) but there has never been hard prove for this. Two, your internet connection. Data over the internet travels with a limited speed, based on overhead in your router, based on overhead in your computer, based on overhead on the link between two connected nodes etc etc. Obviously, if your connection with the RS server is better than your opponent's, chances are that your data will arrive at the server earlier. This still doesn't give an advantage, unless the following happens: the connection from the opponent is that much slower that it arrives at the server end that much later that it gets processed one server tick cycle later (their server ticks at 600ms). In that case, you see a difference between animations, one player being attacking the other a tad bit earlier giving the advantage. The story about IP's, in all honesty and no offence, is completely wrong. Also, PID = player index.

Hi everyone, I'm posting this thread to give you all a heads up why Laz, Zach and I have not been around for the past 3 days. OSBot will continue with the same dedication, all three of us had to attend IRL duties (family, studies, etc..). Usually this never happens on the same days, but this time it did. Kati held our force strong! Sincerely, OSBot.org

Like Zach mentioned, can we please start including logs from the log file because we can't do anything if we can reproduce your issues, if we don't have your log files.

It was patched on 1.7.1.

Due to the recent update from Jagex and some other important matters I have to delay this devoted day to friday/saturday.

Hello everyone, We are proud to announce that BETA v1.7.1 has been released! Today when I got online RS just updated and we managed to update the bot within no time. There were 2 broken hooks of the 200 we have, these were patched up shortly after. Two days ago we decided to do some research to find a reason as to why there has been a higher ban rate recently which affected several bots. We have made OSBot less detectable. Another interesting not is that we have separated some of OSBot's dependencies from the jar. The client will now download some of its dependencies on startup if they have not been downloading before. This reduced the size of the jar from 14MB to 5MB. Also, the client will now for everyone to run Java 7 to prevent the countless help posts about this. With this version we introduce the usage of a color picker and access to the colors of the canvas in case you need it in specific cases. This can be found in the Client class. Furthermore, world hopping has been added and is very easy to use in your script: worldHopper.hopWorld(world); To continue with awesome features, OSBot now support breaking and is completely handled for you and it's written as a RandomEventSolver to give you easy control over the mechanism from your script if the bot is not ready to break, for example if it's still fighting. And then we also added a fully fledged config debugger to make config debugging as user friendly as it can get: For randoms, due to the recent events of the last couple of days, most work on finishing up the last bits to make them 100% altogether has been delayed slightly. However the following randoms have been updated and have been verified to work: Frog Queen (outside cave) Maze (broke after the update, it has been programmed more securely to survive future RS updates) The issue with the order where random event solver were evaluated in is fixed now. Besides all the aforementioned updates, there have been many more updates that I currently can't think of. Expect us to work on randoms in the coming days to make sure every last one of them works as we expect them to work. Thanks for reading, OSBot.org

I'll look in to it once our main priorities with updating are done

They should use closestObjectForName() methods for everything that has a name and is possible in its current context, this way changes to id's won't affect scripts. Some scripts have no other choice, however they could use information about models for example to catch this.

More like 1 hour after . We will look into the issue of the login screen.

Hi all, Please note that Jagex has updated many of the object id's, and perhaps other id's as well, with their update of June 6'th. Good practice would be to use names for most entities like npc's, ground items and objects, but in cases where it's not possible to do so make sure you update your scripts if any of the id's you are using are updated. Sincerely, OSBot.org

Did both of you restart your bot?

Hi everyone, I have just updated the hooks and if you restart your bots everything should be back to normal again. However, we can't guarantee this is the case as I have not had the time to check and test each and every hook, although my script is running again for the last 5 minutes with no problems. Also all debugs are verified, so as far as I can tell we're all set until their next update. As usual, we are the first again . Steps for you: 1. Close your bot 2. Start your bot 3. Repeat if it doesn't work the first time (usually will) If you find any problems with any of the hooks, please report so in the bugs section. Happy botting, OSBot.org

Hello everyone, For the past couple of days we have had to focus on many of OSBot's internal features, updates that are not visible to your eyes as it doesn't change how the bot works at all, but do contain some crucial updates that we can not share further information on. Also a couple of very long awaited features such as a breaking system and the ability to hop worlds were added. Therefor, OSBot has made some important steps again, although now most of this is done randoms deserve or better put need attention again. So tomorrow, I will devote my entire day again to fix up the latest issues with some of the random events. But I need your help! So when you come across randoms tomorrow, share your accounts so I can fix or/and improve them. Specifics that I'm aware of that I'm especially looking for tomorrow are: Molly Evil Bob island Freaky Forester Lost and Found (Abyss teleportation random) I'll update this thread tomorrow with a status update whether I'm around or not. Edit: I'm delaying this until the Saturday the 7'th as I have some unfinished work that needs finishing up first, or I'll start today once I'm finished. Thanks, Maxi

Today I finally got around to finishing up the world hopping system. This was also a nice moment to bring the random management system in to action. For anyone interested in the random management system in action code wise for the world hopping system, here you go: package org.osbot.script.rs2.ui; import org.osbot.engine.Bot; import org.osbot.script.mouse.RectangleDestination; import org.osbot.script.rs2.randoms.RandomBehaviourHook; import org.osbot.script.rs2.randoms.RandomManager; import org.osbot.utility.Gaussian; import java.awt.*; import java.util.ArrayList; import java.util.Map; /** * Created with IntelliJ IDEA. * User: Maxime * Date: 26-05-13 * Time: 19:24 * To change this template use File | Settings | File Templates. */ public class WorldHopper { private final Bot bot; private boolean isHopping = false; private int nextWorld = -1; public WorldHopper(Bot bot) { this.bot = bot; } /** * Logs you out and changes hops to the world specified. This method does not take in to account full worlds yet, * so hopping to a full world will fail. * @param world Worlds range from 301 to 378 but remember that the worlds * 307, 315, 323, 324, 331, 332, 347, 348, 355, 356, 363, 364, 371, 372 * do not exist. */ public void hopWorld(int world) throws InterruptedException { nextWorld = world; isHopping = true; bot.getScript().randomManager.registerHook(hook); while (bot.getClient().getLoginState() != 10) { if (bot.getScript().logoutTab.logOut()) { Thread.sleep(500 + Gaussian.random(300, 300)); } } } private static enum State { GO_TO_SELECTION, WORLD_SELECTION, UNHOOK; } private RandomBehaviourHook hook = new RandomBehaviourHook(RandomManager.LOGIN_SCRIPT) { private State state = null; @Override public String getName() { return "World Hopping"; } public void scan() { if (!isHopping || bot.getClient().getLoginState() != 10 || nextWorld == -1) { state = State.UNHOOK; return; } if (bot.getClient().getColorPicker().isColorAt(54, 294, Color.BLACK)) { state = State.WORLD_SELECTION; return; } else { if (bot.getClient().getCurrentWorld() == nextWorld) { state = State.UNHOOK; } else { state = State.GO_TO_SELECTION; } } } /** * The main loop logic. This will continue until shouldActivate() returns true or * -1 is returned. * * @return The time to sleep until the next loop. * @throws InterruptedException */ @Override public int onLoop() throws InterruptedException { scan(); switch (state) { case GO_TO_SELECTION: bot.getClient().moveMouseTo(new RectangleDestination(new Rectangle(12, 466, 86, 26)), false, true, false); return 600 + gRandom(200, 200); case WORLD_SELECTION: Rectangle dest = getWorldMouseDestination(nextWorld); bot.getClient().moveMouseTo(new RectangleDestination(dest), false, true, false); return 600 + gRandom(200, 200); case UNHOOK: nextWorld = -1; isHopping = false; bot.getRandomManager().unregisterHook(RandomManager.LOGIN_SCRIPT); return -1; default: return 500 + gRandom(500, 500); } } @Override public void onExit() { isHopping = false; nextWorld = -1; } }; /** * Calculates the rectangle of the destination to click a world. * @param world The specified world in the range of 301 - 378 * @return The rectangle used for the mouse destination */ private Rectangle getWorldMouseDestination(int world) { ****** } ***** static { ***** } } Furthermore I started on a breaking system. You will be able to set your break settings per saved account profile, which will then be used if you enable it. Expect both updates to be released tonight or tomorrow, Sincerely, OSBot.org

He was warned a week ago, although continued selling work that is not his. We have to protect our script writers. I'm closing this now as I see no further need to discuss the topic.

Before Xerion his AutoHunterPro was released on the SDN a select group of people received the script to test, under who amongst was Apple. Apple has been selling this script without permission to users of OSBot and breached all of our trust. I want to make a couple of things clear: If you are the buyer of this script, I feel sorry for you as we can block any script in any way, shape or form from our bot. We decided to block this pre SDN release version of the script, this will happen some time this week. If you are the buyer of this script 'illegally', you did not only break the rules at OSBot, you also bought yourself a pile of shit as you can't use it any longer. If you are distributing this script for money, please be aware of the fact that if we come across it, will not hesitate a moment to stop any currently on going services we supply to you. Now this is out of the way, we can happily continue with botting .

If there is nothing valuable to read here, I'm going to close it.

Congratulations to all of us!

Delete and re-download and try again?

Goodfight :p

This has already been adressed in the VIP section twice and answered twice as well.

Using our own accounts and your accounts we could not reproduce the problem, so I can't tell you.

Hi everyone, This release is mostly some bugfixes that were introduced in v1.6.4: Reverted a new immature system that we will put back once we test it more, this system was to get proper interactions with stacked characters as sometimes stacked npc's would lead to no available model data causing our interactions to break. The system to tackle the problem however has some issues. The above issue broke interactions in general, thus breaking many randoms too. They should be back to normal. Fixed an issue in the random management system. Added a combat instance in method provider, containing little to nothing, besides a method to get your special attack energy and a method to check whether your special attack bar is activated. I have added another debug option to the advanced settings tab, this will allow you to debug configs without using a script. Download can be found here: http://osbot.org Sincerely, OSBot.org