Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 04/18/13 in all areas

  1. Have fun with your appeal.
    2 points
  2. Our development team has been extremely busy lately all working on separate aspects of the bot and improving our code along with fixing many of the frustrating bugs OSBot currently suffers from. I will list some of the new features for 1.3.x, featuring our biggest update to the bot's internal engine. Completely new and redesigned threading/concurrency control system.​ (This will fix all our freezing issues, improve stability, and many other bugs including onLoop() calls.) Enhanced new cross-platform GUI (Will improve the overall aesthetics of the bot and fix issues for users running operating systems such as Mac OS X or Linux.) "Already logged in" bug-fix. All broken hooks will be repaired. Destination hooks will be added for advance walking control. Improved/tweaked mouse/keyboard algorithms Unfortunately the SDN (script distribution network) cannot be promised at this time as the web interfaces are still be worked on. Be expecting it to be added to the bot soon however as we already a team dedicated to solely the SDN. P.S. We've hired an additional web developer. Expect the aesthetics of our website to be improved as well soon. The ETA for this update will be this weekend. Thanks, Laz and the OSBot Team.
    1 point
  3. Not yet. We will release energy methods soon. All there is at the moment is enabling run.
    1 point
  4. Well, we might as well just put it our here. We have a massive goal set once again for this week. We've done that in the past and managed to more or less meet our goals within time. We will try to do the same thing this week, however this time it feels as if it's even more and the impact of these updates will make us the best bot out there if we manage to pull it off in time. So let's get to the list: Client related goals: [*]Find the source of invalid logins / unable to login / unable to connect to Runescape. This bug happens only to a select group of users, however we want OSBot to be public to everyone [*]Find the left sources of any freezing issues. I have not encountered it myself, but will try to reproduce the bug and profile it to find its origin. It's most likely a crash of the RS client itself caused by injected callbacks. [*]Fix up the skill hooks [*]Fix up the facing uid hook so we can return the proper facing entity [*]Add facing coordinates, x and y [*]Add the character chat messages, both force chat (used for randoms and such) and regular chat (used to write an AI to talk with other players in RS in the future) [*]Add the ability to provide the walking method with a collection of Position objects to create custom selfmade paths and lower overhead [*]Add a proper enum for hitsplats [*]Add a canReach method not only for entity, which we already have, but also for arbitrary Position objects [*]Find and fix the origin of non running onLoop() methods. This has occurred to me in the past, however not after last update, so we'll once again have to reproduce and find the cause. Non client related goals: [*]Finish up the SDN portal where script developers can login to maintain, update and submit their scripts. Set up the logic on the client and server to handle access to certain scripts (like premium scripts), automatic updates on random event handlers and a secure mechanism of providing the OSBot client with premium scripts that will prevent leaking to protect the creators of the scripts [*]Randoms, like we said, we aim to have most if not all randoms with their first version updated through the SDN once it's setup After writing this list I realized we should stop writing more and put the effort into real code! Yours sincerely, OSBot.org
    1 point
  5. Err what? http://docs.oracle.com/javase/7/docs/api/java/util/concurrent/Phaser.html
    1 point
  6. Hello everyone, Today I have tested the mouse algorithms and they seem legit. It's a mix of all kinds of different algorithms to fool Jagex as much as possible with no fixed patterns whatsoever. Furthermore 100% support for keyboard input has been finished. The bot blocks all input from users when running, but allows all input when paused or terminated. We also have done all menu hooking, so we are pretty much set now to start writing all the methods you will need to script your own magnificent scripts so things will be going faster and faster from now on. Stay tuned! OSBot.org
    1 point
×
×
  • Create New...