Apaec

Both trials activated -Apa

Both trials activated Apa Sure - no problem. Just started a fresh trial for you.

I'd use the official GE API: https://www.reddit.com/r/2007scape/comments/3g06rq/guide_using_the_old_school_ge_page_api/ That way you're not relying on a third party like RSBuddy for your data. -Apa

Sure - trial activated Apa

All trials started Apa

Checking if you are in Lumbridge is not necessarily a good solution - what if the user has their spawn point set to Falador for example? A much more flexible solution would be to check your HP. If you've hit 0 hp, that's the definition of death in OSRS, so that's probably your best bet. -Apa

Sure- trial activated Apa

Sure -trial started Apa

Hey, It looks like your trial has already expired (it only lasts for 24h) Since you didn't get a chance to use the script, i've re-started the trial on your account - good luck -Apa

Sure- trial started Apa

Sure - trial activated Apa

(wave)

Sure - i've cancelled the trial. When you would like the trial again, please drop a reminder here quoting this reply, and i'll activate it as soon as I see -Apa

Thanks for the feedback, osrsf2p brought this up earlier too. I'm hoping to revisit the banking code in the near future to see what I can do about this Best Apa

No worries, started a fresh 24h trial on your account so you can give it another go -Apa Sure -trial started! Apa

Sure - trial activated -Apa

Sure - trial activated -Apa

Both trials activated Thanks for stopping by, -Apa

Sure - 24h trial started for APA AIO Agility. Enjoy! Apa

I wouldn't consider mirror mode any safer than stealth injection - it's hard to form any conclusions about which client is more dangerous, and likely the difference is negligible. I personally use stealth injection for everything as it is most resource efficient and quicker to set up, but it comes down to preference. Here's a good thread on the topic which is worth a read if you haven't already seen it: https://osbot.org/forum/topic/124429-preventing-rs-botting-bans-v3/ 2: Yep, should work for addy, bronze, iron etc. 3: I cannot think of any further data you could gather, but thank you for offering. I'll have a chat with the other scripters and see if anyone else is having this issue, to determine whether or not the developers are already aware. Cheers

Thanks for the feedback. I believe the script has a similar mechanic to this built in, where it will withdraw-all if the number of empty slots in the inventory matches the number of items you want to withdraw. I think this means it will use withdraw-all when the ratio divides 28 without remainder, but I suppose steel does not match this. I've put this suggestion on my to-do list, it's not a small job so will require a fair amount of time dedicated to it - i'm not sure when i'll be able to schedule it in as of yet. As for the error, i've not been able to re-create this, and the recent surfacing of the issue suggests it is an issue with the client rather than the script. Have you encountered it in stealth injection? Best, Apa

Hmm, thought the lag could be associated with some kind of resource throttling, but sounds like it's not. It could potentially be a mirror mode thing, or even network related. I've just increased the delay slightly further for you which should hopefully resolve this (although i'm hesitant to increase the delay too much as this can lead to delays in other places): Update: Version 2.07 Further increase to animation delay to reduce impact of lag Cheers, Apa

Hmm - Are you running on low-CPU mode? Apa

Hey, Thank you very much for this detailed report. I've just had a look at the stack trace you've provided, and i'm not sure what could be causing this. Everything seems to be in order with the code, although I found a potential race condition (i'd be surprised if this was the root of the issue, but i've just patched it so we will see). As for the animation situation, this is a tough one to fix, but i've updated the timer associated with animation tracking to be less sensitive. This should hopefully reduce the frequency of interruptions caused by cancelled animations. Here's the update details: Update - version 2.06: Increased animation threshold, script should now re-start smelting/forging/smithing only when actually stopped. Fixed potential race condition in widget discovery code causing NPEs at runtime. Best Apa Sure - trial activated! Apa

Update - Version 1.04 Fixed build error -Apa