Thank you for the update. Also, does this have the potential to continue being a problem? i.e., the latest update will fix the issue... until it doesn't, requiring another update to fix the issue... like a cycle?
Considering I have not seen any support threads with a description of the issue and logs attached I have to assume RuneMate is working perfectly for you.Thank you for the update. Also, does this have the potential to continue being a problem? i.e., the latest update will fix the issue... until it doesn't, requiring another update to fix the issue... like a cycle?
And if the answer is "we cannot anticipate future issues that may arise" - can we expect that this pattern of: Repeated premature terminations, Bugs interrupting sessions in progress, or *Otherwise failing to be provided with the amount of time and services we paid for - In Full* - to continue?
tl;dr: Please help us understand:
1) Why this is happening,
2) What tangible plans or efforts are already in progress to remediate the issue,
3) And what can we expect from a conversation about being refunded for incomplete/interrupted services?
Love y'all, sincerely, - just another dude asking the same Qs
Apologies, I didn't attach my own logs, but the description provided on several threads with a variety of details and concerns by the community are in line with what I've experienced as well (see above, included).Considering I have not seen any support threads with a description of the issue and logs attached I have to assume RuneMate is working perfectly for you.
Recent migration aside, Runemate is typically back up quickly after game updates (often no downtime, or within the order of low hours to low days). But yeah, all bot clients will periodically break, especially with game updates. It's the nature of the beast. Runemate's payment model (cents per hour) is probably the most user friendly when it comes to downtime, as you can always test using trials or at worst spend a couple cents on premium bots, or come back later; Other clients, if you pay monthly or one-time licenses, you're out of luck until when/if it's fixed.
Typically refunds would have been handled by bot authors, however that's not currently possible (for the past couple weeks) as transferring credits wasn't added to the updated site, and might not be. However it's my understanding that a new refund system is intended to be implemented soon, where botters will automatically be refunded under certain circumstances. But of course that's just my understanding of the plan.
what you're going through, it's been like this for three daysApologies, I didn't attach my own logs, but the description provided on several threads with a variety of details and concerns by the community are in line with what I've experienced as well (see above, included).
That being said, does this have the potential to continue being a problem? i.e., the latest update will fix the issue... until it doesn't, requiring another update to fix the issue... like a cycle?
And if the answer is "we cannot anticipate future issues that may arise" - can we expect that this pattern of: Repeated premature terminations, Bugs interrupting sessions in progress, or *Otherwise failing to be provided with the amount of time and services we paid for - In Full* - to continue?
tl;dr: Please help us understand:
1) Why this is happening,
2) What tangible plans or efforts are already in progress to remediate the issue,
3) And what can we expect from a conversation about being refunded for incomplete/interrupted services?
Love y'all, sincerely, - just another dude asking the same Qs
