- Thread Author
- #481
Fixed in next update.
By registering with us, you'll be able to discuss, share and private message with other members of our community.
Sign up now!Fixed in next update.
Rob's Abyss Crafter Pro updated to v3.1.9.
Seems like an issue with detecting if the bank contains any, I'll investigate.I just had the bot erroneously exit, saying that it was out of pure essence. Log appears totally normal, aside from the fact I actually had many thousands of essence in the bank. Not sure what happened there.
Also, if the bot mis-clicks and enters the wrong rift, it will get stuck on:
"Interacted with: X rift"
Where X is the rift it was supposed to have entered.
Not too sure dude... Hmm.Had the bot crash an hour an 11 minutes in. Sucks to an hour of credits, but hopefully the issue is fixed soon. Not entire sure what happened to cause the error.
I logged in to the account sitting at the bank after a successful nature run with natures still in my inventory. This is what the client shows me:
https://i.gyazo.com/3474377ecf69696caba03a9d32a14da6.png
Not too sure dude... Hmm.
I've refunded you $0.20
It entered the cosmic rift instead of the blood rift. I don't think this was an error with your code, but rather just a runemate-related misclick. The bot just needs some sort of error-checking in case it ends up in an unexpected rift.Seems like an issue with detecting if the bank contains any, I'll investigate.
Which rift did you select, and on which one did it click?
I've had the same issue a few times. Probably lost ~3 hours due to it, but oh well. I just consider that to be a donation to RobinPC since he's maintaining and developing the bot so actively (most other bot's I'd be requesting a refund). I like to support developers that are so open to feedback on their project.Had the bot crash an hour an 11 minutes in. Sucks to an hour of credits, but hopefully the issue is fixed soon. Not entire sure what happened to cause the error.
I logged in to the account sitting at the bank after a successful nature run with natures still in my inventory. This is what the client shows me:
https://i.gyazo.com/3474377ecf69696caba03a9d32a14da6.png
Seems like the bots misclicks a bit too much lately. I'll see what I can do about it.It entered the cosmic rift instead of the blood rift. I don't think this was an error with your code, but rather just a runemate-related misclick. The bot just needs some sort of error-checking in case it ends up in an unexpected rift.
Funny enough, I just had a second very similar issue happen. The bot accidentally entered the pvp arena while trying to cross the wilderness wall after recharging summoning points.
I've had the same issue a few times. Probably lost ~3 hours due to it, but oh well. I just consider that to be a donation to RobinPC since he's maintaining and developing the bot so actively (most other bot's I'd be requesting a refund). I like to support developers that are so open to feedback on their project.I really wish the administration would fix their payment scheme... They justify it by saying they're copying Amazon's payment model, but they don't (and, practically speaking, can't) have the QA that Amazon does.
But customers losing their money due to no fault of their own has been discussed elsewhere so no point in rehashing it here. "Working as intended." It's the users and the bot creators who have to pick up the slack with a never ending refund game.
I'm just gonna enjoy using runemate until Jagex's legal team realizes that since real money is being involved, these shenanigans can be combined with lawyer gymnastics to get the whole site shutdown. Even if it's a lawsuit Jagex would lose, I doubt Party, Cloud, or any of the others are attached enough to the project that they would spend the tens of thousands of dollars to fight a long and drawn out lawsuit. I'm sure RM is profitable, but probably not profitable enough for them to go through that.
But at this point I'm WAY off topic. This has nothing to do with the bot anymore. Spoiler time. lol
That helps, I know why it's crashing. Silly mistake on my end. Fixed in the next update!Just wanted to let you know that it crashed again at the same spot. Definitely don't expect a refund. I'll give you all the details of the account so you can possibly narrow down the error.
A step away from the bank with nature runes from last run in inventory. When I logged in, I had 30 seconds before familiar vanished. 47/75 Summoning points. No pouches degraded. Plenty of ess and extra familiars in bank. Using RS3 screen layout. Same interface layout as suggested. Using bank preset. 4 Pouches. Wilderness Sword 1 (teleport in action bar).
Not sure what other details I can give. Hope that helps
Shouldn't even be possible lol. Which rune are you crafting?everytime i try to use i just get stuck on ''you do not have pure essenses to bind''. it appears that after binding the pure essensses it fails to teleport then it tries to bind again and get stuck.
Is your wilderness sword on your lsst action bar?nature , i dont know it just binds and say '' teleported to edge '' and get stucks lol
It isn't even possible to get stuck there Just ran the bot (same version as you) and it works fine for me...first
We use essential cookies to make this site work, and optional cookies to enhance your experience.