Hey Cuppa, is there anyway to make the agility bot preemptively rotate the camera angle towards the next agility obstacle while still doing the obstacle before? I feel like that would look even more realistic than pausing for a second after an obstacle is completed to rotate the camera. Don't know anything about coding bots so I have no clue if thats feasible, just an idea after using this bot for 30+ hours. Thank you for the great work!
I already informed cuppa about this in at least 2 post. Although it should be possible to do so, i don't know of any simple way.
The hard way you can define valid camera preset for every position on the path of particular agility course. But well for this to be smooth you would have to predict where your going to be in future as camera movements are not instant. Therefore its a problem of getting under balance movement speed/camera rotation speed. I don't know of any simple way to solve this :/
So this is technically possible for me to add, and technically this isn't too difficult. The bot does already "know" which obstacle should be next, as is in the logic pre-hovering uses. And the "easy" way to do this would be, mid obstacle turn towards the "next" obstacle (and if the camera needs to be corrected slightly after landing, do so after). The reason I haven't added it yet is that sometimes the bot might be mistaken in which obstacle is next (tracking current can be slightly off sometimes), and pre-turning the camera might cause more bugs than it's worth. The reason this isn't an issue with pre-hovering is because if the obstacle it thinks we're on is wrong, then the obstacle will probably be offscreen anyway and it just won't prehover for that one obstacle, and it'll re-calibrate on the next obstacle. It's a lot more subtle than turning the camera the completely wrong way.
That being said, I haven't actually tried it and this kind of erronious camera turning may be extremely rare. I'll add it as an optional toggle at first and make it the default if it doesn't cause many issues.
Not sure why but after this last update the bot hasn't been working well, will idle for no reason and not log out for hours even though the bot has stopped due to the fail safe, specifically with seers village. Haven't been able to get it going for more than an hour.
Whenever a bot suddenly has a lot of weird bugs like this, it's often a caching issue. Can you please trying closing osrs/runemate and clearing your osrs cache? There's instructions on google for it. Feel free to test with the lite version so you don't get charged testing.
Lemme know if it still doesn't work, but this is the first report I've heard.
Update: I added an option to do what we discussed above. After cursory testing it seems to work well, so I'll push it as an optional setting and if it seems to perform well I'll make it the default.
Just to let you know, a bunch have tested the bot and used it when it was free/beta: 
