Apaec

Not sure... Perhaps you have to give it a class first? try that! If not, try deleting and creating a new project.

Yea, it's frustrating, but nothing I can do about that unfortunately. They're working on it! Heyo, sure, i've given you a 24h trial. ~apa

Probably the tile visibility issue which is floating around due to raids. If you open up the console, there may be an error - if there is, please let me know what this is so that I can act on it, or confirm that it is the tile visibility issue which the devs are working on fixing ! (client side). Cheers apa

I don't think so - It should be fixed in 2.4.108 (assuming that's the next version number). I don't think it's an easy fix though. The devs are aware ( http://osbot.org/forum/topic/113379-bot-randomly-bugged/ ), and are looking into it, however I cannot provide an ETA as I don't know any more than you! apa

Lmao this one's a classic

Certainly, i've given you a 48h trial as the script, like all others, is broken atm due to raids. If the client isn't fixed within the next 48 hours, i'll extend it further cheers apa

Appears to be the same tile visibility error as before - they haven't updated the client yet. Currently the latest build is 2.4.07 - hopefully they will update it soon but as for now there's really nothing I can do! apa

Sure thing I've given you 24h to try the script, enjoy!: ) apa

haven't been able to finish a raid yet!

Hey, don't worry. I believe this issue is caused by the recent raids update, so just hang tight and the devs should get around to fixing soon! Cheers apa

It is randomised, but once the script is back online I can look into adding more camera and mouse movements too! Heya, all scripts have the same issue due to the recent raids update, just hang tight for the devs to update the bot!

Probably due to the raids update today, just hang tight for the devs to fix!

Yep, will do my best to have this added for you for the next release, after raids ~apa

That depends on what raids will be like, whether it will be worth botting, how hard/long it would take to write a script for etc

Haha, sure! I've given you a 24h trial ~apaa

looking good

Hmm. Potentially count add this for forging. I will take a look!

Update! Version 2.01 Fixed issue causing script to bank for potions even when option not selected.

I certainly have not coded that, so it must either not be my script or the client...! Everything seems to be working OK for me (just did a test run now), so i'm not sure what's gone wrong there... Does it print anything in the logger? apa

oo. That's odd, thanks for mentioning! I will take a look. Cheers apa

UPDATE! Version 1.62 Added support for water boiling ("cooking" bowls of water)~apa

That's odd as I don't seem to remember adding that. Perhaps you've got the wrong script, or the client is acting funny? Try rebooting the bot and giving it another shot! apa

Hey, thanks for the kind words I can add worldhopping to roam mode, will find space on the Gui to add that and will put it on the to-do list. As for the crab selection, it should aim for the closest one which isn't already under attack, but sometimes it can deviate from this just to make it seem more natural. I can probably increase the accuracy of this though! Cheers apa Hey, unfortunately as i'm sure you can understand, I cannot offer multiple trials to the same person. Sorry about that!! apa Firstly, thanks for choosing the script! Unfortunately bans are issued somewhat randomly, however there are a few steps which you can follow to minimise the chances: As you said, play inbetween Spread botting sessions out throughout the day. I'd say that even 2 hours is potentially too long. Try and keep it under/around an hour to be extra safe! Have a brief read of this thread written by one of the bot developers: osbot.org/forum/topic/45618-preventing-rs-botting-bans/ The way I see it, progressing slowly is much better than being outright banned Also, if the account really means alot to you, I would recommend resisting the temptation to bot on it, that way there's no worry that it will get banned. ~apa Hey, that's ok. I've restarted your trial as it does indeed seem you haven't got a chance to run the script. Cheers for stopping by! apa

Hiya! When I said console, I did indeed mean logger, which can be accessed via options>show logger as you said. Whenever the script decides to make a bold/state changing move, it will log what it is doing so that the debugging process is a little easier. I also added status logging for CLI users such that they know the script is going strong! I'm glad to hear that your problems are solved, please let me know if you encounter any more! apa