[cuppajava]

CuppaJava updated Cuppa Tempoross with a new update entry:

Cuppa Tempoross v1.4.15 Released!

Cuppa Tempoross updated to v1.4.15.

• if the bot is on the boat chain when a wave hits, it'll handle it more gracefully
• bot will fill buckets on the lobby boat if any are empty
• fixed a bug where it would rarely spam a failsafe message
• other minor tweaks

Read the rest of this update entry...

 

[cuppajava]

CuppaJava updated Cuppa Tempoross with a new update entry:

Cuppa Tempoross v1.4.20 Released!

Cuppa Tempoross updated to v1.4.20.

• fixed reward counter on the bot interface (Jagex had changed the message and messed up my parsing)
• fixed issue where bot would sometimes click on the fishing spot more often than needed if cooking was disabled
• some other niche fixes
• minor optimization tweaks

Read the rest of this update entry...

 

[cuppajava]

CuppaJava updated Cuppa Tempoross with a new update entry:

Cuppa Tempoross v1.4.22 Released!

Cuppa Tempoross updated to v1.4.22.

• updated to work with today's game update

Read the rest of this update entry...

 

[cuppajava]

CuppaJava updated Cuppa Tempoross with a new update entry:

Cuppa Tempoross v1.4.24 Released!

Cuppa Tempoross updated to v1.4.24.

• tweaks and minor fixes

Read the rest of this update entry...

 

[cuppajava]

CuppaJava updated Cuppa Tempoross with a new update entry:

Cuppa Tempoross v1.5.8 Released!

Cuppa Tempoross updated to v1.5.8.

• added option to input a custom bucket amount (between 2-5, 2 or 3 recommended)
• made the bot much less likely to run into fires overall (fixed various detection related bugs)
• bot will better handle instances of bad/incorrect data from the Runemate client (sometimes Runemate returns that there's no fires when there are some, and it'll do more verification now)
• bot will now be better at prioritizing which fire is closer in it's path (so as to avoid walking through a fire when trying to douse another)
• bot will no longer walk to a random coordinate on the lobby boat (was causing more potential for issue than it was worth)
• improved mast fixing to be smarter
• bot will now only use the main ammo crate for the boat, so real players don't get annoyed (the one closer to the chain for that boat)
• general flow improvements and fixes

Read the rest of this update entry...

 

[medsthegod]

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.

 

[cuppajava]

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.

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.

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.

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.

 

[medsthegod]

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]

CuppaJava updated Cuppa Tempoross with a new update entry:

Cuppa Tempoross v1.5.9 Released!

Cuppa Tempoross updated to v1.5.9.

• should now average even more points per game!
• better estimation of when to cook the final inventory
• better detection of which fires need to be doused and which don't when a wave is incoming
• (hopefully) improved detection of which tether to target when a wave hits & we're on the chain
• will eat admiral pie at more logical times

Read the rest of this update entry...

 

[magicmushroom]

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

 

[cuppajava]

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.

 

[magicmushroom]

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.

Ah I see, no worries, turns out its happening with all the bots so that explains it, thanks!

 

[cuppajava]

CuppaJava updated Cuppa Tempoross with a new update entry:

Cuppa Tempoross v1.5.12 Released!

Cuppa Tempoross updated to v1.5.12.

• slightly improved clicking of tether/fires while moving
  
• bot will sometimes randomly fix the nearby tether even if it doesn't need to at the moment (this is so it's more likely to be fixed by your bot/one of the other bots before the waves hit)
  
• tweaks to pathing when shrine is offscreen
  
• when using pies, bot will now only require half a pie to start a game
  
• bot will now recognize uncharged crystal harpoon
  
• breaks will now update during a game (but still only perform the breaks outside the game)
  
• general bugfixes

Read the rest of this update entry...

 

[cuppajava]

CuppaJava updated Cuppa Tempoross with a new update entry:

Cuppa Tempoross v1.5.13 Released!

Cuppa Tempoross updated to v1.5.13.

• minor edge case fix to all my bots

Read the rest of this update entry...

 

[flextroci]

CuppaJava updated Cuppa Tempoross with a new update entry:

Cuppa Tempoross v1.5.12 Released!



Read the rest of this update entry...

sexy update papi

 

[prodigy]

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.

 

[cuppajava]

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:

Often issues like this can be fixed by restarting both OSRS & Runemate and trying again, especially after game updates. But if that doesn't work you can also try clearing your game cache by:
1) Closing OSRS/Runemate
2) Clear your OSRS game cache
3) Open OSRS & Runemate back up
On windows, the OSRS cache can be found by clicking start and pasting into the search bar: %USERPROFILE%\jagexcache\oldschool\LIVE NOTE: ALL my premium bots have a LITE version you can use for an hour per week.

Please feel free to use the lite version while testing so Runemate doesn't charge you each time you restart the bot.

 

[bobzoc]

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.

 

[cuppajava]

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.

View attachment 11231

View attachment 11233

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]

CuppaJava updated Cuppa Tempoross with a new update entry:

Cuppa Tempoross v1.5.16 Released!

Cuppa Tempoross updated to v1.5.16.

• added optional minimum players for a game, to leave the lobby if less than X players & game is about to start
  
• 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.

Read the rest of this update entry...