Apaec

Ofcourse, trial started Sure - trial activated. Exp depends on your stats, so definitely worth testing out I'm happy to give a trial, but you didn't specify which script you're interested in! -Apa -------- Apologies for delay in reply, I was away from home.

Glad you like it Ammonite crabs would be out of scope of this script though. The specificity of this script is the reason it is cheaper than more generalised fighting scripts such as an AIO crab killer (rock+sand+ammonite) etc. Thanks for the suggestion though! Apa

Sure - which script would you like a trial of? -Apa

Hmm interesting. While they're not worth much, every little adds up so as you said it might be worth adding to the script. I've added it to the backlog -Apa

Glad you got this sorted. It's a bit bizarre that screen size affected this, i'll run some tests and forward a bug report onto the developers if I uncover what could have caused this. -Apa Glad you got it sorted. As you've found, the name string has to match perfectly - while this might be a little annoying/fiddly, it is for security reasons. The last thing I want is for the script to try and guess what you meant when you typed in something incorrectly and inadvertently alch one of your valuable items! -Apa

Thanks again for the screenshot! Glad you're liking the script and thank you for your custom Hopefully the rooftop script lives up to expectations as well! -Apa Ooh, new potion. Didn't know about these. I've added them to the list of things to add. Hopefully i'll get around to it this week. -Apa Hi, Unfortunately this is not currently possible as the script is not aware of how much special attack percentage your weapon uses. Hopefully this shouldn't be too much of a problem though, as waiting until the bar hits 100% will result in using spec at the same frequency as using the full bar, so you're not losing out on any exp gains. -Apa

Sure - 24h trial for the APA chest thiever started -Apa

Hey, The refresh path is fixed, but the exact tiles clicked vary with camera angle, latency, zoom, etc, so I wouldn't worry so much about that. As for task levelling, this is something i'd like to add, but it adds increased complexity to the script with widens the scope for error. I've got it on my backlog list but I can't make any promises for it to be introduced as a feature in the near future. Thanks for the feedback Apa

Hey Glad you got it sorted. For future reference, you need to enable auto-equip of picked up ammo with the Lumbridge guide before using this setting. A pop up should alert you of this. -Apa

Sure - which script are you interested in? -Apa

Glad you're liking the script. Thanks for your custom If you run into any issues, please let me know. -Apa

Thanks for sharing! Congrats on the gains -Apa

Both trials started -Apa

Hey, The script used to have a check for the priest in peril quest, however this was removed due to login issues at the time. Now that those login issues with the client have been fixed, I can re-add the quest check and the script will stop in this particular case. Thanks for the reminder. In general though, I wouldn't rely on this script (or any other) detecting a misconfiguration - the UI is designed to set up the script after all. I'd suggest always double checking your settings before leaving your account unattended. Best Apa

Thanks for reminding me about this, someone else also mentioned this. I think Jagex tweaked the positions of the sand crab spawns in a recent game update, so i'll have to update the script accordingly. I'd suggest switching to a different spot instead of west 1 if that's still causing issues. I'll run some tests this evening and over this weekend on that particular spot, although I am already planning to extend it nonetheless. I'm not sure if it will help with the memory issues, but perhaps you could try running the script on the latest dev build?

Sure - trial started -Apa

Hey, The client break manager should log you out. As you correctly said, the script will run to a safe spot 2 minutes before a break is due to start. It will then wait there until the break manager safely logs you out. For some reason it looks like the break manager isn't logging you out - I have a feeling this might be to do with resizeable mode, but that's just a guess. I'd suggest switching your game to fixed view in the game settings. Could you let me know if that fixes it? If not, could you let me know the version of OSBot that you are using and i'll run some tests and get in touch with the OSBot developers if necessary. -Apa

Hey, As I said, there's probably a memory leak somewhere. My hunch is that it is to do with the client - another diagnostic question: What version of OSBot are you using? Also, did this happen in previous versions? Best Apa

I asked about low CPU mode to make sure you weren't using it - i'd recommend avoiding it as it causes scripts to run sluggishly. Hmm, that's very odd. Sounds like a memory leak somewhere. I have a feeling this is to do with the client, as the script has never had problems like this before (and the code hasn't changed) - see the screenshots on the original post). I'll see if any other scripters are experiencing this and then file a client bug report if necessary. Apa It's on the list of things to do, but sadly not an option yet. Sorry about that. -Apa

Hmm, ok - thanks for letting me know. I haven't been able to recreate this yet, but I will follow up as soon as I figure out what is going wrong. Apa

No worries - sand crabs trial started -Apa

Breaks are randomised by default. Both the break duration and break interval vary by +-10% if i remember correctly. -Apa

Ok thanks, this was helpful. Perhaps I need to modify the west 1 reset route. I have another question - are you using low CPU mode? -Apa

Sure - trial started. Have you considered botting at sand crabs instead? They're much better exp/h! Apa

Hmm, that's interesting. The script is not actually aware of how much a food item heals, but it is odd that it did not pick up the food items in your inventory. I will run some tests with sharks today and see it I can recreate this. For now, i'd suggest switching to a different food item. Glad to hear the script is working well apart from this isolated incident -Apa