Canifis is bugged right now, but I have a fix in queue to be approved soon. Will work again the next time an update is released (within the next few days). Sorry about that.
Ok, thanks for the quick response
By registering with us, you'll be able to discuss, share and private message with other members of our community.
Sign up now!Canifis is bugged right now, but I have a fix in queue to be approved soon. Will work again the next time an update is released (within the next few days). Sorry about that.
Cuppa AgilityAIO updated to v1.1.47.
- fixed issue with Canifis
Cuppa AgilityAIO updated to v1.1.48.
- fixed a bug that was causing crashes sometimes
Cuppa AgilityAIO updated to v1.1.49.
minor rare bugfix to all my bots
Cuppa AgilityAIO updated to v1.1.52.
- improved camera movement to look a bit more realistic
- pathing optimizations! Should generate steps much more efficiently & walk more smoothly. Please let me know if you notice any quirks/weird side effects from this change.
Cuppa AgilityAIO updated to v1.1.53.
- some minor user interface tweaks to make them show a bit better on smaller screens
- object visibility tweaks (to prevent trying to click far away objects that are barely visible)
Cuppa AgilityAIO updated to v1.1.56.
General bot updates:
- Fixed an interface issue which would cause the bot to freeze a few seconds when "Run bot with Settings" was clicked
- Fixed an entirely separate interface issue which caused there to be a delay when clicking the "Reset Settings" button
Cuppa AgilityAIO updated to v1.1.57.
- minor stability fixes
What type of pies are you using? It worked the last time I tested it with pies, but it may be an issue with that specific onegreat i love it but it doesnt eat my pies
Cuppa AgilityAIO updated to v1.1.58.
Cuppa AgilityAIO updated to v1.1.59.
Cuppa AgilityAIO updated to v1.1.60.
- made it so that if summer pies are selected & your current level is lower than the minimum for a course it'll eat a pie
I've gotten a few reports of this recently, and I'm sorry that it happened, but I really don't think it's a bug in my code. The code for stopping at a certain time has the highest priority and is really simple so I don't know what could be bugged.Had a 4:55 timer on the bot. System update happened and instead, it ran for 22 hours despite the timer. What do?
There's nothing I can really do here, this is just a quirk of runemate. My code just calls an action like "perform action "Jump" on "Wall", Runemate decides exactly what to do with the mouse. For what it's worth, I often right click object before clicking the menu.Anyway, to change the clicking from regular left click instead of right clicking then selecting jump. Majority players don't do those extra steps and can make it more of a bot behavior.
I've gotten a few reports of this recently, and I'm sorry that it happened, but I really don't think it's a bug in my code. The code for stopping at a certain time has the highest priority and is really simple so I don't know what could be bugged.
Just to clarify, you definitely clicked "Update Bot Settings" after turning on the stop handler correct? Was the bot still logged in and performing actions at this time, or did it get stuck at the logout screen? I'm really not sure what else I can do here honestly, unfortunately. I'd recommend just checking back in when you can to make sure the bot did stop, or you can use command prompt to schedule your computer to shut down entirely after a certain amount of time.
We use essential cookies to make this site work, and optional cookies to enhance your experience.