Welcome!

<3

<3

<3

<3 <3 <3

<3 <3 <3

Hey, I'm sorry the bot isn't working properly for you. It really shouldn't be taking nearly that much damage on tornados, but may depending on a few factors (like fps/ping/cpu lag, or just bad luck).

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 average KD (all botters) for v1.0.0 is 82%, and some botters are getting 95%+. I only mention this to give some context on what is possible with the bot; I think the bot is malfunctioning for you unfortunately.

Though I know the above doesn't actually help; So all that aside, all I can do here is offer some general debugging advice:
- The main thing causing issues for botters is plugins. If you are on Runelite, please try disabling ALL plugins, as a lot of them break bot behavior. You can make a separate profile with all plugins off, so you can play on your regular profile when not botting.
- Make sure your FPS/ping are reasonable. (At least 30+ FPS and 50ms- ping)
- Make sure CPU usage/ram aren't spiking too much, and ideally try to minimize how much you're running in the background
- It could be the mouse speed. I recommend leaving DirectInput & Hopping Mouse on, and crank RM mouse speed to 3x (in settings)
- One botter found that his Antivirus was somehow throttling Runemate, so you could consider turning yours off if you have a 3rd party one

I will keep working on the bot, but I'm just trying to help bump your success rate to 80-90% here as other botters are experiencing.

<3 <3 <3

<3

<3

Just a note, it only prioritizes attacking over avoiding tornados if it's "far enough" from tornados and not on a dangerous tile, though depending on FPS/ping/cpu spikes/mouse speed it can lag slightly on it.

If you don't have directinput & hopping mouse on already, I do recommend them.

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 average KD (all botters) for v0.3.7 is 80%, and the single highest current run is 138:8 K:D (91%). Personally I usually get ~22:2 K:D when running overnight on my high-level-but-not-maxed account.

I only mention the above to give some context on what is possible with the bot.

Though I know the above doesn't actually help; So all that aside, all I can do here is offer some general debugging advice:
- The main thing causing issues for botters is plugins. If you are on Runelite, please try disabling ALL plugins, as a lot of them break bot behavior. You can make a separate profile with all plugins off, so you can play on your regular profile when not botting.
- Make sure your FPS/ping are reasonable. (At least 30+ FPS and 50ms- ping)
- Make sure CPU usage/ram aren't spiking too much
- It could be the mouse speed. I recommend leaving DirectInput & Hopping Mouse on, and crank RM mouse speed to 3x (in settings)
- Ensure the account stats are actually reasonable (stats in the 80s-90s should be decent, ideally with Rigour/Augury, though botters on pures/zerks are getting some kills)

Of course it's possible these issues you're facing are just things I need to improve, and I will keep working on the bot. I will take your feedback into consideration. But I'm just trying to help bump your success rate to 80-90% here as other botters are experiencing.

Hey, I'm sorry the bot isn't working properly for you.

I just want to mention off the bat that sub 50% success rate on a high combat account is not expected or normal. Just for reference, the bot tracks KD, and the average Corrupt KD (all botters) for v0.3.7 is 81%, and the single highest current run is 138:8 K:D (91%). Personally I usually get ~22:2 K:D when running overnight on my combat levels 80s-90s account.

I only mention that because that is the reason for the price. I wouldn't have it at that price if everyone was getting sub-50% success rates; The average is 81% currently.

Though I know the above doesn't actually help; So all that aside, all I can do here is offer some general debugging advice:
- The main thing causing issues for botters is plugins. If you are on Runelite, please try disabling ALL plugins, as a lot of them break bot behavior. You can make a separate profile with all plugins off, so you can play on your regular profile when not botting.
- Make sure your FPS/ping are reasonable. (At least 30+ FPS and 50ms- ping)
- Make sure CPU usage/ram aren't spiking too much
- It could be the mouse speed. I recommend leaving DirectInput & Hopping Mouse on, and crank RM mouse speed to 3x (in settings)
- Ensure the account stats are actually reasonable (stats in the 80s-90s should be decent, ideally with Rigour/Augury, though botters on pures/zerks are getting some kills)

