Molly

Not sure, you'd need to check out the market and look for someone selling vouchers. You have a trial.

I thought so too, but the system I built on pcpartpicker equivalent to the one he posted is estimated to use 253W.

You can, it's easy. All kinds of guides on the internet to learn how. I'd recommend at least doing some research and seeing if you think you can do it, building your own systems can save you a ton of money.

Build nearly identical to yours, minus an OS because Windows can be pirated very easily, for $635. http://pcpartpicker.com/p/jhchWZ I wouldn't pay 714 for that.

Just confirmed it to be working, could you fill out a bug report as I have outlined in my OP? Or at least copy and paste the log so I can get a better idea of what's happening.

Saw your post in the help section, happy to see they got it cleared up for you. I was about to make a topic myself.

Thanks guys, had another user report this issue a couple of days ago and saw Riathen post on my topic today reporting the same thing. Was about to make a thread/contact a mod, happy it's cleared up!

You guys all have trials now.

Trials given. Are you sure you're using Antidote++? http://2007.runescape.wikia.com/wiki/Antidote%2B%2B I just started it up and it ran fine.

I just ran it for 5 hours fine, please fill out a bug report as I have outlined in my OP so I can try to fix your issue.

You still have one from the other day man.

Authed you a trial.

Manually authed you a trial. I'm not sure what effect that would have, yes, it's very easy to add, but what is the benefit?

Everything looks correct here on my end, perhaps something isn't right on OSBot's end, unfortunately I don't handle transactions so I can't fix the issue. However, if you post here in the support section, and contact a mod I'm sure they will quickly fix the problem! http://osbot.org/forum/forum/154-general-help/

Thanks for the proggies man!

You guys should both have trials now.

You guys all have trials now.

Isn't this handled by the client? Or not in mirror?

I'm going to manually auth you another 3 day trial, mods may have removed it due to your post in the support section about removal of your access to the script. I noticed they stated it was due to a payment issue with your Paypal. I'm giving you another trial in good faith that you can get the payment issue sorted, if you are unable to get it sorted out you can purchase a voucher here in the market section for RSGP to use to purchase it. http://osbot.org/forum/forum/227-vouchers/ Yep, just like the OP. One should be automatically given to you within the next 15m since you liked the OP, if it's not I'll manually auth you one.

It takes a little bit sometimes, it should, in theory, take no longer than 15 minutes, but I've noticed that to not always be the case.

Make a topic in the support section of the forums and contact a mod, unfortunately I do not handle the money side of things and if there was a problem on that end OSBot may have removed your access to the script. I'm going to give you a 3 day session free, if your issue has not been resolved in that time I'll extend it for you, just let me know! Looks like the trial was given automatically, it takes a bit sometimes.

Thanks for the replies guys! Pro, I believe I answered your questions via the PM's you sent me. That annoying "COM1" status will be resolved soon hopefully, it's not a huge priority right now solely because it doesn't effect functionality of the script at all. Also: Just pushed an update to reduce ban rates! The update implements the first stages of anti-profiling methods I am adding to all my scripts. From now on the script will operate in "cycles" where a play type is randomly chosen, this play type will determine how fast the bot does things by adjusting sleep timers, this will cycle based upon a random interval chosen each time a new play type is chosen. Example: For 24 minutes the script will execute actions a tad slower than normal. After those 24 minutes a new type and time is chosen. Now for 17 minutes the script will execute actions a bit faster. The goal here is to prevent the user being banned based on patterns of sleep timers. Instead of say, after you teleport the script sleeps for 200-400 ms and it does this ALWAYS, the script, depending on the play type, might sleep for 400-600 ms after teleporting for 17 minutes. Then for the next 27 minutes the bot will sleep for 625-800 ms after teleporting etc. This makes it much harder for the script to be detected based on time related to actions. Over the course of the next several weeks I will be implementing more and more anti-profiling measures. Using these features is of course optional, and entirely up to the user, they can be disabled via the gui. I however strongly encourage you not to disable them! You may notice the script not being as efficient as it is with anti-profiling disabled, however your account will be safer.

Just pushed an update to reduce ban rates! The update implements the first stages of anti-profiling methods I am adding to all my scripts. From now on the script will operate in "cycles" where a play type is randomly chosen, this play type will determine how fast the bot does things by adjusting sleep timers, this will cycle based upon a random interval chosen each time a new play type is chosen. Example: For 24 minutes the script will execute actions a tad slower than normal. After those 24 minutes a new type and time is chosen. Now for 17 minutes the script will execute actions a bit faster. The goal here is to prevent the user being banned based on patterns of sleep timers. Instead of say, after you teleport the script sleeps for 200-400 ms and it does this ALWAYS, the script, depending on the play type, might sleep for 400-600 ms after teleporting for 17 minutes. Then for the next 27 minutes the bot will sleep for 625-800 ms after teleporting etc. This makes it much harder for the script to be detected based on time related to actions. Over the course of the next several weeks I will be implementing more and more anti-profiling measures. Using these features is of course optional, and entirely up to the user, they can be disabled via the gui. I however strongly encourage you not to disable them! You may notice the script not being as efficient as it is with anti-profiling disabled, however your account will be safer.

Just pushed an update to reduce ban rates! The update implements the first stages of anti-profiling methods I am adding to all my scripts. From now on the script will operate in "cycles" where a play type is randomly chosen, this play type will determine how fast the bot does things by adjusting sleep timers, this will cycle based upon a random interval chosen each time a new play type is chosen. Example: For 24 minutes the script will execute actions a tad slower than normal. After those 24 minutes a new type and time is chosen. Now for 17 minutes the script will execute actions a bit faster. The goal here is to prevent the user being banned based on patterns of sleep timers. Instead of say, after you teleport the script sleeps for 200-400 ms and it does this ALWAYS, the script, depending on the play type, might sleep for 400-600 ms after teleporting for 17 minutes. Then for the next 27 minutes the bot will sleep for 625-800 ms after teleporting etc. This makes it much harder for the script to be detected based on time related to actions. Over the course of the next several weeks I will be implementing more and more anti-profiling measures. Using these features is of course optional, and entirely up to the user, they can be disabled via the gui. I however strongly encourage you not to disable them! You may notice the script not being as efficient as it is with anti-profiling disabled, however your account will be safer.

Just pushed an update to reduce ban rates! The update implements the first stages of anti-profiling methods I am adding to all my scripts. From now on the script will operate in "cycles" where a play type is randomly chosen, this play type will determine how fast the bot does things by adjusting sleep timers, this will cycle based upon a random interval chosen each time a new play type is chosen. Example: For 24 minutes the script will execute actions a tad slower than normal. After those 24 minutes a new type and time is chosen. Now for 17 minutes the script will execute actions a bit faster. The goal here is to prevent the user being banned based on patterns of sleep timers. Instead of say, after you teleport the script sleeps for 200-400 ms and it does this ALWAYS, the script, depending on the play type, might sleep for 400-600 ms after teleporting for 17 minutes. Then for the next 27 minutes the bot will sleep for 625-800 ms after teleporting etc. This makes it much harder for the script to be detected based on time related to actions. Over the course of the next several weeks I will be implementing more and more anti-profiling measures. Using these features is of course optional, and entirely up to the user, they can be disabled via the gui. I however strongly encourage you not to disable them! You may notice the script not being as efficient as it is with anti-profiling disabled, however your account will be safer.