1. I think today because they work at the morning on new update 2. it was a small patch 3. other bots updated at morning (but hb is safer)
I'd say 2-3 days, based on the fact the only dev doesn't seems to be around much. arguable considerign recent events :x The irony is strong in that post.
I would say more than 3 days since the devs are on vacation, perhaps Im wrong and they have someone on backup to update but I dont know. Since 6.2 hb was mostly down, perhaps more attention should be given to updating it and hire another dev to be there for hotfixes. If blizz keeps pushing hotfixes more frequently, the bot will have a lot of downtime, I don't know what to say really. I hope the update will be prompt, I doubt much has changed with this small hotfix but you never know.
And what is the alternative to waiting? A rushed bodge job? No thanks, I am happy to wait for a decent, secure product! PS, if you can't/won't get on board (with reality) then learn to deal with the state of affairs: significant Patch has just dropped, hotfixes are likely and expected -and with that so is downtime as HB conforms to them. There's loads of things you can do in WoW by hand (for profit) that the bot is not so smart at -like Pets via old raids. Rotation wise you can look into GnomeSequener. If you can't get on with any of that then you're really lacking one of life's great virtues, some bloody patience!
Wanting to use something u paid for = self entitled? I agree more tact could be used, by both sides tbh.
If they're not willing to take the time to go x64 you think theyre gonna hire a Dev just to get updates out faster? It's unfortunate they decided to take a vacation around 6.2 but they're entitled just like any other worker. Contingency and pro action has never been bosslands strong suit. We have no choice but to wait. Don't be in such a hurry for that next inevitable ban wave imo. tanaan isn't even meshed yet, let alone last patches lfr. They lost a lot of customers and some devs, they're running on a Skeleton crew to stay profitable I imagine. It's a business like any other. Be glad they aren't sub contracting their customer service to third world countries to save imo.
...botch... Job of what? Updated offsets on a mini hotfix? No need to protect them, if they wanted to post and clarify they would. Blizzard doesn't need to slip in a sneaky secret detection, the one that they have works fine. Besides the Dev teams from the other functional bots would have found it prior to releasing if it was there or findable for that matter.
I agree with a lot of points. Before store it was a job, now - it work with amount of responsibilities. I think raphus still on vacation cos in main update thread message written by not him and the message was edited with errors:
Yup, doubt raphus even know about it yet, and pretty sure he's the only one who can work on it (Apoc is no longer working on WoW)
1) they had several mornings last patch. 2) it was smaller 3) other bots were updated days sooner last time Wishful thinking though. To be fair I feel bad that they only have one guy working on it. Then again if you have one Dev, vacation approval probably isn't the best idea around a major content patch. PS - if there was going to be an update today they would say so as usual.
razer synapse macro are better did you just find out gnomesequencer because you advertesing for them but the problems with gnomesequencer is that whne there is something on cooldown it waits for it with razer naga 1 shot rotation or even autohotkey it keeps cycling trough spells
Secure product? Is there such a thing in this industry? I though the makers made it as secure as they could but that in no way means you are ever safe.
Ugh! Now I have to go on my vacation and not think about botting at all Will be more relaxing, good timing for me hahaha!
If you think HB is secure then you are a FOOL! In my opinion, I think HB is more prone now since Blizzard is really watching them.
I haven't really messed with that program even though I have it. You can set time delays between each macro can't you, like for GCDs so they don't overlap?
