Alek

I downloaded it from the forums, it's giving me 2.3.113. Anyone else having issues?

Use entity hover debug

Nothing in here requires an in-depth explanation. I'd like to thank @Botre for reporting a serious bug that uncovered a lot of others hidden bugs. Also throw @Zach a few high fives for tracking down and killing off some pesky bugs. Yes, we plan on removing the Mouse Zoom random event solver at some point soon. Changelog: -Removed Settings isTabOpen(SettingsTab) -Rewrote Settings open(SettingsTab) --Checks internally if it's already opened -Removed Settings openHouseOptions() -Removed Settings closeHouseOptions() -Rewrote and Deprecated Settings setHouseBuildingMode(boolean) -Rewrote and Deprecated Settings isHouseBuildingModeOn() -Deprecated Settings areRoofsEnabled() and immediately returns false --Planning on rewriting -Deprecated Settings toggleRoofs() and immediately returns false --Planning on rewriting -Added Settings resetMouseZoom() -Updated MouseZoom random to check SettingsTab -Removed unused interfaces which were being initialized -Patched ItemContainer and RS2Widget for correct item ids -Patched Widget Debugger issues returning incorrect values -Updated Store API The OSBot Staff

Because people don't know how to reset mouse zoom, so it ruins it for everyone else. There is an update in the works to remove it and replace it with a real fix.

Apparently VAC bans are never reversed, no idea what triggered it but here is the proof: Today: I sent an email off to Valve, not sure if that made any difference. I never cheated in CS:GO but explained to them how I reversed other games such as Rust and that programs like CE and olly were on my computer.

Moved to stable builds.

Home arrest? ISIS? Internet? Video game? Call your news station.

Use Java 8

Are you compiling against the most recent OSBot version? Are you sure you're using all packages correctly?

Did you not read what I posted? "Stop script on logout" stops the script after botting for x amount of time.

As promised from the 2.3.111 development build, the OSBot Break Manager was re-written and is currently working with all the features found from the new settings interface. Here is some general info regarding the break manager: -Randomize bot/break time randomizes the time by 10% --Ex: 100 min bot time = 90-110 min bot time -If you are using a default account, you will be logged out after the bot time is reached --Should be obvious, you can't log back in without giving the client your user/pass Changelog: -Rewrote Break Manager -Patched Default account bug while logged-out -The OSBot Staff

"Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum." "Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?" "Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum." "Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?" Version number?

Thought about spinners but i didn't want to miss an opportunity to use regex.

Over the last couple of months I've been working towards hand writing all the OSBot interfaces from scratch, a time consuming process but something I believe is important when considering new operating systems (namely Windows 8 and 10) and newer versions of Java. Each interface is not only re-written stripping it from the old GUI maker, but a good chunk of features are usually packed along with it. When considering user feedback, a large concern was the language used to describe break features. In order to meet the needs of our community, the break settings have been re-worked and hopefully make it easier for new botters to understand them. Please note the new feature "Stop script on logout", stopping your script after you botted for a defined (or slightly randomized) period of time. The randomization will most likely be a percentage between 10-15% (if selected) for all you anti-ban junkies out there. The F2P/P2P preference is for starting a new bot tab only; this feature is immediately available to all development build users. In this build however, the breaks have been disabled while I spend some time re-writing the actual break manager. This service will most likely restore for 2.3.112 and that version has a good chance of being placed on the stable build track. Changelog: -Updated GrandExchange setOfferPrice() -Updated GrandExchange setOfferAmount() -Updated GrandExchange confirm() -Added F2P/P2P world preference -Re-wrote Settings interface --Added number checks to bot/break fields --Removed model debugs from debug tab, please use entity hover debug -Various patches and fixes Happy Botting -The OSBot Staff

You tried inputting a fraction of a minute in your break settings... Delete your OSBot local folder and start from scratch to be sure.

Copy and paste the error here.

110?

Have you tried using a different script?

Try downloading 2.3.109. For some reason a large group of users were having issues while others experienced no problems.

Version 2.3.109 was released, hopefully this solves a big handful of users who were experiencing issues.

Anything in the logger?

This is just a small update to start off the weekend. Please note that the jar updater will not work on upgrading 106 -> 107, we're still dealing with some DDoS mitigation issues. Changelog: -Added MouseZoom random event -One-time setup randoms are removed from the cycle after completion -Added prioritization of random events I finally have some time to work on OSBot (not that I haven't) since I'm on leave, so I'll be patching up all the bugs that have been reported this weekend/next week. -The OSBot Staff

Moving to mirror mode forum

SDN Script or Local Script?