Welcome!

Writing this review mostly for the people, and a few issues to the WONDERFUL Developer(s) of this bot.

For The Community:
This bot is brand new, its GOING to have issues the first month. Please recognize this fact! You also need somewhat of a decent CPU to operate this demanding bot, as to be expected. Most issues people have completing a room is derived from not having enough CPU power. It's not fair to post a review saying "bots broken", when the user fails to meet the PC requirements. It's like buying a gallon of milk with no refrigerator at home, it spoils, then try to return the product for your misuse and negligence. Not fair at all guys...

However! The bot isn't perfect, I agree, but it's only a month old. There's a generous trial to test your PC. It resets after a time to try again when the kinks are worked out. Personally I've spent $5 on this script alone, about $1.50 was spent on trial & error. But the devs deserve it for bringing something like this to the community. And I will continue to support them through further developing this beautiful work!

My Review:
Baba - I use blowpipe for boulders and it's never missed. Not once! Only invo's I DONT run are mind the gap and boulderdash. But I honestly never tried them either so 100% could be fine if you have the cpu for boulderdash (supposedly people have issues with positioning running mind the gap)

Zabak - maaaaaan I know the frustration with the community here. Bot would be flawless with all invocations but one issue CAN (not always) get you killed, regardless if you do vanilla Zebak, that issue is the acid. Regardless of rock or wave phase, the bot struggles to position itself BEFORE the acid falls, it appears to prioritize waiting to see where the water balloons and rocks land, then calculates the path where to get behind-push-then clear acid. The problem that's killing me and possibly everyone, is if the acid lands on the player on either phase. It detects too late, has to cancel positioning to balloons and then takes way too much time calculating a path to get out of acid, then recalculates a path to balloon-push-clear acid. That takes too much time, especially if you're unlucky and have a lot of acid around the Boulder(not behind them, just surrounding it) it tries to walk around and just gets obliterated by the shout. Adding any invocations makes this so much worse. The blood orbs still confuses the bot if there's a lot of acid around you before waterfalls can clear. Zebak is kinda just a luck of the draw right now. I've seen the VorkathMate bot pre-determined where vorkaths acid falls and positions itself before the acid hits, if that's possible to code, maybe that'll help the standing on acid issue. Also, if you get pushed in the water, it misclicks the ledge to get back on, repeatedly. Or just spams brews and doesn't attempt entirely. Only way I've fell in water is because of a rare lag spike tho, getting there's not the bots fault, but getting out is nonexistent.

Akkah - if you have decent cpu, you can pretty run all invo's, surprisingly this bot does exceptional with him! May take a hit or two, more so in final phase. But you clear the boss and you get full hp so I don't see why people comment "takes unnecessary damage" when he hits thru prayers a bit, and random orbs are hard to calculate a path 100%, don't get greedy, the bot does well enough here!

