Apaec

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

Please try with the latest build, hopefully all issues should be resolved. Apa

Hi, Apologies for the delay in reply, i'm glad you got this issue sorted in the end. Perhaps I should add a check for this in the script to prevent this issue happening to future users. Thanks for letting me know Apa Hey, I'm not sure what is causing this. Please could you try with the latest client build? Here's a link: https://osbot.org/forum/topic/156423-stable-osbot-2558/ (You should be able to use the download button at the top of the forum) Apa Edit: Please let me know if this resolves your issue.

Hi All, Apologies for the late reply. For some reason, I was unfollowed from the thread and did not get a notification when you all posted. Hi Zygizz, Unfortunately this script is only a cooker, so does not support ingredient combining of any sort. The script will turn your uncooked pizzas into cooked ones, but adding toppings and making the dough are all out of scope of the script. Apa Sure, please let me know if you're still interested in a trial considering the delay to my reply. You can get in touch by quoting my reply here, or by sending me a PM. Apa Hi, Unfortunately the script does not support wine making, nor any other kind of niche cooking technique (it is worth noting that this script is an AIO Cooker, not AIO Cooking - the difference is subtle and perhaps I could make this more clear). A comprehensive list of all supported foods and locations is available on the main thread - i'd always recommend checking these prior to purchasing a script. As for a refund, this may be possible, but is out of my control (the store is maintained by the OSBot staff and not the scripters, we have no access to payment information). I'd suggest filing a request in the support subforum. Best Apa

Hey, Did you get it working in the end? Looking at the console logs you've provided, it looks the the OSBot webwalker is having difficulties. The WebWalker is used to walk the script to the location - if you try starting the script when you are already at the location, it might resolve this issue. I've not been able to re-create this, but I will continue to try. As for deposit all, the script will use this button when it can, but it is not aware of bank fillers or other similar setups. The script will use deposit all if the items in your inventory are all homogeneous and require banking. Please let me know if you run into any other issues Apa

Sure thing, trial activated Apa

Sure - trial started Apa

Update: Version 3.12 Added failsafe for when script tries (and fails) to deposit items into a full bank Added failsafe for when script tries (and fails) to deposit unbankable item Best Apa

Sure - trial started Apa

There seems to be nothing telling from the console log, so unsure what might be causing this issue. Perhaps try hiding the paint as Gunman suggested, that may resolve things? As for the reason I can't do much about this, it is because both mirror and stealth injection run the same API, so are supposed to execute the same also. Any inconsistency with that is in the hands of the client rather than the script, thus out of my control (I cannot modify the client code, that is the job of the developers). Cutting the script down wouldn't help, as issues may arise elsewhere, so ultimately the solution would be for the mirror client to be fully patched up to work the same as stealth injection, which is something the developers are working on continuously. I understand it is a frustrating situation, but this is why I recommend users to stick with Stealth Injection in advance before considering the purchase of the script. As for bans, there's no way to get real proof that either are 'safe' - both carry chances of bans and so keeping a low profile at the cost of slow gains is always the best bet. Cheers Apa Sure - trial started

Oh no! That's really unlucky sorry to hear about that. To prevent this happening to you again in the future, it might be worth giving this thread a quick read if you haven't already: https://osbot.org/forum/topic/124429-preventing-rs-botting-bans-v3/ Hopefully that is of some help! Hmm, an interesting idea, but might cause a lot of confusion as you highlighted. The error correction system is probably the best way forward, but it's not quite ready. As soon as it is I will make an announcement in the thread though! Apa