Of course it's possible these issues you're facing are just things I need to improve, and I will keep working on the bot. I will take your feedback into consideration. But I'm just trying to help bump your success rate to 80-90% here as other botters are experiencing.

Hey, I appreciate the kind and detailed review :) As you mentioned a few of these improvements to make are still on my radar, but I'm glad it's working solidly as well!

Hey, something is definitely going very wrong with Runemate for you, as 3:40 KD is extremely low. The majority of botters (myself included) are seeing 80-90%+ KD, as you can see in the progress logs on the bot's page: https://www.runemate.com/community/resources/cuppa-corruptedgauntlet-beta-sale.2208/

For what it's worth, I do have a fix for a few current (minor) issues queued that should be released in the next few hours, so it's possible you might have better success in the next update.

Your FPS/ping/plugins all sound fine, which is surprising as usually it's a plugin issue causing this. There WAS a Runemate issue hovering large models last night, which may have caused the low success rate for you, but that has been fixed today & should be good if you restart OSRS & RM.

Other general advice is to raise your Runemate mouse speed (in Runemate settings), keep the settings similar to default, (double check plugins are off as those really are usually the issue but probably aren't here), check your CPU usage/ram is not spiking too high.

I do appreciate your suggestions, and I do plan to implement pretty much all of those eventually. But I want to be clear that those definitely aren't the root cause for the bot's low success rate on your end, which is why I'm focusing on debugging.

tl;dr: something is definitely not working correctly for you, and if you DM me more info on what seems to be slowing down prep SO much I can help debug more. But I think the best advice is to just wait a few hours/until the next update and let me know how it goes.

pls consider updating the review if it works better in the future

<3

<3

<3

Hey, I'm sorry you're disappointed, but I do feel like parts of this review are a bit unfair honestly. To address some of your concerns:

Regarding "ban rate" of the activity and/or bot's techniques:
No one has conclusively reported that they've been banned using this bot yet. I've botted 300 hours+ CG (mostly with DI & Mouse Hopping, some without), others more. One person mentioned he got banned after using it, but he also botted 7+ hours a day for weeks prior, so it was likely a delayed ban. Of course more bans will probably come in the future, but it's currently been very safe.

Regarding DirectInput & Mouse Hopping:
These can be disabled in settings and the bot will function fine, but the options exist because it improves the consistency/perfomance (especially for slower PCs, as Runemate's mouse is a bit inaccurate). As mentioned, there's been no conclusive proof this increases risk.

Regarding price:
I'm sorry the bot isn't working well for you, but the price is for the 80-90%+ WR a lot of people are seeing with CG. The price may not be worth it if you're having lower winrates, which might be happening for you, but I've been very actively trying to help debug issues. 95% of the issues reported were caused by plugins so please turn them all off when botting if you haven't yet. There's a few other things that could be issues, but it might also just be necessary to try again after I've made more improvements.

Regarding not using melee:
I don't know of any CG bots that use melee because it's much more complicated logic, and not really much better than mage/ranged.

Regarding killing the bear/taking extra time:
This can be disabled by toggling off "kill all demi-bosses". The bot defaults to killing the bear because it's more consistent; Demi bosses only drop their weapon part once, so if you come across 2 bears in a row (and don't kill them) + say a dragon, the run will be lost. But if you kill the 2 bears + dragon you're guaranteed to get all three T3 items.

"this is not the cuppa im used to"
I am sorry you're disappointed. I've been working on this about 5 months and will continue improving it, but it should be working solidly for most. If you're having specific issues I can help debug.

Hopefully this gives some insight into my thoughts/what's going on, and apologies the reply is so long.

<3 <3 <3

<3

Will do my best regarding improving damage avoidance in prep