Tom

Added

Added

Hi, these things have not been implemented just yet, I've been a little strapped for time for the last week but should be able to get around to it real soon. Some things would be better than original, I'll add another trial to you

That solution is pretty good if I make it customizable. I just have to find some space in the GUI for it, and add more ingredients to the bowl of spaghetti that this script has become

Good feedback once again, The issue with bones / ammo has been one for a while, I have noticed it myself but as you mentioned in the previous post its hard to find a middle ground. I don't want to add too many configuration options. The bone thing is kind of related to waiting until loot spawns, but at what point do you want to sacrifice that XP / H to wait for a little bit of prayer XP? The scheduler doesnt save because the next time you run the script most of those conditions will likely not be met and cause some weird issues. If you load it in and tell it to swap to a steel scimitar at attack, but you already have 20 attack, it could execute something you dont want it to. I saw the only real benefit of saving to be for people running bot farms or something. It shouldnt be looting cooked meat, but it might be because of the safespot swap I did earlier where it tries to click the tile but clicks the meat instead, try drop it on the tile next to where you safespot. Full inventory thing is a little tricky, ill see what I can do there though I've adjusted the loot above value to calculate price of entire stack

Amazing feedback. You raise some good points which were actually in the original scope of the script, config save as, looting out of combat, etc. The PJer thing shouldnt be happening full stop, I'll fix that. Replace feature will need to be fixed as well so I will correct that in the same update. I believe the script will use map to walk to safespot if there are items on the floor normally, or it cant see the spot. I'll see if I can adjust this. Safespot unfortunately doesnt save across sessions at the moment, it was a bit of a design choice but I do see a viable solution that I can integrate. A lot of people were starting the script without setting a spot at all. Can fix the bone bury as well, and will look to include the advanced config in the next update. Happy to give you another trial once it has been approved Edit: update with major issues has been submitted. May take 24 hours

Yep, added trial Added

Lots of different ways to do things, I dont see why not

If you have an account I can use, I can probably get this added swiftly

Likely mirror related, an issue was reported not long ago so I will need to confirm. Thanks for the report!

You can enable the mouse tracker in osbot settings

Added

Ah yes, I addressed this with some larger locations, and will now do the same for Al Kharid Edit: You should be able to make this work properly if you also select the rock type on the first setting screen. Custom rock selection doesnt trigger the walking properly. So if you are doing gold ore, select gold ore and also custom select those rocks Added

Thought I fixed this a while back, will take another look.

perhaps you should do botted then

it USED the trout? the fuck. This seems wrong, mirror mode might explain it Judging by map, this is seers village spot correct?

Trial added

A few things to note Make sure you calling the ConditionalSleep within the main thread, if you didn't create a new thread you dont have to worry about this. Don't conditional sleep for the max duration, thats how your script gets stuck in the future and never recovers Make sure the condition isnt evaluating to true, you may think it behaves in a certain way but theres every possibility that it doesnt, and you will need to add extra conditions

Are you using mirror mode by any chance? When it gets stuck, was there anything in the log indicating why? When reporting issues it helps a lot when you can provide specifics, as with a script like this it is hard for me to replicate the scenario you are in. I can run it solid for hours without getting touched because my combat level is in a sweet spot, yet you havent managed to use a single bone. I can even see in my log that you haven't even attempted to run it on the latest version, I let you know that updates can take up to 24 hours to be live as they go through an approval process via @Token

when its running from the TP to the altar? I have made an update that should help this. Version 1.08 (may take up to 24 hours to be live)

Disputed Member:@Luis Duarte Why it should be removed: based on experience with script Details: No issues previously reported, also not marketplace related Link to topic:

Added

Added

Either its an RS update or thats not this script :S Going to assume its OSBot related for now.

Did not know this existed... I'll look to add it