CuppaJava updated Cuppa Tempoross with a new update entry: Cuppa Tempoross v1.5.63 Released! Read the rest of this update entry...
CuppaJava updated Cuppa Tempoross with a new update entry: Cuppa Tempoross v1.5.64 Released! Read the rest of this update entry...
CuppaJava updated Cuppa Tempoross with a new update entry: Cuppa Tempoross v1.5.65 Released! Read the rest of this update entry...
CuppaJava updated Cuppa Tempoross with a new update entry: Cuppa Tempoross v1.5.66 Released! Read the rest of this update entry...
CuppaJava updated Cuppa Tempoross with a new update entry: Cuppa Tempoross v1.5.67 Released! Read the rest of this update entry...
CuppaJava updated Cuppa Tempoross with a new update entry: Cuppa Tempoross v1.5.68 Released! Read the rest of this update entry...
CuppaJava updated Cuppa Tempoross with a new update entry: Cuppa Tempoross v1.5.69 Released! Read the rest of this update entry...
CuppaJava updated Cuppa Tempoross with a new update entry: Cuppa Tempoross v1.5.70 Released! Read the rest of this update entry...
CuppaJava updated Cuppa Tempoross with a new update entry: Cuppa Tempoross v1.5.71 Released! Read the rest of this update entry...
Hey Cuppa, Been loving the Tempoross bot. Worked great for the last two days, was able to run it for 3-4hours per session no problem. Now today Ive run it for less then an hour each time and at some point (seemingly random, didnt notice the first time it happened, but the second was by the cannons, the third time was by the whirlpool) it keeps throwing an exception out of bounds error and crashes the script bot. Ive submitted a bug report with the first two instances and figured I'd follow up with a hard comment as well. Let me know if there's a way to fix it, perhaps Ive done something stupid on my end?
I am seeing the exception logs, but honestly I'm not really sure how this is possible, outside of Runemate just generally bugging out for you. Have you restarted osrs and runemate since first encountering the bug? Sometimes runemate has a habit of fixing itself honestly.
CuppaJava updated Cuppa Tempoross with a new update entry: Cuppa Tempoross v1.5.73 Released! Read the rest of this update entry...
CuppaJava updated Cuppa Tempoross with a new update entry: Cuppa Tempoross v1.5.74 Released! Read the rest of this update entry...
CuppaJava updated Cuppa Tempoross with a new update entry: Cuppa Tempoross v1.5.75 Released! Read the rest of this update entry...
CuppaJava updated Cuppa Tempoross with a new update entry: Cuppa Tempoross v1.5.76 Released! Read the rest of this update entry...
is this broken? --- Double Post Merged, Nov 8, 2022, Original Post Date: Nov 8, 2022 --- tried to restart 4 times now and each time it just sits there and doesnt do anything
The bot definitely should be working, it's working on my end. I can take a look at the logs if you'd like to PM them to me/send them on discord (found in Help > View Logs) and they *might* help me narrow down the issue. I'll send the general debugging advice I give though, which will hopefully maybe help: If you are botting with Runemate on Runelite, try disabling all plugins as some can interfere with bots (you can star/favorite them so you don't lose track of which you had enabled). Otherwise, this sounds like the type of issue that is usually a temporary Runemate bug. You may be able to fix it by restarting OSRS & Runemate before trying the bot again. You can also try closing OSRS/Runemate & clearing your game cache (instructions on this page https://support.runescape.com/hc/en-gb/articles/360001441169-How-to-clear-your-cache-#OSWin, the Runelite game cache is found at %USERPROFILE%\.runelite\jagexcache\oldschool). Feel free to test using the lite version of the bot so you don't get charged while testing. If the issue persists or this doesn't help, let me know.
Hey so this error is actually a Runemate bug, not specific to my bots. Basically Runemate isn't able to connect to the game client. A few other people have gotten it from time to time but I'm not actually 100% sure of a consistent fix for it. You can message about it in Runemate's discord https://runemate.com/discord By my understanding you can try a few different things such as running runemate as admin, turning off any vpns/allowing runemate through firewall. Though sometimes I think this issue just fixes itself for people. Sorry I don't really have more info.
