"There is no such thing as a "lite" version of Honorbuddy." "Making Honorbuddy 'safely' work again after a patch is BosslandGmbH's highest priority. The product will not be made available after a patch until a thorough analysis of the changes have been conducted, updates made, and testing done. The process takes as long as it takes--if that's a month, that's what it takes. BosslandGmbH will not jeopardize the account investments made by its customers due to a rush to restore the product to service!" (excerpts from Game client "Patch Recovery" blues wiki entry) In short, this current situation feels like yet another withdrawal from a well-established rule and a good business practice, that thorough and complete analysis is first done, and then a product is released. You are essentially releasing a lite version, with reduced safety, and then pass on the responsibility of lost accounts to your customers. This is yet another bad business practice from you. In short, I suggest you do not release a lite version, as per your rules and your history. Work out any concerns you might have, and then release a safe version. Live up to your responsibility to combat any detection mechanics there are in place - as much as humanly possible. Let the process take as long as it takes.
You can call it bad business practice (it's not) all you want. Some of us want to use the bot detected or not, its that simple. There is a demand, its clearly stated there is a probability that the tripwire enabled version is detected, if you don't accept that risk do not go through and de-activate tripwire. You are acting as if they are releasing a version known to be detected as undetected and telling no one.
That is still using the bot lol. regardless if you're questing, fishing or just using it to DPS it's still botting.
It's up to you whether you want to disable tripwire or not. I don't see how you can apply that logic when it's a given choice and not forced upon all clients. As stated, they will not release the client publicly until it is fully tested and deemed safe. This post is misleading.
Ok, point No. 1: Then why didn't they give this option all along? Why now and not in the previous release? Or back, in the previous xpacs? And why in the previous releases we waited for a safe release? And everyone who asked for a quick, potentially unsafe release was directed to the "no lite HB" wiki entry? Why withdraw from that clause, too? Point No.2: We are paying for a program that is (more than expected) unsafe. Please now, don't give me the "botting is always unsafe". At least in the previous releases we knew that the team did what was humanly possible to safeguard us. Not now. And more arrogantly, they charge us for it; because guess what, the clock is ticking, we are losing days. Some people who prefer not to use a much less safe version will have their days vanish away. Point No.3: It's not about freedom of choice. That would be the case if the days did not count for our subscriptions. Anyone who fails to see that this is another attempt to make us pay for something that we didn't agree on, is shortsighted. You release an unsafe version? Fine. Please don't charge us for it. That's not what we paid for. Again.
They already said we will be compensated for the days lost. With your stance I don't think you're interested in a real reply, you seem to only be interested in what you have to say.
I am sorry if I offended you, honestly. I just am a little frustrated with all the withdrawals from previous statements from the company. And when a new one arrived, I maybe lost my temper. In your reply: I agree that if they compensate for the days with an active release, but tripwire on, i'll retract that part of my statement. However, as recently evidenced, instances when tripwire was active and we had an option to disable it, it counted days in our subscription. However, this doesn't nullify the part that they are shifting the blame for a potential banwave. It is the responsibility of the company (and in their best interest, market-wise) to protect us from a possible HB detection. Now, if a banwave regrettably happens, all they can say is "you botted with tripwire disabled". All we are asking for is their best shot at a safe bot. We know that at some point HB may be detected. Shifting the blame to customers, well now that's not good business practice. tl;dr Problem with botting with tripwire disabled is that it will eat up our days for an unfinished product and that it's an easy way out for the company if HB is detected
So, after a 2 month absence from WoW, I bought a legion subscription and will try Honorbuddy, again...However, whenever I start up the new patch 7.2.x version of WoW, in the upper left a message flashes each time saying that data files are being modified by Blizzard. Is this something new to detect bots? By the way, my sincere thanks to the Honorbuddy programmers and testers for all your hard work. Sometimes this forum gets dark and brutal, but your product is still the best out there... Update: Just tried to use honorbuddy, and it says that Tripwire is active. What do I do now? Update: Thank you, Raphus, for responding and answering my questions.
We have released a full version (not lite or whatsoever) under tripwire control because of the high demand. You are enforced to disable tripwire on your key to be able to use the bot. The days tripwire being active will be counted as down time while those days are being compensated in to keys. You are not losing anything with this decision. You are getting free usage of the bot if you are willing to risk more than usual.
