Apaec

Both trials activated!

You've made some very awesome progress... certainly seems like you've got your moneys worth! As for progressive mode, i'm not sure what you mean by this. Was this the attack style switching system? If so, it's on my 'would like to add' list (and has been for a while). I just haven't found the time or add this as i've been focussing on more pressing updates and rewrites to other scripts in my collection! If you'd like a trial, please let me know!

Sure - done! Glad you like it! This is something that I can add to the script if there is enough demand. However, you will need to have the teleports on you for it to work (e.g be carrying falador tablets for progressive mode to go from canifis -> falador etc). The script would have no interaction with the bank. Cheers for the suggestion! Apa

Sure, trial activated! Sure, done! Hi both, 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

You could try with a 'more spawns' sand crab position. Some spots only have 2 sand crabs, while others have up to 4 (many on CCI). Gauging the rate at which you clear the spawns can hint at using a more or fewer spawn location. Glad to hear the script is running well!

That was helpful, thank you! The cause of the issue was a capitalisation error in the game data entry for wines of zamorak. I've fixed this: Update! Version 1.07 Fixed capitalisation error with Wines of zamorak As usual, the up to date source code can be found at https://github.com/apaec/aio-herblore. For immediate access to this update, download and compile the script directly. Apa

Awesome to hear! Hoping to add the myths guild as a location too in the near future, working on training my test account up to accessing it so I can gather the game data. Cheers for stopping by!

Are you using stealth injection or mirror mode? You can see from the code here: https://github.com/apaec/aio-herblore that there's no specific code for ranging potions so it's odd that specifically range potions are going wrong for you. Apa

I don't want to make the ui too cluttered with individual options for individual locations! In terms of efficiency, walking is much faster than turning the camera as at the script is not able to reliably rotate the camera and interact simultaneously. As a result, this certainly looked less 'genuine' than walking. In future I would like to look into a way of getting the script to turn the camera to show both range and bank in both positions (and in-between) without hardcoding an angle or doing some horrible trial and error, however it is not as simple as you make out! If you're worried about bans, I think this should be fairly low down on your list of concerns. Much more important is how you make use of the script/bot (be sure to give this thread a read! https://osbot.org/forum/topic/124429-preventing-rs-botting-bans-v2/) Apa

As for your first point, it is a compromise - it used to be the case that the script did not walk to the bank, but instead turned the camera and clicked the bank (and likewise for the range). However, people didn't like this as it moved the camera too much, so I updated the script to walk. Naturally I cannot please everyone, so I opted to stick with this approach! As for switching to mirror mode, I can only guarantee reliability/offer support for stealth injection. Any discrepancies between SI and mirror mode are beyond my control as both utilise the same API. I would highly recommend sticking to stealth injection for the superior reliability and lower resource usage. Best Apa

UPDATE! Version 1.01 Fixed store dimension issue causing script to crash Implemented Buy-50 instead of Buy-10. The script will now buy out the runes faster! -Apa Issue has been fixed in version 1.01 (see above). Thank you kindly for reporting this to me. Apa I can confirm the script is working as of version 1.01, which should be released within the next 24h

Just a quick status update: I've managed to recreate the issue and am working on a fix as we speak. Sorry for the delay with this, the issue was caused by a recent game/osbot update (not sure which as of yet), but hopefully will be able to get a working version pushed out soon! -Apa

Have you considered: if (getMap().distance(player) <= 1) { // .. } ?

Couple of things. Firstly, it might be worth taking a look at the WalkingEvent API https://osbot.org/api/org/osbot/rs07/event/WalkingEvent.html (specifically setMinDistanceThreshold, which presumably doesn't do what you think it does) Secondly, it is worth noting that a Position (https://osbot.org/api/org/osbot/rs07/api/map/Position.html) represents an in-game tile. You might find your 'same tile' check can be simplified: if (myPlayer().getPosition().equals(player.getPosition())) { // .. } Best of luck Apa

No worries - switched the trial for you. Cheers! Certainly, done!

No worries, although the miner trial should still be active

I want to, yes - i'm currently looking to borrow an account which has access to the guild (my test account does not). Just need to hop onto an account for no more than 20 minutes to gather some game data to add the location to the script -Apa

It's 24h after I issue the trial!

Not easily - the OSBot walking system is in use in this situation - as a result, without writing my own, I would not be able to perform actions mid-way. Writing my own would sacrifice the reliability, support, future proofing and simplicity that the OSBot system provides. I understand that it is not ideal, but I believe the way it works at the moment is the better side of a closely balanced compromise! Apa

Replied to your PM !

Update: Version 3.12 Implemented CLI support - details below (this information can also be found on the initial thread):

Just tested the script at varrock east - the script handles the door perfectly and reliably (I stress-tested this). It also successfully recovers from misclicking the staircase. I've been working on CLI - everything is now in place. Hoping to release by the end of the day! Apa

Sure- activated!

I don't think there's anything I can do about this as when the script is on the login screen, the client has taken over. If you open the logger, it should tell you the reason for the script stopping - alternatively it could be the client killing the script because of persistent disconnections. Apa

All trials have been activated - thanks for swinging by! Apa