Welcome!

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

Sign up now!

Resolved Bot Loggin Issue, Wallet Tanked!

Status
Not open for further replies.
Joined
Oct 21, 2015
Messages
4
Hey RunMate Team. I was using Cuppas MotherLoad Mine Bot. set a break handler like normal and all started well and good. Went to work, visited family and went to bed thinking the Bot was still running (as expected). I return to my pc to find that not only had it been logged out for over 12 hours!!! but that it still took my credits!! absolutely tanked what I had left... I always check to see if there's any warnings or if RuneLite has a feature activated for incompatibility. no warnings where given as such when I started. However, after I found it hadn't been running and still took my money anyway, I started the Bot up again to see if the whole Bot was broken, but this time I see a blue message from RuneLite stating that the login handler may not be working properly, so be advised to deactivate it. Never seen this message before in my life.

I understand that it was an unavoidable issue, but I was not warned of this before starting it (as most likely the bug wasn't discovered when I ran the Bot initially). as such I don't feel its right to punish me with over 12 hours of a non-active Bot time still being charged to my account. I'd like to have a refund for the credits that was tanked from me.

I can provide any info regarding the Bot and the time it was ran, which I'm sure you can already see on your end.

mistakes happen, just hope that restitution is in order.
 
Last edited:
Joined
Apr 23, 2019
Messages
31
Hey RunMate Team. I was using Cuppas MotherLoad Mine Bot. set a break handler like normal and all started well and good. Went to work, visited family and went to bed thinking the Bot was still running (as expected). I return to my pc to find that not only had it been logged out for over 12 hours!!! but that it still took my credits!! absolutely tanked what I had left... I always check to see if there's any warnings or if RuneLite has a feature activated for incompatibility. no warnings where given as such when I started. However, after I found it hadn't been running and still took my money anyway, I started the Bot up again to see if the whole Bot was broken, but this time I see a blue message from RuneLite stating that the login handler may not be working properly, so be advised to deactivate it. Never seen this message before in my life.

I understand that it was an unavoidable issue, but I was not warned of this before starting it (as most likely the bug wasn't discovered when I ran the Bot initially). as such I don't feel its right to punish me with over 12 hours of a non-active Bot time still being charged to my account. I'd like to have a refund for the credits that was tanked from me.

I can provide any info regarding the Bot and the time it was ran, which I'm sure you can already see on your end.

mistakes happen, just hope that restitution is in order.

Weird one, Hard to say who's at fault here. I'd say a gesture of good will would be to give you maybe 3 hours refund.
 
Joined
Oct 21, 2015
Messages
4
Weird one, Hard to say who's at fault here. I'd say a gesture of good will would be to give you maybe 3 hours refund.

Any gesture of restitution would be appreciated. $2 is $2, I have the logs to prove that It ran roughly 4 hours out of the 18 it ran for. Which it has been able to do so perfectly, thus why I set up break handlers and come back to it after worm (yesterday was a busy day tho).

Is this the correct place for asking compensation? Do I contact RuneMate since this was a Developer issue (as they personally stayed their team was investigating) or do i contact Cuppa (Developer of the Bot) for a partial refund?

Obviously I don't want nor need a Full refund, as 4 our of 18 hours where used, tossing in a questionable legitmate break of 2 hours. Id say 3-4 hours gifted back is fair.
 
Client Developer
Joined
Oct 12, 2015
Messages
3,760
We made a change recently which inadvertently caused thread death on logout, that should be fixed within the next couple of hours. If you reach out to Cuppa, he'll be able to provide further information regarding refunds etc.
 
Status
Not open for further replies.
Top