Apaec

Glad to hear Make sure you take extra care though - botting is certainly a lot more risky than it was back then... Apa

Very bizarre - the script code hasn't changed in that time so not sure what could have gone wrong. I'm glad it seems to be resolved for now though Apa

Very strange... I've so far not been able to reproduce this so I have no idea what might be causing it. Does this happen in both Stealth injection & Mirror mode?

Just pushed an update to this script to hopefully fix the UI sizing issues. As this is a small patch, the version number hasn't changed. Apa

Certinaly, trial activated !

Sure - trial started

Hey, Another user mentioned this too - when I did a test, everything worked perfectly for me. Please could you let me know if there is anything written in the console logger when you try and start the script? You can open the console logger via the OSBot settings menu. Apa

Hey, That's odd - when a trial is started, it should just be on the scripts list. Nonetheless, thank you for your custom - if you run into any issues, please let me know! Apa

Certainly, i've just started a 24h trial on your account. Enjoy! Apa

Unfortunately not; Karambwans are only available in the premium version That's odd, looks like the JVM is running out of memory for some reason. Are you able to run other scripts? Perhaps this was caused by the recent change to the OSBot 'dracula' theme. I'll take a look. Apa

Sure - trial started Apa Hey, When the screen goes red, this means the client is in control (the script code is not running). You'll notice that it also does this when you are being logged in, as scripts are not allowed access to your RS account data. It sounds like it might be an isolated incident, but i'll pass your report on to the OSBot developers nonetheless. If you find this happening regularly, i'd recommend disabling random dismissal (this can be done via the OSBot settings menu). Randoms will disappear after a short duration. Apa

Of course, trial started Apa

I've figured out the cause of this issue. On Saturday, when I updated the script to remove deprecations, I also updated the randomisation function. In doing this, I introduced an unintentional bug whereby occasionally the script would pause for long durations while generating new random numbers. This is fixed in the update I have just rolled out, and the script behaviour should return to its previous stable state. I'd like to apologise for this - due to the random nature of this bug, it was not flagged in the testing I did on Saturday. I will be more careful when making changes such as this in the future. ----------------- Update: Version 3.53 Fixed random number generation As usual, please allow up to 24 hours for the developers to verify the changes and release them live. -Apa

Sure - trial started Hey, Unfortunately I don't handle refund requests, as the store is maintained by OSBot, but i'll be further investigating the issue you have brought to my attention tonight. I am fairly convinced it is an issue with the latest client build, so I will be gathering evidence to collate a bug report this evening. There's not much more I can do as the issue seems to be with the client banking code, but if it turns out to be otherwise, I will upload a fix as soon as possible. Apa

I ran tests on Saturday following the script update I pushed out, which is why I was surprised issues have surfaced. Nonetheless, as the issue has now been confirmed, I will run some further tests tonight and try and determine the cause of the issue.

Sand crabs are currently much better exp/h, so i've gone ahead and enabled a Sand crabs trial on your account. If you'd also like a rock crabs trial, i'm more than happy to arrange that - just let me know -Apa

Hi both, sorry to hear you are having problems. Please could you open the console logger and let me know what is written to the console when you try and start the script? This will help me determine the cause of the problem. Apa

Hi, I replied to your PM, but I see now that you've managed to get the script up and running. Please could you make sure you have: Auto-retaliate enabled NPC attack options set to their default value If both of these are already in place, and you're still having issues, please let me know. Apa

Hmm, ok. Thanks for letting me know. I'll investigate this ASAP - probably tomorrow evening as i've got a free slot then. Hopefully i'll be able to recreate the issue. Apa Edit: I just had a quick look and it seems the OSBot client is having a few issues with banking at the moment; from what I can see the developers are already aware of this, so will hopefully be rolling out a fix soon.

Sure - trial started Apa

I'm unsure why this is, I am currently running the script without problem. If this is happening to another script also, that suggests perhaps there is an issue with the current client build? Please could you let me know two things: Are you using mirror mode, or stealth injection? What client version are you using? Apa

Sure - trial started Apa

Update: Version 3.52 Removed usage of deprecated API methods Updated script randomisation Please allow the development team 24h to verify the changes and push them live. Apa

Hey, Oops! You're completely right. I am fixing this right away for you. Apologies for the inconvenience caused - the script should be back up and running soon. In the mean time, i've given you access to my Sand Crabs script for 24h so that you can continue botting while you wait. -Apa

Nope - it will stop when you run out of items & runes in your inventory. Hope that helps Apa