Welcome!
By registering with us, you'll be able to discuss, share and private message with other members of our community.
Sign up now!You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
Cuppa Corrupted Gauntlet updated to v1.4.10.
- when enabled, 1-tick prayer flicking will only activate when we have 0 or 1 potions left, AND we have medium-low prayer (to save doses for stamina)
Cuppa Corrupted Gauntlet updated to v1.4.9.
- overhauled 5:1 bossfight logic (again)
- if the bot can't melee hit, it'll now walk around (rather than using a suboptimal weapon or idling)
- added logic to avoid getting "dragged" into kicking (if you're in ranged/mage combat with a npc and remove your weapon, you can get dragged; bot will now avoid that)
- more accurate tracking of hits
- other general improvements i forget
Cuppa Corrupted Gauntlet updated to v1.4.8.
- improved 5:1 logic quite a bit in Hunllef fight (bot now has no tolerance for crossing tiles, and will attempt to move around rather than attacking with non-optimal weapon)
- will use Direct Input for more actions (when enabled)
- fixed a niche issue where the bot could get stuck dropping & picking up paddlefish
- fixed an issue where the bot could unequip before equipping for no reason
Cuppa Corrupted Gauntlet updated to v1.4.7.
Cuppa Corrupted Gauntlet updated to v1.4.2.
- added a button for "Stop Before End of Hour", so you get the maximum bang for your buck!
- bot will now path from Grand Exchange to Prifddinas via the Spirit Tree (if started in the GE)
- tweaked a bunch of values for when to eat/drink potions at
- bot will now be most likely to eat the tick after attacking, while running from tornados (by my understanding, the most efficient time)
- bot will now track attacks using player animations rather than projectiles (will fix some weird issues where the bot could try to attack while it's attack is on cooldown)
- added an option for amount of time to delay between bot cycles (basically shorter delays will use more CPU power while being more responsive, whereas longer will use less CPU power but be slightly less responsive)
- fixed an issue causing crashes in v1.4.1