Alek

It's a problem with your script then, I can't just wave my magic memory wand and add more memory usage. If it's an SDN script pm me and I may have time to look at it.

Fixed some memory stuff, everyone should be working again. Make sure you have at least 1GB of RAM available (this does not mean OSBot will use 1GB). The mem flag overrides the 1GB requirement. Also potentially decreased some memory usage with the web walker, MGI pointed out some efficiency concern he had for a change I made a while back.

I should hire @Lagoni

If anyone gives you their questions let me know so I can remove them swiftly from the community. Questions are based on the OSBot events and some basic Java. WebWalkEvent, InteractionEvent, MouseDestination, mouse events, are all things you should look up and be familiar with.

@Bamboozled and @Abuse, looks like I did add no render in early January, my mistake!

Oh please. HWID is such a general term I have no idea why people even talk about it. It could mean anything from volume information that can be changed easily or manufacturer serial numbers which can't. In which case they can determine which hardware they want to track. Oops looks like you changed your sound card, better ban you.

@Alexrs RAM usage only gets increased when the application needs more RAM. All I did was allow the application to get the heap space it needs.

I removed two votes. If you are voting for the bot farming option, I specifically mean bot farming here at OSBot (which requires VIP+)

Be honest when answering. If I see gray names saying they are running 3+ bots you'll be on the naughty list. Try and take it seriously because I'll be using this input for my next goals list. Thanks!

I never got around to adding it in the first place, I might add it at some point soon.

@DrDu The only thing that changed was ensuring that the jvm has access to a larger heap space. All this means is that OSBot will use more RAM when needed instead of crashing (throwing out of memory exceptions). If this comparison is new vs old, the only conclusion I can draw from this is that on the old build your client was crashing.

Reflection has nothing to do with mirror mode, injection, or anything related to bot detection whatsoever. Also "norender" doesn't exist.

Patched an issue with out of memory exceptions on some machines. Also touched various other things which shouldn't matter too much. Download: https://osbot.org/devbuilds/osbot 2.4.117.jar

You're using random positions that could be totally messing everything up.

The clicakable area: Updated 19 Dec 2015:

There isn't, I'm not going to add it to CLI.

You were spamming. If you make me dig up the chat logs I'm going to be pretty upset.

Still haven't touched it, I don't have a local server set up for testing. The reason why I was able to do it last time is because Zach was there to accept my changes. Maybe over the summer.

Not a scripting question, belongs in the witchcraft section.

Areas can be polygons, not rectangles. Not sure if you specifically meant rectangle areas.

If you are on Windows try downloading the .NET redistributables, I think there is a sticky thread about it in the mirror mode section.

It could literally be anything.

No idea who he was, he just kept private messaging me about contacting the "owner of osbot" to buy his friend's revolutionary anti-ban technology.

Thanks for reporting.