Preliator

Yes, you can do this by sending mouse events manually. For example, if you want the bot to instantly move the mouse down by 40 pixels, you can achieve this by using the following: bot.getMouseEventHandler().generateBotMouseEvent(MouseEvent.MOUSE_MOVED, System.currentTimeMillis(), 0, mouse.getPosition().getX(), mouse.getPosition().getY() - 40, 0, false, 0, true);

Yeah, it's for rs3 only. Limit is still 6h on 07.

Yes link is working now, thanks .

You should use org.osbot.Boot as your main class, or simply run "C:\Program Files (x86)\Java\jre1.8.0_40\bin\java.exe" -jar "C:\path_to_your_osbot.jar" I imagine you need multiple arguments for the proxy etc if you want to run org.osbot.BotApplication directly and skip the boot GUI (if possible).

Why is there a post count requirement to read the mirroring guide? I'm sponsor but I can't read it. I really want to test it :P

You can do the following: bot.getRandomExecutor().registerHook( new RandomBehaviourHook(RandomEvent.AUTO_LOGIN) { @Override public boolean shouldActivate() { return false; } } ); And if you want to allow the autologin to activate again, use the same code again but change the return false; to return super.shouldActivate().

Awesome, thanks for the update

Thanks, it's working great at the moment .

I often got the same error when hopping worlds. It seems like the event executor can get bugged after a while, causing the script to freeze. What I did is "renewing" the event executor every time before hopping (or in your case, before interacting with an inventory item) like this try { Field field = Bot.class.getDeclaredField("eventExecutor"); field.setAccessible(true); field.set(bot, new EventExecutor(bot)); } catch (Exception e) { } This completely prevented the error from occuring again for me. I imagine it would fix your problem too.

The answer is actually A, not B. After bouncing i times, the ball reaches a *height* of h(2/3)^i. However, it travels 2h(2/3)^i (twice the height) before reaching the ground again, since the ball travels up and down.

Just letting you know, osbot 1.8.15 is working fine at the moment. But yeah, I too do expect updates (and a dl link) since they said osbot1 would still be supported. I understand they want everyone to switch to OSB2, but right now osbot 1 is still much more reliable.

Amazing read. I think mouse movements are a crucial part of Jagex's bot watch. Since all scripts use the same API methods with the same mouse controller, all bots would have the same profile. If, according to your first quote, it would be possible for Jagex to compare profiles of different players, it would explain why Jagex is so good at detecting bots nowadays. What I think that needs to be implemented in OSBot: let all accounts have different bot profiles (different mouse speed, accuracy and mouse movement patterns). What also would be a nice addition, is that each bot could change its behavior at random times. For example, sometimes your concentration is good, at other moments you like to afk a lot or you are tired (thereby decreasing your mouse speed and accuracy). I thought about writing my own mouse controller too, but I failed (seeing your code, I can imagine why). So an amazing thanks for these snippets. I personally had the idea of recording my own mouse movements (say 300+ different paths). Then every time the bot moves the mouse, a random path is picked based on the distance that needs to be covered. Of course you will need to rotate and scale this path, but that's not a problem. Add some extra randomization and you would have amazingly realistic and undetectable mouse movements.

Got mixed feelings about this. At one side it's really great to see change (hopefully a better API and/or a client which is harder to detect), but I also feel that at the current state of OSBot 2 (bugs, high cpu usage) will not really increase the botting experience. But this might of course change in the future. By the way Laz, do you have any intention on adding Groovy support? I'm probably the only one that still uses it (and I love the convenience of lambda expressions etc), but I will be sad to see it go.

That formula doesn't seen to be right. This is the real max hit formula for a dds special attack: maxhit = floor(floor((5+(8+lvl+style)*(1+40/64))/10)*1.15) where style = 3 if you're using aggressive and 0 otherwise. So the required strength level for each max hit is: 17: lvl 79 18: lvl 85 19: lvl 91 20: lvl 97

Thanks laz! Good to see so many updates