Apaec

Both trials activated !

Hey, The script won't do this, it only works at fixed locations. If you're wanting to cook at a fire, perhaps try rogues den? I could certainly make it an option, but it would be quite difficult to get it working as you can't light fires on all tiles and it would add additional complications wrt. banking, etc. Also, cooking this way is really inefficient! Apa Sure, trial started!

Certainly, trial started The mark looting should be independent from progressive mode, it's strange that this is what you've found. The mark looting is just based on reachability so presumably any issues with this would be rooted in the client. It is likely caused by a different factor, for example resizeable mode. If you're in resizeable, try switching to fixed? Alternatively, it could be mirror mode related. Are you also experiencing it on stealth injection? -Apa

You put it in the OSBot data folder and then run it with OSBot

I'm sorry to hear this Bans are fairly random and this certainly sounds like you got unlucky. With that said, it is brave to assume that any script (or bot) is safe to use for any extended period of time -- jagex is very good at enforcing its game rules. As I don't handle the store nor the payment system, I am unable to directly refund you, however to my understanding the OSBot policy specifies refunds are not given to users who recieve in-game bans. It is up to you to take the precautions to prevent bans and ultimately you use botting tools at your own risk. To help reduce your chances of being banned in the future, you might find this thread to be worth a read: https://osbot.org/forum/topic/124429-preventing-rs-botting-bans-v2/ Best Apa

I'm not sure if the method is currently profitable, and you may need a little more than 200k to start with. You can always try with 200k, but you would have to do trips to the GE regularly. The script spends roughly 500-600k gp per hour with the usual rune configuration -Apa

Sure - trial started

Hey Thanks for the comments. In future, I would certainly like to implement something similar to this which keeps the camera at a fixed angle. Unfortunately, this would be a huge amount of work as I would have to write my own interaction & walking APIs which keep the camera fixed - this would risk reliability and would not benefit from the maintenance that the developers provide to the current API. Also, as i'm sure you know, reinventing the wheel is rarely a good plan. I don't think the fixed camera setup would improve efficiency and i'm unsure as to whether it would affect detectability (probably wouldn't). Nonetheless, thank you for this suggestion -- i've made a note of it -Apa

That certainly sounds pretty unlucky. Everything I can do to prevent bans I have already added to the script - unfortunately jagex are very good at their job and with sand crabs being such a popular place to train, the area is likely regularly scouted manually by moderators. Hopefully in future the accounts will last longer - also, I wouldn't worry about a VPN. For more info on bans, be sure to skim over this thread if you haven't already: https://osbot.org/forum/topic/124429-preventing-rs-botting-bans-v2/ Best Apa

It's probably internally randomised, plus there are all sorts of factors which mean the interval won't be millisecond consistent anyway Thanks for the suggestion!

Combat scripts should really implement a mechanic which caters for breaking (As an example, in APA Sand Crabs, the script will walk the player to a safe place 2 minutes before a break starts to ensure a successful logout). I'd suggest letting the script writers know and they can advise you further Apa

It clicks as soon as options become available, e.g as soon as you can select the alch spell, it will, and as soon as you can click the item, it will. Efficiency should be optimal Apa

Hey, Sorry to hear this. Mind I ask - what is the reason that you are looking for a refund? If there is an issue with the script, please let me know so that I can look into it for you. You can submit refund requests to the OSBot staff here: https://osbot.org/forum/forum/150-refund-requests/ -Apa

Are you running the latest OSBot version? Also, you might find switching to fixed window mode may fix any problems you may have - OSBot only released support for resizeable mode recently and as a result there can still be issues Apa

Trial started

No-one really knows and there isn't a way to find out. All I can say is that SI is less resource intensive and much more reliable - in the end, reliability is what counts! Hey, Sorry to hear about this - what exactly went wrong? Perhaps you could send me a copy of the console logger so I can prevent this from happening again, if the cause was indeed a bug. With that said, this is the first time someone has had a problem with getting stuck while resetting so it could well be that your account was logged out for a different reason, e.g if you were crashed with the option 'stop if crashed' selected or alternatively if your character ran out of a resource. Apa Ah, hmm.. Is anything logged in the console?

Hey, This sounds like you might be using Mirror mode -- switching to Stealth Injection should fix this issue (for more information, check out the 'things to consider before buying/trying' section on the original thread) Best Apa

Sure , trial activated

Trial activated -Apa

Looks like a good start so far. I have to say, making oak larders is quite an adventurous script to write as your first. You may find it easier to work with something simpler to begin with, then work your way up Perhaps a simple oak chopping script? Apa

Sure - trial started Where abouts does it stand?

Sure - trial started Apa

Sure - trial started Apa

Sure thing, trial started - have you considered training at Sand Crabs instead? They're much better exp Apa

Thanks for this While there's nothing I can do about misclicks (other than to recommend you allocate enough CPU and run with sufficient network latency), i've been working on an error recovery system which is not quite ready for release just yet. When finished, this should hopefully allow the script to recover from unfortunate and rare situations like this. Thanks for the kind words, and that's some awesome progress you've clocked up! Apa