Navigation

Navigation section

Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

Sign up now!
Overview Updates (64) Reviews (291) History Discussion
Leave a rating
GCVxRaS.jpeg


Check out the official discord channel: RuneMate Discord - Fight Caves Channel
Start the bot just outside or inside the Fight Caves.

The Trial goes up to wave 55 and is available for 3 hours per 3 days.
Use the Trial to make sure your tick health is good (95%+) as bad tick health can result in missed prayer flicks.
Use the Trial to get familiar with the settings and check for any issues after a recent update!

Recommended setup
Stats
Minimum stats: 40 def, 43 prayer, 61 range
Recommended stats: 70 def, 74 prayer, 75 range
1 def pures may struggle due to monsters attacking on the same tick (Damage is calculated on animation, not hitsplat, so even if they hit at different times the tick you need to pray is the same) Some users have had success using the 'Prayer only' mode (Only handles prayers, not eating or combat) and playing more defensively.

Equipment
Best ranged gear you can afford. At a minimum, Rune Crossbow with Diamond bolts (e).
Make sure you bring enough ammo for the runs you want to do. If you run out the bot will escape the caves and stop.

Settings
gq7SYGp.png
  • Like
Reactions: NLxOSRS, sletje and Defeat3d
Author
slashnhax
Downloads
3,419
Views
3,419
First release
Last update
Rating
4.03 star(s) 276 ratings
Download Join the discussion More information

More resources from slashnhax

Share this resource

Latest updates

  1. Fight Caves Mate v2.1.4 Released!

    Fight Caves Mate updated to v2.1.4.

  2. Fight Caves Mate v2.1.3 Released!

    Fight Caves Mate updated to v2.1.3.

  3. Fight Caves Mate v2.1.2 Released!

    Fight Caves Mate updated to v2.1.2.
Read more…

Latest reviews

W
charged me $2 and the bot would not even start, saying main class of fight caves mate could not be found and discord link is broken too
Upvote 0 Downvote
R
took 2 runs, but i got my first fire cape on the iron. its expensive but man is it worth it.
im going raise my range lvl and come back with better gear.
Upvote 0 Downvote
AMassiveDegenerate
I had used this for a handful of successful runs before the latest update, but one run with the new version and the bot just sat on pray mage against Jad and got nuked.
slashnhax
slashnhax
Sorry to hear that, I'll happily approve a refund (Sessions section of the Bot Store), can you please attach the logs to the refund convo as well?
Upvote 0 Downvote
H
Used the trial on my base 80s cb acc up to wave 55, then quickly switched to the paid version (full auto mode) for the last 8 waves (17 minutes of fighting). It's worth the 1$ imo, bot did not make a single mistake.
Upvote 0 Downvote
L
Changing my rating. I've been able to use the bot for an hour and so far its fairly good. The only issues I've had are from conflicts with an enabled plugin or ping issues causing the bot to miss prayers or stop which are most likely user side errors. IF you're using this bot multiple times, please do a short run using the trial before every session. I've done a session and everything went fine, did another session right after and had had an issue forcing a stop.
Upvote 0 Downvote
G
Multiple attempts now just to make sure it wasn't an issue on my end with plugins or ping health, free trail has no issues up to 55 on my iron, once on Jad will miss prayers and die
would recommended saving your credits until reviews state its working
slashnhax
slashnhax
Thanks for sending me the logs in your refund request, as per the message there, some users are experiencing method calls taking 5 to 10 times longer than expected, which I haven't been able to reproduce. I'm trying to figure out the cause but it's difficult as I can't reproduce the issue.

People experiencing the issue seem to be getting the NpcTracker took x ms warning (where x is > 20), so that would be something to look out for even if other reviews state it's working (because they don't have the issue).

I don't really think it's hardware related but it seems to be common with older intel cpus
Upvote 0 Downvote
P
tried it for 2 hours, got a insta perm ban. both hours didn't complete the script.