Kephri - this needs a bit of work too but can scrape by. My issues are with how it handles dung, it gives waaaay too much space to get melee and mage scarab trapped (rarely on mage). Leaving 4 tiles in between the walls, it moves two spaces for the 1 tile airial attacks. 1 tile away would make the world of difference if you don't use the invocation that makes the blast radius bigger. Regardless if that's fixed, I also noticed it purposely position itself before the dung wall to be 4 tiles apart. And I may be wrong but I think choosing the corner for first dung wall would be better. Back to the trapped scarabs- the bot will spam click the trapped melee scarab when it can't reach, and will do this indefinitely. To mitigate I set up soldier scarab for mage gear (next best thing if you can't melee, DONT RANGE IT!) & blowpipe for mage (don't do cb or bow unless tbow, too slow and you risk tanking a mage hit). Those mitigations make the Kephri phase last way longer than should. Infact, kephri takes a lot longer than Akkah most of the time.

Warden - I wish it would use the salts right before phase one obelisk. It pulls it out but doesn't use it sometimes. Seems to wait for phase 2. If you use something other than fang for special attacks on phase 1 obelisk, say a dds- after you run out of special attack, it doesn't switch back to a fang till like... 20% health, and the dds without spec is incredibly inaccurate. You take so much damage, so just use your fang specials so it doesn't delay the switch after spec'ing. The phase 1 fight is great except for the triangle ️ floor attack where it positions itself next to the obelisk, gets ready to avoid the red about to hit but doesn't move fast enough and always takes 20ish damage. Windmills & square electric blasts are flawless though! Phase 2 does incredibly well! However if your cpu is limited, the attacks will outpace the bot and you may die, so be careful about the invo's on warden regarding speed and frequency of attacks in phase 2 if you have a limited PC.

Quality updates - I haven't read anyone having this issue, so it must be on my end. But for some reason after it completes a raid, when it tries to resupply at the bank. It refuses to accept all my gear is on or in inventory. It always starts with my ruby dragon bolt (e) and says it can't find it, it tries 20 times, I get the orange warning on runemate, then the bot stops. I either have to clear all my gear presets and create them again for it to realize I have the gear, then will willingly walk into the raid, otherwise it wont leave the camel. To counter it, I keep the bot paused, pot up and get the inventory setup, enter the raid, then start the bot. Then it goes to town! But after one completion it will never recognize my gear or inventory again, nor in bank! So I have to baby sit the bot at the end to set up the next raid. Kinda frustrating but I know it's not permanent.

A pre pot preset would also be amazing but don't prioritize it until other kinks are worked out.

I hope to see a parameter we can set to adjust how fast the bot switches gear? Millisecond delay or tick delay system. Just because the gear switches are so fast that it would contend against Oda and Torvesta... maybe it doesn't matter but quality anti detection is always appreciated. Regardless we all know what risks we run so that's never on the developers

I only run a 150, if zebak wasn't a luck of the draw with him Hawk Tuah'ing with acid landing right on you- I'd have a 100% completion rate!

Hope this helps clear up any reputation lost, and helps others get comfortable with trial & error. It's an incredibly advanced bot! Would hate to see this project dropped

If you're dying you need to lower your invos

without fang/bis needs to stay around 150-200

if you find a invos your getting steady finishes stay there til you get a fang I myself tried to keep going higher and its just not worth the hassle.

Needs prepot update badly

Also very close out everything else but runelite and your client this is a heavy pc drainer even on an i7 laptop

this bot is great has a few bugs like monkey room sometimes get pulled into venom and keeps walking back into it, other then that its finished a handful of expert raids. sometimes i use a little manual input to correct things but aside from the monkey room it runs flawlessly if you're pc is good and your internet is stable. Don't leave a bad review if your pc/internet sucks obviously the script wont run right. hopefully the monkey room gets fixed and id have no problem writing this as a 5 star ! <3 thanks dev team

This bot has potential but way too many flaws and inconsistencies. $0.30 credit is pricy for having to babysit the bot so much due to the amount of errors/wrong decisions it makes. Another review stated that it continually gets more laggy past the 2nd or 3rd room, delayed clicks and decision making.

Zebak room is 100% inconsistent, some times it'll dodge the Blood Orbs perfectly, other times itll just stand there and take damage. It gets really confused and runs into poison all the time and makes a lot of mistakes when trying to clear a path for Zebak's special attack.

Kephri room has been getting better with recent updates, but the bot continues to freak out whenever you have to kill the Soldier Scarab and does not position itself well for Kephri's dung, honestly would be better to just leave it alone and focus on dps'ing Kephri.

Baba's encounter seems to run ok, except for boulder phase. First row will work flawlessly but then it attempts to hit the next boulder and skip it at the same time causing it to take damage over and over again since it would struggle to boulder skip. Red X'ing works okay most of the time unless it's lagging, then it will freak out and will occasionally stay next to a rock in prep for Baba's throw attack. Otherwise it would just continue trying to attack and get nuked.

Akkha seems to work just fine if youre not using any invocation other than Stay Vigilant. Continues to freak out with other invocations and waits to get melee'd before butterflying.

Warden's tend to work flawlessly given no lag or delayed clicks. Gets rough in the last phase.

Out of 30+ attempts and hours using this bot, I've completed only 3 raids even when with babysitting every session, the bot will just get nuked with bad decisions. Definitely has potential though.

Like everyone else has mentioned, the bot still has various bugs across multiple rooms - most of which can be assisted (if you're babysitting the bot and pause it to correct the error).

However, the biggest problem I have noticed is how (for some odd reason) the bot runs perfectly for the first 2-3 rooms. After this, an incredible amount of lag sets in which allows for misclicks and damage taken, sometimes even deaths. By the end of the warden phases, the lag gets so bad that it freezes the client and will not reconnect until RuneMate is closed. After closing Runemate, the client runs perfectly fine with no lag - but by that time you're already dead and your run/supplies are done for.

Of about 10-15 different raids, which all have made it past at least 2 or 3 rooms, only about two raids have been completed. I've spent multiple credits just playing with invocations and dealing with the lag which tells me this script is nowhere near ready to be sold. As noted by most other users, it does have potential though.

Hoping I don't get a ban from all of the obvious noob mistakes, and standing still until death due to lag... lol.

The only reason I believe the lag issue is due to this script is because I've never had this issue before, I'm running a fully capable gaming PC, and I'm also not the only one to mention this exact issue from this script specifically.

Wouldn't recommend using this bot for now, too many issues but had great potential. where it works, it does it flawlessly but some of the rooms it makes complete rookie mistakes that you need to babysit to get past

This script has potential but it tends to get stuck. Had to manually take control during zebak and kephri.
Eventually, the script caused runemate to use 100% of my cpu causing my entire PC to freeze. Throughout my trial, I made it to kephri once. Every other run, i'd die to zebak due to the 100% cpu load.

I don't even have bad PC specs, running a ryzen 5 5600x lol. no reason it should be using 100% of the cpu and 80% of 32gb ram

1 out of 7 raids completed, 150 invocation level. Seems to take unnecessary damage at Akkah, puzzle room and boss both. Died to Zebak roar multiple times too.

honestly once you get it setup with decent invo's its pretty flawless only problem ive run into is ZEBAK WAVES it never steps thru them just stands there and gets pushed until it dies & also sometimes doesnt shoot the ball to rock will just stand there pleaaaasee fix zebak roooom & i will always use thiss

This bot has alot of pottential but it fails alot.
Wich makes 0,30 a really high amount since the bot is not flawless.

Ahka and Zebak are nearly perfect with the bot.

In Baba's monkey room, it needs to avoid venom better.

In Baba's room with boulders, it assumes blowpipe use, which isn't always ideal.

Kephri sometimes ignores melee soldiers, requiring manual intervention.
Zebak should handle blood orbs better.

For Wardens, manual intervention is needed initially due to the Overly Drained invocation,

Overall, the bot performed well in a 500 raid with occasional manual pauses for keris healing.

Here is a detailed review from someone who has put over 30+ hrs into the bot already. I'm giving it 4 stars because it has amazing potential, and you can tell how much effort they have put into this. I haven't ran any invocations past 250 with this bot due to running it on an ironman w limited gear.

1: Crondis room: Does everything flawlessly except for blood orb invocations. Sometimes it freaks the bot out and it forgets to dodge waves or get behind rocks.

2: Kephri room: Does everything pretty well with every invocation turned on besides medic and overlords. The bot doesn't spec kephri for some reason with dwh only arcane scarab? Occasionally the bot will run under the 3x3 aerial when going to attack scarab when it spawns

3: Baba room: This is where the bot starts to struggle. It cant get the ticks right between the boulders. Also cant have on mind the gap because the bot spam clicks one tile too far and falls into the gap every time. As long as you babysit the bot during this room the bot will complete toa without an issue.

4: Het room: The bot does this room really well for the most part. If you turn on random attack intervals invocation it struggles a little.

5: Wardens: Since the update the wardens room is great. Occasionally misses a obelisk red floor pattern dodge, and an occasional boulder during final warden phase. Other than that this bot has so much potential and i look forward to future updates.

Days later this bot is not only the same price but is breaking further, I would really LOVE to continue spending money on this, Ranged is completely broken, wont even attack Zebak or Soldier scarab, and still refuses to path Baba boulders with dash off..

Great bot, and really impressed with how fast updates are made, usually on a daily basis at the very minimum. Once optimised, this bot will be the GOAT!

Great work.

Has potential. Glraing issues I have personnally seen: Prioritizes running up instead of being in the correct lane at baba boulders as well as when boulderdash is active on the off chance it does prioritize the correct lane it usually runs to early and get hit by the previous boulder by running into the side of it. With Kephri seemed to do fine unless medic was active. With medic active it panics and just esstentially switch between the kephri gear and swarm gear and doesnt attack anything.

Able to consistently do 300s, that being said, it's not able to consistently do DEATHLESS 300s. I do not have max gear but I have bowfa fang and toxic trident. The things it takes damage from / dies to are able to be patched tho like acid at crondis. I would say it's worth the 30 cent an hour for an ironman (which is what I'm using it on) but for a main this doesn't seem like it could do 400s+ without complete max gear AND luck, at least until he gets some patches in as this is fairly new.

simply amazing, struggle a little at kephri but still amazing overall.

Baba doesn't dodge boulders if they are far left or right and it will not shoot shoot soldier scarabs at all just paths out of harms way. Tbh kind of steep pricing. please fix soon, amazing if it gets beyond kephrii and baba.

Was going okay and quite impressed (Didn't complete a raid in 5 tries but was still impressed)
Have since paid for 5 instances where it has just done nothing at all.
Will be great once its fixed.

It seems the bot needs a bit more work to be fully complete, but after a couple runs during my trial, here's some things i can point out, some have already been said by other comments but I will restate them for the sake of creating a comprehensive list of issues.
- Often walks 1 tick too early on baba boulders (using dcb)
- Cannot successfully survive boulderdash, especially not consistently, and often wont run out of the way after it gets hit once.
- Often walks into poison during monkey room
- Does not position towards arcane scarab, often causing it to get hit when using melee (for people without a shadow)
- Occasionally gets hit by baba's thrown rock while red xing. (This happened right after boulder phase, could have something to do with the positioning)
- It got stuck when doing the pillars in Path of Scarabas, also pillars are slow, if possible make it avoid that route entirely.
- Does not dodge dps check against akkhas shadows
- Walks into poison at zebak, and refuses to stand less than 7 tiles away. My specific zebak poison left 3 tiles to stand on in that row, causing the bot to kinda freak out and try to position there, which caused it to die to a blood orb spawn.
- Would be nice if it had an option to use a melee spec at zebak like bgs (you can hit and run away without getting bitten)
- Similarly, would be nice if it would heal using blowpipe spec
- It would also be nice to recharge items. Toxic trident, blowpipe, serpentine helm, etc.
I'm very excited to see this bot in action, a LOT of work has clearly gone into it, and I assume you're already working on a fix for a number of the issues I stated. I hope you take this review into consideration. If it wasn't .30c an hour I would've loved to test it more.

To anyone currently running the bot on v1.1.25,
I recommend turning off mind the gap and boulderdash, doing baba first and babysitting it during boulder phase.
Also to save yourself some time while setting up, have like 250 arrows equipped if your setup uses them, otherwise it will try to withdraw the amount initially set, which is likely your whole arrow stack. Once that stack is reduced by even 1 arrow it will soft stop until either fixed for it times out.