Jump to content

Laz

Suspended
  • Posts

    775
  • Joined

  • Last visited

  • Days Won

    33
  • Feedback

    100%

Everything posted by Laz

  1. Ericthecmh committed it. Please talk to me in private if you or dreamliner have any concerns. Edit: Both you and DreamLiner have been paid for it.
  2. Hello community, this release is one of the best updates ever released, providing definite improvements to the realism & stability of the bot! Also previous builds of OSBot are unstable because an injector broke as a result of the latest #55 RS update. Here's the list of changes: New, more realistic mouse algorithm!@author DreamLiner Issue with minimap clicking has been fixed!It was too slow to move the mouse before when running/walking/moving the camera around! @author Laz Interaction events are now more stable! Maze random solver has been patched! Bank.depositAllExcept has been patched! a new DepositBox API has been added!@author Ericthecmh Added Settings.areRoofsEnabled() && Settings.toggleRoofs(boolean) Combat API has been rewritten and contains new features!@author Alek Thanks, have fun botting! Sincerely, Laz and the OSBot Team! Edit (@Alek): Combat: -Deprecated setSpecialAttack -Deprecated activateAutoRetaliate -Added toggleAutoRetaliate -Added toggleSpecialAttack -Updated isMultiway -Updated isWilderness Settings: -Added areRoofsEnabled -Added toggleRoofs P.S. A YouTube video will be released this weekend demonstrating OSBot's future web walking capabilities!
  3. Hello community, even though I've released the updated hooks for revision #55, it seems that our interface injections have broken and therefore many trivial things do not work! I am currently investigating the problem with the injector and will release what would have been yesterday's update. Also, to those who are upset that no update was released yesterday, two updates will be released today. One after the injector is fixed (which also includes lots of changes by Ericthecmh & Alek) and another one today to catch up. Thanks for your patience! The bot should be updated shortly!
  4. It's so that if you think you might get banned and would like to save money by paying only for what you use. Basically it makes buying scripts easier but it won't be mandatory (i.e. you could keep paying monthly or switch to pay-per-use). The feature hasn't been released yet.
  5. OSBot 2 didn't meet our proposed deadlines because one, we were very eager with our ETAs and two, because writing/developing/maintaining/debugging/testing a bot takes a LOT of time, the majority of that time wasted on simply debugging/testing. Also I never stated it would be COMPLETED by December 2013. OSBot will never reach a point where it is COMPLETED. Why? Because there's ALWAYS room for improvement.
  6. Hello community, this release is for yesterday as I started promising daily updates for OSBot. This build features a couple of fixes I've been working on including a much more accurate isVisible() method which improves interaction handling significantly. Also the mouse algorithm has been tweaked slightly to show more realistic slow-downs and to look more human-like. For strange plant the bot now waits until the fruit is nearly or ready to be picked based on the plant's height. The internal antiban in the client has been adjusted slightly to behave differently. Another update is coming tonight (specifically the auto-updater w/ improved bank scrolling). Thanks, Sincerely, Laz and the OSBot Team.
  7. Hello community, lately you may have heard the "API team" we have here at OSBot. If you didn't well it was a group of some of our script developers. A few weeks ago I invested a couple hours of my time into modularizing OSBot's code so that a couple of developers could help me fix bugs faster than I could just alone by myself. Well for some time they were committing various miscellaneous fixes and some small nifty additions but recently have stopped committing their "fixes" due to the fact that they now want to get paid extra compensations for these fixes. Ideally I would like to hire some extra muscle around here to help with OSBot's development but the reality is that our user base has shrunk and we're not making nearly as much profit as before. I've asked the script developers on behalf of our current customers/users to commit their changes for free out of kindness, especially since OSBot is the foundation for their own commercial scripts. But because the proposed API team wants unrealistic compensation for minor bugfixes, no deal has been reached. Therefor I would like to optimistically announce that from now on OSBot will feature daily builds every day from Mondays - Friday. On top of that all the bugfixes that the private team has refused to commit to OSBot's codebase will simply be done by me instead. I want this community to understand that I personally love working for OSBot and I'm extremely eager to be working on our current products and planning/developing our future products. I work very hard and am too dedicated to this job and will not stand by and let others destroy it. On top of the fact that the developers will be fixing the bot's bugs ourselves is the assurance that we know what we're doing with our code. In my honest opinion, the API team that was proposed has decent scripting skills but other than that not much. Botting is more than just knowing how to script and requires knowing how RS's internals work thoroughly and understanding. Now, I'm not trying to to offend anyone here, but simply outlining how this business should be working. The developers have been fixing the bot's bugs up until now but it takes time to fix everything. Nonetheless, I am promising daily updates every day from Mondays - Friday. I'm also going to outline some of our current goals/projects: Dynamic walking/web walkingWe've been talking about this feature for quite some time but because we've prioritized stabilizing our current API it has been delayed for some months now. This project is quite big but OSBot is fully capable of having it fully implemented sometime soon. More updates/sneak peaks at web walking will be released this week with more information regarding the project. Mobile bottingWe're going to start developing some tools/apps for mobile phones/browsers to remotely control your bots and to notify you of situations like random events, script errors, and more. I have been planning mobile botting for months now and am fully ready to start working on it. The final outcome will be extreme control over bots and statistically lower ban rates. Passive scripts/in-game enhancementsThis is a nifty idea we've been thinking about for some time now. The idea is so that you could select certain scripts to be enabled at a single time and they'll work together to produce the final outcome (i.e. gameplay). This expands OSBot not just into the botting market, but the custom client market where players like PKers use passive scripts like next hit predictors, and also psuedo-gamplay (where you can control your bot using custom interfaces to speed-up gameplay; example: walking across the map, etc.). Second generation scriptsSecond generation scripts will be scripts which are much smarter than our current scripts. These scripts will be able to interact with the API to let it know when it CAN and CANNOT run efficiently. Additionally the scripts will know the ideal starting locations and will use our future webwalking API to traverse to those areas in between scripts as well as handling deaths. Another feature is that OSBot will be able to suggest certain scripts based on your current state in the game (hint: this will boost script sales especially since pay-per-usage botting will be implemented soon) Script schedulerThe final outcome of all these proposed changes will be the script scheduler. This will be the ultimate tool against getting banned and we are rushing to get everything ready for this. The scheduler will allow you to schedule scripts at certain times/intervals and allows switching skills/scripts automatically (for example: a tab maker could switch automatically to a mercher to sell its tabs) Now you may think that this is just hype but regardless of your opinion, OSBot is here to stay and I am here to make sure of that. These projects are all basically inter-dependent and take time but just know that we're always working very hard on our side to compete with other bots and making botting as easy as possible. Thank you so much for our loyal customers. OSBot could not exist without you and we're eager to give you more! Moreover OSBot will eventually expand to RS3 botting. Most of the tools developed for the OSBot will be reused and re-implemented for the new RS3 API and eventually OSBot will be part of a bigger father company which controls both an OldSchool and an RS3 bot In conclusion, this ends my little developer blog. One thing I want to change here at OSBot is all the negativity going around about how the way we work. If you don't have something positive to post here don't post at all. P.S. A 2.2.9 is coming out tonight with many API bugfixes that the API team has claimed to have fixed because I want OSBot to be independent! We don't need to rely on anybody.
  8. Hello community, the hooks for OSBot have been updated for the latest RuneScape update. OSBot should be ready to go now, just restart your bots. Sincerely, Laz and the OSBot Team.
  9. The issue is still being debugged. Interactions still work though.
  10. Hello community, this release features a patch for the pinball random solver which fixes an issue with the bots exiting the cave. Also the API has been merged with the latest commits of the API devs. Some fixes in the trading API were added. Thanks, Sincerely, Laz and the OSBot Team.
  11. Hello community, this update features a fully working break handler that may be configured per RS account in the settings menu. Additionally, the following random solver were patched: Freaky Forester (had an issue with dialogues) Run away from combat (did not wait long enough before) Also some patches for the API including trading were added. Have fun botting! Pretty much every random event solver is operating smoothly. Sincerely, Laz and the OSBot Team.
  12. Lol it only happens once and its because your local OSBot store/save was being encrypted incorrectly in previous versions. This version is the last version that will get this error. It has nothing to do with the SDN.
  13. Fresh accounts are highly flagged automatically. Botting on high level/quest accounts lower ban rates but increase your risk. I've been using auto merchers and have not gotten banned although I agree they are at high risk for bans.
  14. Are you running multiple windows?
  15. Hello community, this release is a small update which fixes one of the patches with the previous build. Sorry for the quick update but it fixes a very prominent error. Download: http://osbot.org/get/index.php Check out the rest of the changes since 2.2.4: http://osbot.org/forum/topic/56439-osbot-224-many-bugs-mentioned-have-been-fixed/
  16. I tried to do a lot of the bugs reported today. Tomorrow I'm going to revamp the bank scrolling to support the mouse wheel and be more accurate.
  17. The hooks for the patched Inventory.isItemSelected() were just pushed! So restart your bots to get that specific patch if they're already running.
  18. Hello community, I'm happy to present you with OSBot 2.2.4 which has a multitude of patches in it. Here's some of the updates: Debug messages for blocked access to injected methods removedWhy? They were annoying and were causing our members to freak out when they really shouldn't. Stealth injection is now required, which means the bot may not work at all for Java 8 (however we're working on fixing that soon). A bug which caused an issue with Linux based VMs has been patched and should no longer cause a NullPointerException error. Inventory#isItemSelected() has been patched and works when mouse is over a tab! Inventory#deselectItem() has been patched and Magic#deselectSpell() has been added! Dropping of items in random events has been patched. Strange plant has been patched to wait until the plant reaches a certain height (not tested). Brand new trade API has been added and tested!within your scripts the field is called "trade". Check out the API docs for it: http://osbot.org/api/org/osbot/rs07/api/Trade.html Supports verification of second screen and caching of items upon accepting. Also supports getting the last player who requested to trade. Does not support clicking the request messages yet, but support for this will be added soon. World hopping has been patched. Pinball has been patched (not tested). Saving of OSBot settings has been patched (it will be deleted once more but should not happen again after this release!) Upcoming updates: Patched break handler Sleep deviation configurations Various bot profiling methods more.... Thanks for your patience! Here's the download: http://osbot.org/get/index.php Here's the docs: http://osbot.org/api/ (updated API coming in a few minutes). Thanks, Sincerely, Laz and the OSBot Team. EDIT: The API page has been updated. Check it out at http://osbot.org/api EDIT: Forgot to mentioned that noted items now have proper names!
  19. I hate it when ignorant, impatient, leechers like you that don't understand how programing even works and have never even studied RuneScape's game engine internally at all react when someone who knows what their talking about actually explains to them that everything is a ok. I've been reverse engineering RuneScape since 2008. I've created everything from fake-clients, private servers for almost every type of client revision, update servers, eoc, etc. If you don't have any authority or basis for your claims than don't post your ignorant comments anymore. Maybe you don't know how to bot correctly, but I've made thousands of magic tabs, caught thousands of chins, and botted many more scripts on OSBot and with confidence in it.
  20. I've stated that it works if you have it enabled. Enough said. Quit asking questions and go back to botting. The debug messages are just printing which methods are Jagex are trying to detect that would NORMALLY NOT BE THERE. So by blocking their access by throwing no method exceptions they won't know.
  21. I have no evidence that they have been using this method prior to today's update. I don't believe you got banned for what you thought. I'm sorry for you loss however and hopefully you can move on.
  22. Most likely a delayed ban sir. The stealth injection should be doing its job.
  23. No, a physical update was not pushed. Just restart the bot... it should load the latest hooks now.
×
×
  • Create New...