By registering with us, you'll be able to discuss, share and private message with other members of our community.
Sign up now!Hi Serene,
Been using this bot for a while with really no issues until recently. I've received a pop up that shuts down the bot leading me to restart it and lose a little bit of $. I hit submit on the error message so you should have received that from RuneMate's end.
I've attached my transaction history. Can you please look at the double charge "yesterday" at 11:18PM and 11:23PM. And then today, "19 minutes ago", "13 minutes ago", and "1 minute ago".
Requesting a $0.18 refund please.
Thanks.
View attachment 7028
Even if you sent them through the client submit, because there is no way for me to see who submitted what logs through there, you will still need to follow the guide in the overview for refund requests. Will need every log for each session.
Also note that yesterday was update day. One was released, which broke OSRS interactions temporarily for the client. I have a section in the refund guide in the overview that explains how I handle client bugs such as those stemming from OSRS updates. If any of these sessions are from that, they will most likely be handled as described in the overview.
Okay cool. Sorry, here are the logs - and I don't run the bot until a while after the OSRS updates. Like I said, never had any issues with any of your stuff before.
Logs - Google Drive
Can you re upload the logs (or make sure that they are viewable for me)? The drive is showing up as empty.
I've uploaded them to Pastebin:
Oct 11 (quoted as "yesterday" above):
Divine NMZ - 11:23PM
Shared
Oct 12 (quoted as "today...minutes" above)
Divine NMZ - 1:52PM
Runemate
Runescape
Shared
The error also popped up today. Before I submitted it I took a screenshot, see below:
View attachment 7031
Oct 13 - Today:
Divine NMZ
Shared
Please let me know if you need anything else.
Thanks
hey man probably been discussed before but i just started using this script today, i enable quick prayers which have alread been set (i.e protect and eagle eye) and when i start it, it manually selects only protect. im not sure what im doing wrong
[/QUOTE]Still happening even without using special attack. Each time it appears to happen around the 4 minute mark.
I appreciate the refund of $0.18 but the errors occurred two more times since then. Logs for October 13 are within my previous post. Here are the ones today along with the error message:
October 15:
Shared - Runemate - Divine
I'll try using your bot again after the next update.
View attachment 7038
Divine NMZ updated to v3.4.12.
[
Since the refund, it hasn't been updated..
You will get a notification when the update goes through. The version number will change as well.
Refunded. Fixing special attack now. Until then, if you want to use the bot just don't turn on special attack.
Only protect from melee is allowed for quick praying. The support of other prayers (eagle eye, piety, etc.) is disabled atm. It should be listed in the overview, if not i'll make it more clear
bit of an update and knocking on wood as to not jinx myself, but i've gotten 99 attack defense strength and HP using your script and i couldn't be happier. thanks for solid work.
if you're open to suggestions, i think a piety flicking option would be absolutely superb. when i'm playing legit and flicking piety my xp/hour increases by almost 20k an hour.
Great bot man, the only thing I have had an issue with lately is, it will leave the bank without pots and run towards NMZ, but get caught on the wall to the left. But as long as I pause it, run to NMZ with the correct pots/equipment, then no issue.Serene submitted a new resource:
Divine NMZ - You couldn't dream for more exp!
Read more about this resource...
I run this thing 24/7 and never really have a problem. Except today it just mass spam clicks the npc. Not sure why, works otherwise fine and going to keep running it anyways. Just thought i'd mention it.
We use essential cookies to make this site work, and optional cookies to enhance your experience.