We're complaining because there is no clear line of communication from the developers to the customers letting us know that they know what the problems are and are addressing them.
We're complaining because we don't know what's going on, and the only response we're getting is copied and pasted troubleshooting for problems we're not having and requests for logs for something that's wrong on their end.
" If you have a car, it may break."
I complain to the dealer or a mechanic.
"If you have a computer, it may break."
I complain to whoever made the computer.
"If you have a house, it may break."
I complain to the plumber, electrician, or contractor who is responsible for the broken part.
Do you seriously not see how mind blowingly wrong you are?
Respectfully - If your house breaks, you will pay someone to fix your plumbing, if your car breaks, unless it is under a warranty you'll pay someone to fix it and in that case someone is getting paid anyway, just not by you - if your computer breaks, same deal as the car...
You paid for a piece of software that was at version A - let's assume you paid for it a year ago. Since then you've received continual updating, new profiles, new features, new expansion support, and haven't paid a single extra penny. The software is now at version "S" and you haven't paid a single additional penny... This is analogous to you buying windows XP and then getting mad that it doesn't support HTML5 and you can't download patches for it anymore. I'm sorry but I'm on the dev's side here - the product works 90% of the time for me, if not more and when it doesn't it's an easy fix.
As a software developer myself, I can tell you that this model does NOT scale well, and frankly - no one in the industry uses a pay once, get free lifetime support model - Are you willing to pay a subscription fee, say $2.00/mo to bot and to have 24x7 support? I certainly would be - and I think many people would be, the reality of the situation is HB is very probably at critical mass, and the only way to continue to generate revenue from it is to enable a subscription and work to support it as such.
Now to the devs: If the issue is with the server authentication, and mesh downloads - why is it the bot cannot be run offline - I'm a bit baffled why if I am questing in zones x,y and Z, and am online for hours at a time that it must maintain a constant session connection, and why can't it cache all the data necessary, and refresh as necessary - For many of us we are repeating the same profiles over and over and over, whether it be for farming or for questing such that the amount of redundant data downloaded would seem to be excessive (I'm speculating, I don't actually know what is downloaded and maintained).
I would love to see some type of token authentication where we authenticate once every <insert time frame here> and receive a valid token, That token is validated at the time interval, and the session is stopped if it's invalid - this would prevent rogue use of the bot for more than the time interval - the user could also define the amount of storage to allow for cached mesh information, maybe 100MB, maybe 1TB, whatever works for each user - this would prevent each user having to touch the server continually... You should also consider some type of data deduplication if your servers are having difficulty sending/loading all that data to the users...
My point is if i have 10 bots that have all done dragonblight quests, I Shouldn't need to continually download tile information for those areas?
Respectfully - X
