cuppajava
<3
cuppajava
<3
Gratz on the enh!
Gratz on the enh!
cuppajava
<3
cuppajava
The trial and premium version use exactly the same code. If the trial worked properly for you & the premium bot didn't, something is going wrong on your end. I'd be willing to help you debug if you contacted me.
Average CG KD success rate is currently above 90%, and some botters are seeing 90%+ success rates. A few things may cause a lower success rate, so you could try the debugging below:
- Try the "Recommend Settings Optimizations" button in the bot, and try to use some of it's advice if it seems useful.
- Ensure your stats are reasonable for CG (the Wiki recommends 85+ Combat stats, 77 Prayer & Rigour/Augury. But I'd prioritize high Ranged (or Magic if using 5:1 & Staff priority), ideally high Prayer & Rigour/Augury, high HP/Def. Att/Str don't matter as much).
- It's recommended to use RuneLite with GPU plugin on (if possible) as it runs smoother.
- Disable essentially all other Runelite plugins, as many can interfere with the bot (you can make a separate profile on Runelite with your current plugins saved, for using when not botting). You may choose to keep some on like GPU (with default settings)/FPS/Worldhop/Loot.
- Keep DirectInput & Hopping Mouse on, and/or have Runemate's mouse speed set to 3x (in Runemate settings).
- Ensure reasonable FPS (30fps+), Ping (50ms-), and CPU/RAM usage aren't spiking too much. You may consider closing other programs.
- It's always possible it's a temporary Runemate or bot issue and you can try again later.
- If you're on Mac, a feature called "App Nap" may be reducing resources to windows that are not focused, and may require keeping Runemate as the active window.
- It may just be very bad luck.
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.
PS, please consider updating your review when the bot works properly for you again.
Average CG KD success rate is currently above 90%, and some botters are seeing 90%+ success rates. A few things may cause a lower success rate, so you could try the debugging below:
- Try the "Recommend Settings Optimizations" button in the bot, and try to use some of it's advice if it seems useful.
- Ensure your stats are reasonable for CG (the Wiki recommends 85+ Combat stats, 77 Prayer & Rigour/Augury. But I'd prioritize high Ranged (or Magic if using 5:1 & Staff priority), ideally high Prayer & Rigour/Augury, high HP/Def. Att/Str don't matter as much).
- It's recommended to use RuneLite with GPU plugin on (if possible) as it runs smoother.
- Disable essentially all other Runelite plugins, as many can interfere with the bot (you can make a separate profile on Runelite with your current plugins saved, for using when not botting). You may choose to keep some on like GPU (with default settings)/FPS/Worldhop/Loot.
- Keep DirectInput & Hopping Mouse on, and/or have Runemate's mouse speed set to 3x (in Runemate settings).
- Ensure reasonable FPS (30fps+), Ping (50ms-), and CPU/RAM usage aren't spiking too much. You may consider closing other programs.
- It's always possible it's a temporary Runemate or bot issue and you can try again later.
- If you're on Mac, a feature called "App Nap" may be reducing resources to windows that are not focused, and may require keeping Runemate as the active window.
- It may just be very bad luck.
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.
PS, please consider updating your review when the bot works properly for you again.
cuppajava
<3
cuppajava
<3
cuppajava
Hey, so the bot should totally be working. Honestly I haven't made any significant updates to the bot in quite a while, in a couple months now, so performance shouldn't be degraded. Is it possible something has changed on your end?
A few things may cause a lower success rate, so you could try the debugging below:
- Try the "Recommend Settings Optimizations" button in the bot, and try to use some of it's advice if it seems useful.
- Ensure your stats are reasonable for CG (the Wiki recommends 85+ Combat stats, 77 Prayer & Rigour/Augury. But I'd prioritize high Ranged (or Magic if using 5:1 & Staff priority), ideally high Prayer & Rigour/Augury, high HP/Def. Att/Str don't matter as much).
- It's recommended to use RuneLite with GPU plugin on (if possible) as it runs smoother.
- Disable essentially all other Runelite plugins, as many can interfere with the bot (you can make a separate profile on Runelite with your current plugins saved, for using when not botting). You may choose to keep some on like GPU (with default settings)/FPS/Worldhop/Loot.
- Keep DirectInput & Hopping Mouse on, and/or have Runemate's mouse speed set to 3x (in Runemate settings).
- Ensure reasonable FPS (30fps+), Ping (50ms-), and CPU/RAM usage aren't spiking too much. You may consider closing other programs.
- It's always possible it's a temporary Runemate or bot issue and you can try again later.
- If you're on Mac, a feature called "App Nap" may be reducing resources to windows that are not focused, and may require keeping Runemate as the active window.
- It may just be very bad luck.
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.
A few things may cause a lower success rate, so you could try the debugging below:
- Try the "Recommend Settings Optimizations" button in the bot, and try to use some of it's advice if it seems useful.
- Ensure your stats are reasonable for CG (the Wiki recommends 85+ Combat stats, 77 Prayer & Rigour/Augury. But I'd prioritize high Ranged (or Magic if using 5:1 & Staff priority), ideally high Prayer & Rigour/Augury, high HP/Def. Att/Str don't matter as much).
- It's recommended to use RuneLite with GPU plugin on (if possible) as it runs smoother.
- Disable essentially all other Runelite plugins, as many can interfere with the bot (you can make a separate profile on Runelite with your current plugins saved, for using when not botting). You may choose to keep some on like GPU (with default settings)/FPS/Worldhop/Loot.
- Keep DirectInput & Hopping Mouse on, and/or have Runemate's mouse speed set to 3x (in Runemate settings).
- Ensure reasonable FPS (30fps+), Ping (50ms-), and CPU/RAM usage aren't spiking too much. You may consider closing other programs.
- It's always possible it's a temporary Runemate or bot issue and you can try again later.
- If you're on Mac, a feature called "App Nap" may be reducing resources to windows that are not focused, and may require keeping Runemate as the active window.
- It may just be very bad luck.
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.
cuppajava
<3
cuppajava
<3
So I'm not sure exactly what error you're seeing, but if it's "OSRS/RM Lag" that'd usually be some form of PC lag causing Runemate to not calculate tiles fast enough; It's not usually internet related. I'll send the general debugging below but feel free to DM me if it persists.
- Try the "Recommend Settings Optimizations" button in the bot, and try to use some of it's advice if it seems useful.
- Ensure your stats are reasonable for CG (the Wiki recommends 85+ Combat stats, 77 Prayer & Rigour/Augury. But I'd prioritize high Ranged (or Magic if using 5:1 & Staff priority), ideally high Prayer & Rigour/Augury, high HP/Def. Att/Str don't matter as much).
- It's recommended to use RuneLite with GPU plugin on (if possible) as it runs smoother.
- Disable essentially all other Runelite plugins, as many can interfere with the bot (you can make a separate profile on Runelite with your current plugins saved, for using when not botting). You may choose to keep some on like GPU (with default settings)/FPS/Worldhop/Loot.
- Keep DirectInput & Hopping Mouse on, and/or have Runemate's mouse speed set to 3x (in Runemate settings).
- Ensure reasonable FPS (30fps+), Ping (50ms-), and CPU/RAM usage aren't spiking too much. You may consider closing other programs.
- It's always possible it's a temporary Runemate or bot issue and you can try again later.
- If you're on Mac, a feature called "App Nap" may be reducing resources to windows that are not focused, and may require keeping Runemate as the active window.
- It may just be very bad luck.
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.
So I'm not sure exactly what error you're seeing, but if it's "OSRS/RM Lag" that'd usually be some form of PC lag causing Runemate to not calculate tiles fast enough; It's not usually internet related. I'll send the general debugging below but feel free to DM me if it persists.
- Try the "Recommend Settings Optimizations" button in the bot, and try to use some of it's advice if it seems useful.
- Ensure your stats are reasonable for CG (the Wiki recommends 85+ Combat stats, 77 Prayer & Rigour/Augury. But I'd prioritize high Ranged (or Magic if using 5:1 & Staff priority), ideally high Prayer & Rigour/Augury, high HP/Def. Att/Str don't matter as much).
- It's recommended to use RuneLite with GPU plugin on (if possible) as it runs smoother.
- Disable essentially all other Runelite plugins, as many can interfere with the bot (you can make a separate profile on Runelite with your current plugins saved, for using when not botting). You may choose to keep some on like GPU (with default settings)/FPS/Worldhop/Loot.
- Keep DirectInput & Hopping Mouse on, and/or have Runemate's mouse speed set to 3x (in Runemate settings).
- Ensure reasonable FPS (30fps+), Ping (50ms-), and CPU/RAM usage aren't spiking too much. You may consider closing other programs.
- It's always possible it's a temporary Runemate or bot issue and you can try again later.
- If you're on Mac, a feature called "App Nap" may be reducing resources to windows that are not focused, and may require keeping Runemate as the active window.
- It may just be very bad luck.
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.
cuppajava
<3
cuppajava
<3
cuppajava
> but as of late this bot seems to be performing badly on purpose
I have to be honest, this is an extremely frustrating comment, as I've spent over a year and a half consistently trying to make the bot better. I would absolutely never in a million years *intentionally* make it worse.
Also I've made essentially zero code changes to this bot in at least a month, (only some logging changes, and changes to the manifest for RuneMate updates), and I've made no major changes in months now. So if anything has changed lately it is absolutely something different on your end, or worse luck, or RuneMate acting up for you.
As always, I'm down to try to help debug but it's hard to do so in reviews. The general debugging is below if it helps:
-Try the "Recommend Settings Optimizations" button in the bot, and try to use some of it's advice if it seems useful.- Ensure your stats are reasonable for CG (the - Wiki recommends 85+ Combat stats, 77 Prayer & Rigour/Augury. But I'd prioritize high Ranged (or Magic if using 5:1 & Staff priority), ideally high Prayer & Rigour/Augury, high HP/Def. Att/Str don't matter as much).
- Use RuneLite, with GPU plugin on
- Disable essentially all Runelite plugins, as many can interfere with the bot (you can make a separate profile on Runelite with your current plugins saved, for using when not botting). You may choose to keep some on like GPU (with default settings)/FPS/Worldhop/Loot.
- Keep DirectInput & Hopping Mouse on, and/or have Runemate's mouse speed set to 3x (in Runemate settings).
- Ensure reasonable FPS (30fps+), Ping (50ms-), and CPU/RAM usage aren't spiking too much. You may consider closing other programs.
- It's always possible it's a temporary Runemate or bot issue and you can try again later.
- If you're on Mac, a feature called "App Nap" may be reducing resources to windows that are not focused, and may require keeping Runemate as the active window.
- It may just be very bad luck.
All the best.
I have to be honest, this is an extremely frustrating comment, as I've spent over a year and a half consistently trying to make the bot better. I would absolutely never in a million years *intentionally* make it worse.
Also I've made essentially zero code changes to this bot in at least a month, (only some logging changes, and changes to the manifest for RuneMate updates), and I've made no major changes in months now. So if anything has changed lately it is absolutely something different on your end, or worse luck, or RuneMate acting up for you.
As always, I'm down to try to help debug but it's hard to do so in reviews. The general debugging is below if it helps:
-Try the "Recommend Settings Optimizations" button in the bot, and try to use some of it's advice if it seems useful.- Ensure your stats are reasonable for CG (the - Wiki recommends 85+ Combat stats, 77 Prayer & Rigour/Augury. But I'd prioritize high Ranged (or Magic if using 5:1 & Staff priority), ideally high Prayer & Rigour/Augury, high HP/Def. Att/Str don't matter as much).
- Use RuneLite, with GPU plugin on
- Disable essentially all Runelite plugins, as many can interfere with the bot (you can make a separate profile on Runelite with your current plugins saved, for using when not botting). You may choose to keep some on like GPU (with default settings)/FPS/Worldhop/Loot.
- Keep DirectInput & Hopping Mouse on, and/or have Runemate's mouse speed set to 3x (in Runemate settings).
- Ensure reasonable FPS (30fps+), Ping (50ms-), and CPU/RAM usage aren't spiking too much. You may consider closing other programs.
- It's always possible it's a temporary Runemate or bot issue and you can try again later.
- If you're on Mac, a feature called "App Nap" may be reducing resources to windows that are not focused, and may require keeping Runemate as the active window.
- It may just be very bad luck.
All the best.
cuppajava
<3
So there's CA support for a couple incidentally (like no armor), however for others you'll need to do them semi manually; You can use helper mode though and it makes CG super easy tbh, as it handles all prayer/weapon switching, eating/potting etc. Or let the bot enter the gauntlet, pause, manually do whichever prep, enter the hunllef room & immediately unpause the bot.
So there's CA support for a couple incidentally (like no armor), however for others you'll need to do them semi manually; You can use helper mode though and it makes CG super easy tbh, as it handles all prayer/weapon switching, eating/potting etc. Or let the bot enter the gauntlet, pause, manually do whichever prep, enter the hunllef room & immediately unpause the bot.
cuppajava
<3
Good luck! :)
Good luck! :)
cuppajava
<3
cuppajava
i will pray for your enh :)
and thank you for the review!
and thank you for the review!
cuppajava
Hi, I sent you a DM a while ago but never got a response. I'll send my message below as well:
It sounds like you may have done all the standard debugging; It should be working though. I'll send some of the common advice in case any of it helps.
Try the "Recommend Settings Optimizations" button in the bot, and try to use some of it's advice if it seems useful.
Ensure your stats are reasonable for CG (the Wiki recommends 85+ Combat stats, 77 Prayer & Rigour/Augury. But I'd prioritize high Ranged (or Magic if using 5:1 & Staff priority), ideally high Prayer & Rigour/Augury, high HP/Def. Att/Str don't matter as much).
Disable essentially all Runelite plugins, as many can interfere with the bot (you can make a separate profile on Runelite with your current plugins saved, for using when not botting). You may choose to keep some on like GPU (with default settings)/FPS/Worldhop/Loot.
Keep DirectInput & Hopping Mouse on, and/or have Runemate's mouse speed set to 3x (in Runemate settings).
Ensure reasonable FPS (30fps+), Ping (50ms-), and CPU/RAM usage aren't spiking too much. You may consider closing other programs.
If you're on Mac, a feature called "App Nap" may be reducing resources to windows that are not focused, and may require keeping Runemate as the active window.
All that advice aside, can you send me a log (found in help > view logs) if it persists?
PS feel free to test using the trial so you don't get charged & feel free to request any refunds through (the refund page)
PS2: always feel free to reach out via DM if a bot is giving issues, as it's hard to have a dialog over reviews. And please consider updating the review when we get the bot working for you again
It sounds like you may have done all the standard debugging; It should be working though. I'll send some of the common advice in case any of it helps.
Try the "Recommend Settings Optimizations" button in the bot, and try to use some of it's advice if it seems useful.
Ensure your stats are reasonable for CG (the Wiki recommends 85+ Combat stats, 77 Prayer & Rigour/Augury. But I'd prioritize high Ranged (or Magic if using 5:1 & Staff priority), ideally high Prayer & Rigour/Augury, high HP/Def. Att/Str don't matter as much).
Disable essentially all Runelite plugins, as many can interfere with the bot (you can make a separate profile on Runelite with your current plugins saved, for using when not botting). You may choose to keep some on like GPU (with default settings)/FPS/Worldhop/Loot.
Keep DirectInput & Hopping Mouse on, and/or have Runemate's mouse speed set to 3x (in Runemate settings).
Ensure reasonable FPS (30fps+), Ping (50ms-), and CPU/RAM usage aren't spiking too much. You may consider closing other programs.
If you're on Mac, a feature called "App Nap" may be reducing resources to windows that are not focused, and may require keeping Runemate as the active window.
All that advice aside, can you send me a log (found in help > view logs) if it persists?
PS feel free to test using the trial so you don't get charged & feel free to request any refunds through (the refund page)
PS2: always feel free to reach out via DM if a bot is giving issues, as it's hard to have a dialog over reviews. And please consider updating the review when we get the bot working for you again
cuppajava
<3
cuppajava
<3
cuppajava
<3