Alek

Please tell me who you were talking to in this conversation:

You did not answer both questions and you did not answer my question with a yes/no answer. Please read my questions carefully before I flip a coin. "The exact script you bought is unique to you", then you go on to explain that if someone else ran it, it would "not affect the outcome" and "not affect the situation". It looks like the only part which is "unique to you" is the username check, and the core of the script is the same. Final chance to answer each of my questions correctly. 1. Did you try selling the script to anyone else? (Only "Yes", "No", or "I do not understand the question") 2. Was the script more unique than just the username check? (Only "Yes", "No", or "I do not understand the question") 3. If the script was only unique because of the username check, did Montana understand that is what made the script unique? (1-2 sentence explanation)

Did you tell both Montana and CMDrake that their scripts would be completely unique? Did you try selling the script to anyone else? (Please nobody besides House respond) Edit: Please a simple yes or no for each question.

Then explain this: if ((!getClient().getUsername().equals("House")) && (!getClient().getUsername().equals("CMDrake"))) { log("This is not your script! >:("); stop(); } If you tell the truth and don't lie, I usually try and defend the script writer.

How did you get the virus? Through the script?

Might as well set it to -mem 1 and let the magic memory system run OSBot on a single megabyte.

Your jvm was probably being constrained to 512mb, forcing gc. Once again I can't wave my magic wand and increase memory usage.

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.