CuppaJava updated Cuppa Tempoross with a new update entry: Cuppa Tempoross v1.4.15 Released! Read the rest of this update entry...
CuppaJava updated Cuppa Tempoross with a new update entry: Cuppa Tempoross v1.4.20 Released! Read the rest of this update entry...
CuppaJava updated Cuppa Tempoross with a new update entry: Cuppa Tempoross v1.4.22 Released! Read the rest of this update entry...
CuppaJava updated Cuppa Tempoross with a new update entry: Cuppa Tempoross v1.4.24 Released! Read the rest of this update entry...
CuppaJava updated Cuppa Tempoross with a new update entry: Cuppa Tempoross v1.5.8 Released! Read the rest of this update entry...
recent thing's I have noticed watching the bot while at home: 1. When a wave begins to emerge, and you're walking on the chain between land/boat it cant decide which one to the rope on, I don't know how much I can explain unless wish to speak on discord. 2. ( Know I Don't know if this is a bug) But while leaving a game i notice the character decided to run around to the other side to speak to another NPC to leave, which was very weird that just happened which is why i paused the bot to post this. P.S. I will join your discord to speak more if need be.
The chain issue is a bit of a rare edge case that's hard to completely avoid as there's a tiny bit of lag in runemate's clicks, so what happens is that the bot is moving towards the boat, detects the wave & decides on where to tether, but as it's still moving it might re-detect where to tether and decide on the other one. I tried to make the cutoff in a logical spot, but it's kind of a side effect of the client. I do have a tweak in queue that may fix this, but it's a bit of a weird one. This is a bug that I have logic to try to avoid, but it still happens really rarely. Shouldn't be very often at all. I think out of the ~600 rounds of Tempoross I've only seen it happen 5ish times, and it just continues whatever it was doing on the other side. If it happens more often definitely let me know though.
Thanks, just thought id throw those out as this bot has been amazing almost 99 from just doing tempoross, haven't had much issues.
CuppaJava updated Cuppa Tempoross with a new update entry: Cuppa Tempoross v1.5.9 Released! Read the rest of this update entry...
Hi the bot seems to get stuck during the end of the first break before logging back in, it gets stuck on saying "Waiting for bot to leave" and then triggers the failsafe after a few minutes. It also did the same with the agility bot yesterday. I imagine this may be something to do with the most recent update? Haven't tried today so it could be just a strange anomaly, will try again. Just giving a heads up
Yeah sorry man, Runemate is still partially broken after yesterday's game update. It may work if you start bot logged in or you may just want to wait for full fix release. I think Cloud is still working on it.
CuppaJava updated Cuppa Tempoross with a new update entry: Cuppa Tempoross v1.5.12 Released! Read the rest of this update entry...
CuppaJava updated Cuppa Tempoross with a new update entry: Cuppa Tempoross v1.5.13 Released! Read the rest of this update entry...
Recently, the bot has only been able to run 1-1.5hr at most. It always has the error saying that the bot was stopped because it idled for too long. and its always at the dock. Was not happening 2-3 days ago.
I've never heard of this happening, and especially if the bot was working fine a few days ago it's likely a temporary runemate bug on your end. If you haven't restarted runemate/osrs in the last few days, try that first (sometimes people don't). Or:
I have no idea why, but after a few rounds of using this, it started using 100% of my cpu. Unsure if runemate bug or what. I obviously couldn't continue, was getting like 3 fps. Maybe a bad loop? Had all settings off except cook harpoonfish. Happened after a runemate reset, but not a runescape reset. (Saw it happen, shut down the bot and reset runemate, but not osrs. When I restarted the bot, it went back to 100% cpu usage.) I'll investigate further if it happens after a full computer restart. Sorry for lack of information.
I think you're the same person who posted this on my discord server? Just to echo my same response here, that's definitely weird & I'm not totally sure why it'd happen. My Tempoross bot honestly isn't super optimized (but it also just has a lot to keep track of at all times), but I haven't heard any reports of this before. That being said, Runemate in general can be a bit weird with memory/cpu usage spikes. I'd probably just recommend restarting osrs/runemate/maybe your PC as you said, but besides that I'm not certain.
CuppaJava updated Cuppa Tempoross with a new update entry: Cuppa Tempoross v1.5.16 Released! Read the rest of this update entry...
