Alek

I'd prefer if this was in an actual bug report because I track those; however a few questions right off the top: -Is it only when you are running a script? -Does it happen before you "Add new bot"? -If it only happens during script execution, are you running mirror mode? -Have you had similar issues before? -Are you getting any errors in the logger? -What operating system are you using?

The new update did nothing to increase or decrease CPU usage.

This update has nothing to do with mirror mode or detection; you can find a list of changes under "changelog" on the original post.

No they aren't. Restart the client or post any error messages in the logger. ids change on RS game updates

This will move as a stable update shortly.

Why was this posted in Tutorials, why is your directory not correct, how are you trying to start OSBot, what operating system are you using?

Sounds like you aren't logged in or your proxy settings are incorrect.

Yesterday was a pretty large update, thank you to everyone who made bug reports. This update aims to resolve any remaining issues stemming from 2.3.102, namely VIP. If all goes well with this version, it will move as a stable build. Changelog: -Patched 2.3.102 VIP issue -More code cleanup -Updated Worlds API, avoids skilling worlds -Updated world load list to avoid skilling worlds 2.3.104 -Fixed an issue related to the local directory -Updated error messages Thank you for using OSBot, enjoy the rest of your Sunday.

I'll test this issue out, thank you for reporting. It's a bug

Not optional, single global variables.

OSBot has been through various face lifts since my time here and I think this change is something which will help new users embark on their botting journeys. Most notably the login system was moved to the booter and the logout functionality has been removed (you will stay logged in until you close the client). Another noticeable change is that individual account settings have been removed in favor for global settings that affect all your accounts. This means that when you tick "Dismiss all randoms", any account which you are logged into will dismiss randoms; break settings as well. Although many of you won't notice the change (unless I screwed up something, but hey it's a dev build), the booter interface was the first interface to be stripped from the NetBeans GUI-maker. Auto-generated code bottlenecks a lot of development and design choices as well as creating a host of other issues. Most of our interface related issues/errors stem from NetBeans and hopefully over time I'll be able to rewrite all of the interfaces. The settings interface is most likely next up on the chopping block with a few new functional benefits in the work. Changelog: -Booter stripped from NetBeans, re-written by hand -Removed Login system from client interface -Added login system to booter interface -Proxy saved to separate proxy file --Preliminary separation needed for proxy manager -Added new booter save file -Removed settings from RSAccount -Settings now placed as global variables that affect all accounts --Added new settings file -Re-wrote account manager -Added new account file -The OSBot Staff

Try re-downloading 2.3.99.

There is an 8 hour logout timer...

If your account is suspected to be stolen, if your computer is blocked, or if you were banned, the RSL will print that statement when you are trying to log in during the Auto-Login event. http://osbot.org/api/org/osbot/rs07/constants/ResponseCode.html It's part of a smaller security check we have here at OSBot, I would suggest not botting on that account especially if you were moved to a bot world.

You could try area.getRandomPosition()

Try downloading 2.3.99.

This is not a client suggestion, moving over to Forum Feedback/Suggestions.

It was in .96: http://osbot.org/forum/topic/79514-osbot-2396-very-experimental/ Only a handful of SDN scripts were affected, in which case I contacted the script writer(s). Were you affected by this change?

.99 release tonight, I kept getting low quality reports and finally got some good info on the random which was not working for a large group of users. If you guys have anything else for me (small stuff), find me in chat tonight and pm me.

Would you like me to move this to the mirror mode bug reports forum?

Have you tried testing this in stealth injection mode, because I can't seem to replicate not scrolling. By the way thanks for posting videos.

This is not an OSBot issue, moving to general help.

I do not know what you are suggesting, please give a bit more detail.

It's deprecated, definitely do not use it. It will eventually be the new walking class, replacing LocalWalker and containing but the WalkingEvent and WebWalkEvent based methods. The changelog typically contains everything, not matter how big or small. If scripters have questions about the Walking class, they will know the purpose behind it.

Version 2.3.94 Release -Additional mirror mode checks and verification --Patches a majority of users who were unable to use mirror mode -Updated random event activation -Updated preset points in IE