no what is that?Doesn't seem like a hard task at all actually xD Are you on Slack?
By registering with us, you'll be able to discuss, share and private message with other members of our community.
Sign up now!no what is that?Doesn't seem like a hard task at all actually xD Are you on Slack?
It's where all of the developers and some members of the community chat.no what is that?
just made my account on slackIt's where all of the developers and some members of the community chat.
Join Developer Chat | RuneMate
left it for one hour came back and it was constantly teleporting, I dident have bank options selected.
It runs out of area then can't get back into the area
Post your log file so the author can see what was going wrong.
RuneMate Client - Help > View Logs
What's wrong here? Your log appears correct.I think it is todo with the webpath is broken at the moment.
Here is my log it was too big to paste it all.
01:12:09 DEBUG Crab no longer aggressive, refreshing zone
01:12:09 DEBUG Traveling to refresh area
01:12:11 DEBUG Traveling to refresh area
01:12:12 DEBUG Traveling to refresh area
01:12:13 DEBUG Traveling to refresh area
01:12:14 DEBUG Traveling to refresh area
01:12:14 DEBUG Traveling to refresh area
01:12:16 DEBUG Traveling to refresh area
01:12:17 DEBUG Traveling to refresh area
01:12:18 DEBUG Traveling to refresh area
01:12:20 DEBUG Traveling to refresh area
01:12:21 DEBUG Traveling to refresh area
01:12:22 DEBUG Traveling to refresh area
01:12:24 DEBUG Successful area refresh
01:12:24 DEBUG Traversing to general crab area
01:12:27 DEBUG Traversing to general crab area
@soopaDo you ever plan on updating support for RS3?
What's wrong here? Your log appears correct.
What would you like to see added and/or changed to RS3?
Yesis it working on sand crabs atm ?
I have several logs, maybe you are seeing the log where the bot did try to come back to the crab area but I manually got it back to the crab area.
01:12:09 DEBUG Crab no longer aggressive, refreshing zone
01:12:09 DEBUG Traveling to refresh area
01:12:11 DEBUG Traveling to refresh area
01:12:12 DEBUG Traveling to refresh area
01:12:13 DEBUG Traveling to refresh area
01:12:14 DEBUG Traveling to refresh area
01:12:14 DEBUG Traveling to refresh area
01:12:16 DEBUG Traveling to refresh area
01:12:17 DEBUG Traveling to refresh area
01:12:18 DEBUG Traveling to refresh area
01:12:20 DEBUG Traveling to refresh area
01:12:21 DEBUG Traveling to refresh area
01:12:22 DEBUG Traveling to refresh area
01:12:24 DEBUG Successful area refresh
01:12:24 DEBUG Traversing to general crab area
01:12:27 DEBUG Traversing to general crab area
It couldnt travese back to rock crab area so I manully been taking it back there.
Yes
Chris, you're killing man... you never mentioned in your prior posts that this was in RS3 and only referenced rock crabs on the Last line of the second message lol (not a big deal, just didn't notice it the first couple of times I read you rmessage). You're a veteran RuneMate user now, you should know how to read the overview and when necessary provide proper bug information to us when reporting an issue.
What you're reporting is already known as an issue and we think it's an issue with the web in that area. If you go to the Overview page for this bot, it states that the rock crabs location recommends caution.
Creating bots is something I do in my free time. So when I have to take time out of my own personal time to investigate an issue that turns out it is already known (and could have been known to you as well if you read the Overview page), it doesn't sit over well. (Plus my GF nags me to get off my computer and watch some stupid Nicholas Sparkles movie with her... literally happened in this case.)
All I ask, and this is for every member in the RuneMate community, is that you read the overview and some recent posts on the thread before making your comment, posting a potential issue, or creating a review. If the bug is already known and it is out of reach of the Bot Author's hand (like this one), there's nothing either of us can really do other than wait.
Edit: I'm not mad or feel anything near anger towards the situation, and I don't want it to come off that way. My point is just that I'd like some uniformity and some prior research from the users of the community before post in a bot discussion's thread.
Ok, so a few problems here...
One: The bot resets when crabs are STILL spawning (there is no need for the bot to reset the crabs, for any reason).
Two: Upon pathing back to the shore (under Spot Hop setting) the bot can't decide where to go. It will click to the left (run 5 paces) then click to the right (run 5 paces) (these clicks on the minimap); causing your character to run back and forth from left to right, before - after about 10-12 seconds of the bot doing this - decides finally upon a location to start attacking crabs.
Three: The bot literally has been running for 9 minutes and it has already "reset" the crabs TWICE when they aren't even 'despawned'. What is the point of this? This is unnecessary, no actual player playing the game would run to reset crabs if they don't need a reset. If I saw a player doing this every couple of minutes I would assume they probably have a broken bot or have some sort of mental incapacity crippling their decision making process.
For a bot that is $0.06/hr, these pathing issues and unplayer like actions (despite the antiban system in place) should be patched. I would understand if this bot was free, but this is real money we are talking about here. Again, sorry if this feedback sounds harsh but please.
Issue Four: I spent 6 minutes finalizing this post before submitting it. The bot decided it needed to reset the crabs AGAIN. This is THREE times in 15 minutes.
EDIT - Issue #2 listed above is recurring after EVERY reset (which seems to happen about every 5 minutes?).
Also - noticed another bug. If you gain a hitpoint level while you are running the bot, the bot will NO longer eat food. This is because the % threshold to eat at has changed. For instance, if you are 50 hitpoints, and say to eat at 50% HP (meaning 25 HP left), and then gain an HP level (so you are now 51) the bot cannot determine the new 50% of HP since the original 50 HP is now 51 HP. This is fixed if you reboot the bot (which causes another $0.06 to be taken from your RM balance) but if you do not reboot the bot you will need to manually eat food (babysit) or... reboot the bot so the bot can do it's own thing. This is unfortunate because you aren't able to leave the bot unattended for hours at a time, especially at the risk of gaining an HP level and dying. For a premium bot, this shouldn't be.
My suggestion is to add a common HP level to eat at. Instead of a % threshold, you would choose when to eat (under 40HP, etc. etc.). Please implement this as soon as you can.
Until you implement the suggestions/feedback I've pointed out above, I personally have found this bot not worth using, NOR paying for. Once this is implemented, I will gladly use this bot.
ApexCrabber PRO updated to v1.1.7.
I have no idea, I've personally never gotten a ban using any of my bots (and I literally just got done with a week long botting session.) In his case, he could have used powerban recently, used no break handling, etc... But regardless, with botting there is ALWAYS a risk to getting banned. As for why He specifically got banned, I have no idea.I have a quick question and I know nothing is perfect so please, understand that I am typing this for the fact that the first review is about a ban. Was there a reason for that players quick hit?
We use essential cookies to make this site work, and optional cookies to enhance your experience.