Apaec

Sure, trial started

Sure - trial activated !

Authed

Just had a quick glance, i'm not sure why you're extending Script in your second class? Only one class can extend Script, otherwise the script executor won't know the entry point to your code Hopefully fixing this will prevent the crashing issue which you are experiencing. You should then be able to debug further issues yourself, if there are any As a side note, when developing code it is important to do it in small parts. Add one bit at a time instead of writing the whole thing and only then testing it. That will make sure you don't end up in this situation in the future -Apa

Trial activated -Apa

Hmm, looks like it's trying to read your quest data before fully logging in. This is frustrating as the script shouldn't be running while not logged in. I'll see if I can add a check for this Apa

Sure - replied on trials thread

Sure - trial activated !

Hiya, Sadly, in the interests of fairness, I can only offer a single trial to each user. Apa

Sadly not I'll do some test runs of the script and see if I can re-create this issue. Apa

Trial started!

Hey, This could be to do with a mis-configuration. If you open the console logger, it should print the reason out -Apa

Hey, This sounds like what happens when you run the script in mirror mode - I'd strongly suggest switching to Stealth Injection for a more fluid experience. Check out the 'things to consider before buying/trying' section on the main thread for more info Apa

Both trials activated Thanks for this suggestion, that's a really interesting idea which I hadn't thought of. I'll add this to my list of future things to add. Cheers! Apa

I'm sorry to hear about this - odd behaviour for sure. You didn't happen to grab what was logged in the console so I can stop this happening in the future? All the best Apa

Sorry to hear this It happens. Sounds like you got fairly unlucky though. Hopefully it's only a 2-day Apa

Probably not all that much now, it really depends on the price of unicorn horns and they are not worth a huge amount at the moment!

Trial activated thanks for stopping by! To qualify for a trial, your OSBot account must be over a week old (this is OSBot policy). As a result, I cannot offer you a trial just yet. Sorry about this -Apa

Hey I'd say that, for the most part, the chances of being banned with any script is about equal. There's little-to-nothing that a scripter can do to prevent bans, so your best chance is to keep sessions short and well spaced, use generous breaks and mix in some legitimate play. Also, fresh accounts tend to be targetted more by botwatch so waiting after creating an account may reduce your chances of being banned, but really no-one knows! -Apa

Hey, After purchasing the script, it should stay in your collection. This script has no renewal so it should still be there if you purchased it! Please could you double check your collection? If it's definitely not there, then you might have to get in touch with the community administrator @Maldesto who manages the store. He should be able to assist you further Best Apa

There are a few options here and I would strongly suggest against having any static duration sleeps anywhere in your code. Your first option is to try and find a condition other than animation to feed the conditionalSleep. You'll have to look through various debuggers to find this query value, if it exists. The second option is, as Malcolm suggested, some kind of animation timer. You can either implement this in-place as Malcolm suggested, or you can run it in a concurrent thread which is my preferred method, although there are a few intricacies to Java's thread system (specifically correctly creating, running, querying and stopping the thread) which mean there are ways this can be implemented incorrectly which give unexpected behaviour. This might be a little complex for someone as new to java as you, so perhaps the basic method is sufficient for now . With that being said, there are plenty of tutorials available online so if you want a challenge you could always give this a go! The benefit to the concurrent system is it is entirely detached from the running of your main code, so you are not relying on an iteration of your onLoop not exceeding a certain time threshold. Apa

Hey Thanks for the suggestions! If you're worried about bans, be sure to give this thread a read: https://osbot.org/forum/topic/124429-preventing-rs-botting-bans-v2/ - The risk is pretty much equal no matter which bot or script you use, so keeping a low profile is key. You can calculate the xp you've gained from the total by just removing the HP portion, I previously had these figures separate however too much data shown cluttered the paint. Perhaps i'll add it back, will see I would also like to add TTL stuff, i've added this to my list. As for breaking, the script does not have permission to change your break settings (this is handled by the client). The script is only allowed to know in how long you are going to break, so sadly this is not something feasible for me to implement. Eating on aggro reset is an interesting idea which I hope to explore! -Apa

Correct, apologies for this. It is a rule which all scripters must follow and is to prevent trial farming -Apa

Thanks for letting me know , was a little worried when you mentioned this on the sand crabs page! I will investigate this. For now, maybe try the east side. As a side note, you might find Sand crabs to be more efficient exp wise, although rock crabs are quite quiet now. Cheers Apa

Hey, Naturally this shouldn't happen, I'm worried that it did. I've not experienced this before nor heard of it happen and it's weird that the script didn't try to reset the area. Did the script log anything to the console, and are you sure the script was running and it hadn't terminated earlier? Also, you mentioned rock crab, I presume you're referring to sand crabs as you've posted on this thread, but just thought i'd double check this as I also have a rock crabs script -Apa