I could never quite conquer. The complexity and difficulty of the CG made it a frustrating experience, often leading to numerous failed attempts as a full time working dad I didn't have the required time sink available.
The Cuppa CG Bot's performance is impressive. It optimizes resource gathering, effectively combats enemies, and ensures that every run is executed with the highest chance of success. This level of automation and accuracy is something I could never achieve on my own, making the bot an indispensable tool for any OSRS player struggling with the Corrupted Gauntlet.
Using Cuppa CG, I was not only able to complete the Corrupted Gauntlet consistently but also managed to pull an Enhanced Crystal Weapon Seed as well as full Crystal Armor.
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.