Molly

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.

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.

mi boting clyent n0 wurk wut d0!?

The update is pushed, but the live version will not be updated till 10AM EST sadly. The SDN manager does updates every day at 10AM and 10PM EST.

I just did a major rewrite of this script last weekend, I tested much of it but did not get to test as extensively as I would have liked to. This is the reason for any bugs, I just got home from work and will be trying to replicate and fix those issues. Edit: Yes, mirror is better, but requires VIP. Edit x2: I made sure deathwalking is working, seemed to work okay for me but sometimes would not equip glory and teleport to edge if possible, fixed that. Stam pot issue was fixed last night and just confirmed fix working. I found another bug, due to the fact RSBuddy's GE price pages are down right now the bot wasn't starting, this has also been fixed. Pushing right now, version will be 8.2 when live.

Pushed a fix for that bug, price tracking will not work for the time being. RSBuddy's GE database is having issues and that is where the prices are grabbed from.

Just like the OP and one should be given within 15 minutes. Bans happen when botting, it's a known risk. I've run this script for weeks without bans, I've had other accounts banned within 1 week, it happens. As far as "half the script not working", if that is true, perhaps you should fully read instructions on how to place a bug report so the "half" of the script can be fixed. Here is the format for bug reporting as I have clearly outlined in my OP: Bug report form, this is a MUST for problems to be resolved quickly: Description of bug(where, what, when, why): Status on paint: Log: Your settings: Mirror mode: Y/N

I actually plan on implementing it this weekend.

OSBot Scripter's Aid Checking into it, thanks. let me know if it happens again. This could have been caused by an issue in the client with web walking to areas, make sure to update to the newest revision of the client before you run the script again.

Please post logs when you experience bugs, I have a detailed bug report form in my OP outlining what information a bug report should include. I found the stam pot issue, it will be fixed when SDN updates are next pushed. Does the script use stam pots if they are available? As for logging out after running bank to bank after death that may be because it no longer has some required items in bank, perhaps air staff. Please post a copy of the logger if it happens again.