cuppajava
<3
cuppajava
<3
cuppajava
<3
cuppajava
I appreciate the review :)
This type of thing can be caused by a lot of different edge cases honestly (temporary issues with runemate not detecting it, specific camera angle, or other factors like plugins) so it can be a bit hard to nail down every case. Will keep an eye out for it though.
Glad the bot is working well overall :)
This type of thing can be caused by a lot of different edge cases honestly (temporary issues with runemate not detecting it, specific camera angle, or other factors like plugins) so it can be a bit hard to nail down every case. Will keep an eye out for it though.
Glad the bot is working well overall :)
cuppajava
<3
cuppajava
<3 <3 <3 <3 <3
cuppajava
<3
cuppajava
<3
cuppajava
<3 <3 <3 <3 <3
cuppajava
<3 <3 <3 <3 <3
cuppajava
<3
Thank you!
Thank you!
cuppajava
<3 <3 <3 <3 <3
cuppajava
I'm sorry you lost HC status. But I really don't think this is valid cause for a 2 star review, especially if as you say "the bot works well". I'd NEVER recommend running this bot on a HCIM because it is not intended to be deathless; I wouldn't recommend running any PVM bots on a HCIM, but especially not gauntlet.
It is intentional that the bot stops when the time is reached, otherwise it might tick over into the next hour and charge an extra 20c for a few seconds of runtime.
This bot should not be ran on a HCIM.
It is intentional that the bot stops when the time is reached, otherwise it might tick over into the next hour and charge an extra 20c for a few seconds of runtime.
This bot should not be ran on a HCIM.
cuppajava
<3
cuppajava
I'm glad you enjoyed your trial period :peepo:
cuppajava
<3 <3 <3 <3 <3
cuppajava
You are a hero
<3
<3
cuppajava
Hey, I'm sorry the bot isn't working properly for you.
I just want to mention off the bat that a low success rate on a high combat account is not expected or normal. Just for reference, the bot tracks KD, and the current average KD (all botters) is 90%+. I only mention this to give some context on what is possible with the bot; I think the bot is malfunctioning for you unfortunately.
I DMed you with debugging advice but it looks like you're not on RuneMate anymore, so I'll paste it here too:
- 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.
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, and please send me a log (found in help > view logs) and I'll see if I can find anything
I just want to mention off the bat that a low success rate on a high combat account is not expected or normal. Just for reference, the bot tracks KD, and the current average KD (all botters) is 90%+. I only mention this to give some context on what is possible with the bot; I think the bot is malfunctioning for you unfortunately.
I DMed you with debugging advice but it looks like you're not on RuneMate anymore, so I'll paste it here too:
- 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.
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, and please send me a log (found in help > view logs) and I'll see if I can find anything
cuppajava
I believe RuneMate or the bot may have been having issues at the time, but everything should be working now :)
Please contact me if any issues persist & consider writing an updated review if things are working.
Please contact me if any issues persist & consider writing an updated review if things are working.