won't recommend this script
slashnhax
slashnhax
Sorry to hear you got banned, but usually first time offences are a 2 day temp, and it's pretty common knowledge that they delay bans to make it difficult to know what caused it. Kind of seems there's some critical information lacking.
Upvote 0 Downvote
botter222
Of the Jad bots, this one is the best. That said, it has quite a few issues with full automation and requires watching it the whole time. Next cape I'll be using this bot only in Prayer mode and only for the Jad fight.

Here's the issues I encountered:
- Listen to the warning about >95% tick accuracy. I was only getting around 85% on my mac and the bot kept dying around wave 40. This is an issue with the way MacOS implements power saving mode and even the tricks I saw to fix this by pinging my local network didn't fix it. However I switched over to my PC and was getting 98% tick accuracy and the bot worked much better.
- The bot doesn't use Saradomin Brew's very well. It would use brews to heal but then wouldn't use a Super Restore to restore stats. This means I had to switch to Sharks and the bot missed enough ticks that I only had 1 shark left out of 19 going into Jad and almost died to the healers.
- The bot is constantly too late for the first tick of protect from magic on wave 40+, it should start all those wave with protect from magic on until it registers the ticks from the mages.
- It doesn't prioritize protects very well, if two NPC are on the same tick it should always protect from magic over ranged or melee but it doesn't. I ended up changing setting to only protect from magic and the big melee guys.
- The "Off-tick NPC" setting can cause it to freak out when there's a lot of NPCs. It would regularly get stuck running back and forth when there were 4+ enemies. This led to it getting wailed on by 2 bats and missing protect from magic ticks. It should only off tick enemies that you have selected to protect from but instead it tries to offtick everything.
- Doesn't start Jad fight with protect from range on and can be too slow sometimes. It should leave range on until it registers ticks.
- It doesn't tag the healers right. It prioritized them but focuses on killing them 1 by 1 rather than tagging them first and them killing them. It should also only use the alt loadout for tagging them and the main loadout for killing them

You're much better off learning the safespots for melee and using this bot only in prayer mode for Magic and maybe Range if your stats are low. At 75 ranged and 75 def, the rangers barely hit me without prayer and they die very quickly so in the future I'll be doing the waves manually, keeping protect from magic on, bursting range down first, and safespotting melee and then only using this bot in prayer mode for Jad
slashnhax
slashnhax
Thanks for the detailed review and feedback :)

I'll be looking at adding full sara brew restores this weekend.
I'll look into it not praying for the first tick, it does schedule a prayer for the spawn tick (and lookahead will make it turn on x ticks earlier), but maybe it needs some tweaking.
The prayer priority order is mage > melee > range, if you can send me the logs I can see if there's anything there that can help me figure out why it's not praying mage over everything else.
Good suggestion regarding off-ticking, I'll make it only try to offtick things it's set to pray against, and revisit prioritisation for things that we're not praying against.
It shouldn't need to start with protect from range on since you get 3 ticks to react to the attack.
I'll look at adding more healer options, but currently it should be prioritising ones close to Jad not attacking the player, and if there's none, it'll knock off the closest first (unless you've got Jad higher on the prio list, then it'll ignore them after tagging).
I'll likely also look at adding a simplified Italy rock usage sometime soon, which should also help.
Upvote 0 Downvote
T
I initially started using the full control script however this kept dying around wave 50. I tried using it with saradomin brews + ranged pots + restores, but everytime it drank a brew it would ranged pot like 2-3x instead of sipping a restore to boost its stats.

I then switched to the prayer only mode and died to a mager.

For reference I am on a 1 defence pure, so missed flicks are a bit more dangerous and it does say that the full control script doesnt work great with pures.
Upvote 0 Downvote
L
want my money back 9 dollar somethimes during the waves he forgot prayer by mage 2 hits died happens again and again want my 9 dollar back plz ty and update the bot and fix the errors
Upvote 0 Downvote
Read more…
Top