Jump to content

Laz

Suspended
  • Posts

    775
  • Joined

  • Last visited

  • Days Won

    33
  • Feedback

    100%

Everything posted by Laz

  1. Hello community, OldSchool RuneScape updated today and the latest hooks for OSBot were released just now. Simply restart your OSBot to load the latest ones. We're preparing some big updates to be released soon. Stay in tune. Sincerely, Laz and the OSBot Team.
  2. Hello OSBoticans, once again RuneScape has updated. The latest hooks for client #62 have been release just now. Simply restart your clients and you're good to go. Sincerely, The OSBot Team.
  3. Hello OSBoticans, the hooks for the latest RuneScape update which occurred this morning have been released. No need to re-download your clients. Simply restart them and they will be functional again. Sincerely, The OSBot Team.
  4. Laz

    OSBot 2.2.30

    Hello community, I present to you OSBot 2.2.30 which contains several bug-fixes resulting from the merge errors created from having many developers. This will not happen again and sorry that the update took so long. From now on we will be taking several more precautions with our source code management to prevent the creation of bugs. OSBot 2.2.30 contains all these changes not include in OSBot 2.2.29. OSBot 2.2.30 Alek's changes: -Overriden method toString() applied to Area -Added MoveMouseEvent(Bot bot, Point point) -Added ClickMouseEvent(Bot bot, Point point, boolean rightClick) -Added click(int x, int y, boolean rightClick) -Updated move(int x, int y) -Added isVisibleOnCanvas(int x, int y) -Updated GroundItem hover() to use point destinations Ground item interactions have not been changed -Added getPoint() to Ground Item -Added PointDestination class -Updated Account Settings GUI to include random event solvers -Updated RSAccount class with random solvers Thanks, Sincerely, Laz and the OSBot Team. Expect more maintainece builds after this and the new OSBot 2.3 platform is almost complete. MGI and I are working on a newer botting platform that will letting you bot on almost any legit way to launch the client (like in the browser or the desktop game-client, perhaps even OSBuddy?)
  5. Laz

    OSBot 2.2.29

    Hello community, the hooks on our server were updated just now. Unfortunately our auto-patcher failed. We will begin improving the autopatcher soon. Sincerely, The OSbot Team. PS. JavaDocs have not been updated, they will later today. PSS. OSBot 2.3 is coming out later this weekend. Happy Botting!
  6. We've already picked a new name, but it's secret. It's very nice though, I'm sure everyone will like it :p.
  7. Haha you're asking too many questions regarding thing we haven't even taken into account but I'm sure we'll have APIs that handle bot types.
  8. We already know how to control ban rates for both versions of the game. OSBot 2.3 (coming next week) will feature some of these new anti-detection technologies.
  9. Hello community, you may have already noticed, but if not, we have a new developer called @MGI. He has been hired because OSBot is planning on creating a fully functional RS3 bot to compete with other botting companies. He's a very talented man and is working on and investigating RS3 botting. Thanks to the extra muscle on board the company, OSBot will continue to maintain and update its OldSchool bot while the new RS3 bot continues its development. There is no exact ETA for when this bot will be released to the public. But you may expect a BETA release for it in the upcoming weeks. The RS3 bot will be based on top of a heavily altered version of the OSBot 2 engine which will still support all our current scripts. MGI may or may not be very active on the forums as he is very busy working on the new bot. Also at the moment, MGI plans to be around for a limited time and may leave after his work is finished. Nonetheless, please welcome him into the OSBot family. Stay tuned! Sincerely, The OSBot Team!
  10. I was asleep. Yesterday I hadn't slept in 48 hours because I was working on my next release (2.3.X) non stop. Unfortunately the timing of the updater breaking wasn't great.
  11. Hello community, Sorry for the inconvenience but the bot should be fully operational again and there is no released for a physical update. Simply reload your bots and they should work fine now. We spent the majority of the day patching the updater and everything is fixed. Please keep in mind that it's actually very rare for our updater to break and this should not happen again on the next update. Sincerely, Laz and the OSBot Team.
  12. OSBot 2.2.26 fixes all the bugs with this release. Sorry for the inconvenience, there was some troubles merging and we also added the Ancient Spell book thanks to @Xerion.
  13. Hello community. We haven't released some updates in a few days but I'm here to explain what's happening, what you can expect, and more. First of all, as the lead developer of OSBot, I've been focusing a lot more recently now on our next major update. Jagex has recently had much success in detecting bots and as a result, OSBot 2.3 plans to change that. We're currently developing some major restructuring of the internals which lets OSBot inject itself into RS. These changes will not break any scripts, but rather change the entire process of how botting works. We don't want to release too much information now, but the new technology is almost ready for deployment. Also to clarify, OSBot 2.3 will not contain webwalking. The webwalking project is currently on hold because it's no longer a high priority and will take up too much time for little reward. Instead what we're doing is changing the way scripts work so that webwalking won't even be needed anymore. Moreover, as a result @Alek is the only active developer maintaining OSBot 2.2. If he cannot get online tomorrow to work on a maintenance release for 2.2, then I will handle tomorrow's update. Regarding ETAs on Updates (subject to change): -Expect an update for 2.2 arround tomorrow -OSBot 2.3 is being developed, the new technologies should be ready within 1-2 weeks. -OSBot 2.4 will be coming within 1 month of OSBot 2.3 being released. Note that the ETAs are being estimated as achievable goals for me. Although their subject to change, they're still our current goals. To sum it up: -OSBot 2.3 will feature a complete internal redesign (without breaking scripts) and will focus on anti-detection technologies. -OSBot 2.4 will feature new APIs that will make scripts more powerful than ever. Additionally, we will be shipping a script loader that runs other languages supported by the JVM. Thanks, Sincerely, Laz and the OSBot Team.
  14. I have more time now because I'm no longer a student.
  15. Hello community, This new update features some changes that we've written so that RS updates are handled as fast as possible. Our servers will now be running our client updater 24/7 now, updating the hooks as soon as an update is detected. We've also added a callback to the bot which tracks login server responses. If the bot detects the login server message "RuneScape has updated," then the bot gets restarted and reinjected with the latest hooks from the server. If the automatic update takes longer than 5 minutes or experiences any issues, the bot is simply closed for your safety. This feature should work with practically every script supported by our API and scripters should not need to make any changes to their code. The bot handles the automatic restarts perfectly now. Also, we've been upgrading our backend infrastructure to remove some server overhead and to optimize the website. You may have noticed the front-page (http://osbot.org/) now displays the exact version number of the bot. This gets updated automatically now and the download links has moved to (http://osbot.org/mvc/get). These changes will allow for faster distribution of the bot, less bandwidth usage, and overall better design. Additionally, our SDN script processors will now always be using the LATEST OSBot build jar for compiling scripts, so there will be no more awkward delays in API changes for scripters. Following this update you should expect OSBot to handle future RS updates automatically, requiring no user input. API Changes: -Added canCast(Spell spell) to Magic API -Added canCast(Spell spell, Condition condition) to Magic API -Added canCast(Spell spell, boolean checkConditions) to Magic API -Added spellCondition(Spell spell) to Magic API //Used to check behavior of boolean checkConditions -Identified several performance problems in EventExecutor -Added bank caching --Added bank.cache(); --Added bank.cacheContains(String name); --Added bank.cacheContainsAny(String... names); --Added bank.cacheContainsAll(String... names); --Added bank.getCachedItemAmount(String name); -Patched WithdrawAsMode and RearrangeMode -Added DepositBank method close() -Rewrote Bank method close() -Added Freaky debugger Download: http://osbot.org/mvc/get Sincerely, Laz and the OSBot Team. P.S. The JavaDocs have been regenerated and can be seen here : http://osbot.org/api EDIT: OSBot 2.2.24 was released as a hotfix. It contains fixed bank scrolling and a patched memory leak.
  16. Hello community, this release features a revert to the Modeled.getModel() method which makes it never return null now. We had patched it in OSBot 2.2.21 to return null if the model was not being drawn but because of this, it broke many scripts and we don't want to wait for the developers to fix them. As such further improvements have been added including using cubic areas for entity interactions to fix a bug that occurs when the bot tried to interact with a stacked entity. Furthermore, I've read about the concerns of the world-hopper speed and have decided to add an injection which lets the bot instantly switch the current world after logging out. Thanks, Sincerely, Laz and the OSBot Team. [INFO][Bot #1][09/02 03:31:47 PM]: Started script : World Hop Test [INFO][Bot #1][09/02 03:31:47 PM]: Hopping to world : 303 [DEBUG][Bot #1][09/02 03:31:48 PM]: Breaking in 1 hours and 3 minutes for a total of 24 minutes [INFO][Bot #1][09/02 03:31:50 PM]: Started random solver : World Hopper [INFO][Bot #1][09/02 03:31:50 PM]: Random solver exited : World Hopper [INFO][Bot #1][09/02 03:31:52 PM]: Started random solver : Auto Login [INFO][Bot #1][09/02 03:31:57 PM]: Random solver exited : Auto Login [INFO][Bot #1][09/02 03:31:59 PM]: Terminating script World Hop Test...If you look at the above timestamps, the entire world-hop plus auto-login completed within 7 seconds!
  17. Hello fellow OSBotters, We've been noticing some recurring downtime associated with our website and our hosting provider has just recently clarified the issue. It seems that they've been actually backing up all network drives nightly at specifically between 11AM-1AM Eastern US/Canada (GMT - 4:00). As a result our servers IO usage was quickly being used up and thus long wait times for loading the forums. We're correcting the issue by moving to some better dedicated servers instead of using cloud services. However this next upgrade will definitely be suited for faster performance. The transition to the new servers will be seamless for bots and we anticipate some downtime for forums. Currently, the transition is planned to occur within the next 3 days. Thus, you may experience this slowdown again on the forums during these time periods, but only for the next 3 days at most! Our servers are handling fine now and you should be fine to bot! Thanks, Sincerely The OSBot Team. BTW: This is all credits to @Zach. He solved this entire situation for me and should be congratulated for his great professionalism!
  18. I'm not saying that non-official devs are bad, its just that they may not entirely comprehend how the entire OSBot engine works together to perform the final output. I did make that comment however because our previous mouse algorithm was optimized very similar to the way this build is optimized now and sorry to say but I prefer creating code than fixing other people's code. Regardless the mouse algorithm was a great improvement nontheless but it was definitely in need of optimizations.
  19. Well the only way to know for sure is to have people test and report the bugs. Honestly its way to rare for the developers to find it themselves. On top of that, this build is definitely better than the previous ones so rest assured and bot safely.
  20. A bug in our bot that caused it to detect events that weren't actually occurring. It was a rare bug anyways.
  21. Hello community, This release features several internal optimizations to our mouse algorithm. Since it was re-written by a non-developer it was not very optimized and thus caused unneeded CPU to be used up. This update makes sure that we're not recalculating unneeded internal values. Further changes: We've researched a bit and added some patches which should prevent invisible random events from being activated! Strange plant bug fix (detects if it's not your plant correctly now instead of spam-clicking the plant) Mouse destination point algorithm rewritten Various other bugfixes Sincerely, The OSBot Team. EDIT: Some scripts may have been broken due to our new model system. The will most likely result in NullPointerExceptions in some scripts. The developers should be fixing their scripts to work properly again. Here's a download link to OSBot 2.2.20 if your scripts do not work (please be aware of the the above bugs that were fixed): OSBot 2.2.20
  22. Yeah but I dont have any classes this semester now and have a lot more free time... situations change over time.
  23. Make sure your using OSBot 2.2.20 as there were bugs in the isFull() methods in prior releases too.
  24. Sorry guys I had to re push it to OSBot 2.2.20 because we forgot to merge our changes. (I'm still getting used to having Alek as a developer )
×
×
  • Create New...