Apaec

Hmm, strange - those should work no problem. I'll run some tests and see if I can recreate this when I am back home -Apa

Hey, The script uses human-like movements. However, avoiding bans is much more down to how you use the script, rather than the script (or bot) itself. If you keep sessions short, use generous breaks and play legitimately between sessions, you should be fine. -Apa

Hmm, that's strange . Which rocks are you using? -Apa

Were the rocks depleted when you selected them? Be sure to select the rocks in their un-depleted state and that should fix the issue. -Apa

Hey, sorry you're having issues with this. Did you follow the setup guide on the front page? https://osbot.org/forum/topic/122438-apa-aio-miner. Also, there might still be an issue where the script mines depleted rocks in mirror mode, so I recommend using stealth injection for this. -Apa

Sure, trial activated -Apa

Sure, trial started! -Apa

Sure, trial started! -Apa

Sure, trial activated -Apa

Awesome. Thank you for sharing! -Apa

Hey, Sounds like the script might have run out of an item - if you open the console logger, it should display a reason for stopping and logging out. Hope this helps - let me know if you're still running into issues! -Apa

Sure, trial activated. Have you considered sand crabs instead? I've also got a script for them and they're better exp/h! https://osbot.org/forum/topic/98799-apa-sand-crabs/ -Apa

It does. Let me know if you'd like to give the script a trial! -Apa

Thanks for the kind words -Apa

Nice work, and well done getting something of your own up and running! My main piece of advice based on your code is to focus more on reliability. An important thing to remember is that the code interacts with a live game: a complex system with many points of failure beyond your control. As a result, any game interaction might fail. For this reason, it is important that at no point you implicitly depend on an interaction succeeding. For example, on line 28 you open the bank. However, this might fail! You then immediately proceed to deposit your items on line 32 assuming the bank is open. We can't deposit items if the bank failed to open, therefore line 32 might throw an error. A good way to avoid this is to ensure that, given a game state, only one interaction follows. E.g., the following code would be an improvement: onLoop() { if (getBank().isOpen()) { getBank().depositAll(); } else { getBank().open(); } }

Cheers, glad the script is living up to expectations!

Sure, trial activated -Apa

Sure, trial started -Apa

Hey! Hi, sure - trial activated -Apa

Sure, trial activated -Apa

Sorry I didn't get to you in time! Thanks for your custom and I hope the script lives up to expectations -Apa

Sure! Trial activated. -Apa

Sure - trial started -Apa

Sure, trial activated -Apa

Hey - I haven't in the past for a few reasons: (1) I didn't want to clutter the UI any more than needed; (2) I didn't want to add the risk of changing to an attack style by accident (e.g., accidentally levelling your pure to 2def because you used settings saved for another account). I might revisit this in the future though as I could see this being a useful feature if implemented in the right way! -Apa