What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal
RebornBuddy Forums

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Status
Not open for further replies.
I've got to say, this is genuinely hard to believe for anyone with experience in this domain. I don't think most people will appreciate what a staggering level of incompetence is required for a mission critical service to be down for a month without anyone realising. Look I know mistakes happen, but there are so many technologies out there for making sure services are up and running and doing their job, the fact you had to trawl through the server logs to determine if something as important as the tripwire was working is simply bewildering. I suspect my post will be deleted or reported as spam but I really hope you think long and hard about how this could have happened and how to avoid a repeat mistake. For most companies this would be game over.

agree with this
 
Click to move, 32 bit, only using cr, only using this, only using that... doesnt matter jack squat....... im no expert but with common sense, i can safely say there has been some kind of detection of some kind.

i installed HB only 3 days ago, and botted the last 2 days... i have NEVER used a bot before on wow in my life..

I have said this on some threads...and the reason i know they have figured out some way to detect HB. for all we know, they could have been able to detect HB for a looong time, the fact that they detected me in just 2 days, clearly favors the latter, they prolly detected me the second i attached HB to my wow for the first time.

To me that says that they havent been monitoring paths that the bot might take... or click to move, or whatever profile u have been using...
They have clearly had a scan of some sort running maybe once a week, once a day.. who the fuck knows, for some while. that can detect if u have HB injecting code or even just running on your computer

Also
The only reason they dont ban every week is because they want the subs, they want every penny they can get from ur botted accounts, before they ban the shit outta u
also this keeps HB devs in the dark as to what way they got you
 
@ raph and chinajade,
no promises but possible test release that is unsafe may be out this weekend by any chance?
 
I've got to say, this is genuinely hard to believe for anyone with experience in this domain. I don't think most people will appreciate what a staggering level of incompetence is required for a mission critical service to be down for a month without anyone realising. Look I know mistakes happen, but there are so many technologies out there for making sure services are up and running and doing their job, the fact you had to trawl through the server logs to determine if something as important as the tripwire was working is simply bewildering. I suspect my post will be deleted or reported as spam but I really hope you think long and hard about how this could have happened and how to avoid a repeat mistake. For most companies this would be game over.

The service was up and running. The issue was a part of the service not functioning properly due to a misconfiguration of an offset.
 
Dude you guys do your stuff you don't need to explain any more just make sure you guys come back stronger
 

Even a small-time one-man business should have monitoring set up for critical services, in any professional environment it is arranged so that if something goes wrong or goes down more alarms go off than if there was an incoming nuclear strike.

The service was up and running. The issue was a part of the service not functioning properly due to a misconfiguration of an offset.

Thanks for the clarification. It makes me wonder how the system is configured though if you can have such a large single point of failure.
 
Last edited:
I have been a software developer for nearly three decades now and shit like this just happens. And yes, I didn't want to lose my main account for another 18 months. It even hinders my development as re-leveling does take time. But I don't complain and I have not yet decided to move on to greener pastures, because I don't see any. :-P

Let's just hope that this loophole really is what caused the banwave. If anything different is the reason for the detection, then we are in a deep hole so it is actually good news they found something that could be fixed and that could be the reason. Time to start

Have you ever worked in a major company? Shit like this like this does not just happen. Even a small-time one-man business should have monitoring set up for critical services, in any professional environment it is arranged so that if something goes wrong or goes down more alarms go off than if there was an incoming nuclear strike. They should be truly embarrassed and ashamed to make this admission. You would expect it from some amateur bot company but not HB who have some of the most respected developers in the business. It's no surprise to see a bunch of lapdogs eager to let them off the hook without any criticism, but I feel someone has to point out the obvious. As I said, for most companies this would be game over, and there should really be no coming back from a failing like this. But I also appreciate they have a difficult job and many external influences to contend with, still, I hope this acts as a wake-up call.

Dude shut up
 
So this time there was something wrong with Tripwire. What exactly was wrong with Tripwire when the first banwave in May took place? Sorry, as much as I appreciate your work, I can't believe that whole Tripwire thing anymore, and I'm absolutely convinced by now that Tripwire won't do anything when the next Banwave will happen. And it probably won't take long until it will happen, I think most of us are aware of that.

In anticipation of the kiddos screaming out of their basements: No, I'm not crying because my accounts are gone, I'm doing this whole bot-ban-bot-ban thing for quite a while now but this is clearly not my point here. My point is that I'm having trouble believing in Tripwire anymore.
 
Thank you guys for your understanding and work.
Just a heads up, I havent ran the bot in quiet sometime on my botting account and it was banned. Blizzard is going through out PC with some other program and watching, there is no other way. They are doing something outside their EULA. Our privacy is being violated.

Good Luck and fairwell fellow botters and Dev team!
 
My main account was hit with a 6 month suspension on this banwave. However I echo whats been said here previously about the candor of your message and appreciate it. Thanks.
 
Mhhh, just my 2 cents:
I dont believe this statement. The history repeats in a fancy way. The whole statement doesnt make any sence, sure fanboy out there will tell me i do a shiat but hey the staff trust in a "fixed" tripwire, i dont even believe it was "broken".

Blizzard just outplayed you another time and you try to cover your own product behind a security mistake - sorry but this cant be true.

I would be fine if you would tell us the truth. But i dont expect one ;-)

Well you got 6 months to do something - the next banwave will come for sure aswell :X
 
Last edited:
I think it's been detected, i've not used HB for over 2 years on my account, I started using it about a week ago, I had Enyo and bought one of the Gladiator routines for £15, banned within a day, i'm no expert but it just seems to be too widespread to be a mistake on your end, 2 mass bans within the space of a year from what i've read, seems to me whoever even attempted to open it got banned, also how will it ever be determined fit for use again? I honestly think the main issue here is that you have to run in 32-bit and the click to move thing that people have already posted, for one of the most popular botting programs out there it seems to be awfully outdated
 
Thank you guys for your understanding and work.
Just a heads up, I havent ran the bot in quiet sometime on my botting account and it was banned. Blizzard is going through out PC with some other program and watching, there is no other way. They are doing something outside their EULA. Our privacy is being violated.

Good Luck and fairwell fellow botters and Dev team!

Nope, Blizzard has built a "on demand RFC" routine in the WoW system and will only "see" you when you're active with HB and only when they activate the scan.
The fact that you have not been running HB "for quite some time", doesn't mean a thing - Blizzard could have run the scan a long time ago and they tend to collect the "suspects" and ban you in the next banwave.
 
I think it's been detected, i've not used HB for over 2 years on my account, I started using it about a week ago, I had Enyo and bought one of the Gladiator routines for £15, banned within a day, i'm no expert but it just seems to be too widespread to be a mistake on your end, 2 mass bans within the space of a year from what i've read, seems to me whoever even attempted to open it got banned, also how will it ever be determined fit for use again? I honestly think the main issue here is that you have to run in 32-bit and the click to move thing that people have already posted, for one of the most popular botting programs out there it seems to be awfully outdated
Dude trust me they're gonna come back stronger have faith in them. They won't let us down just don't bot on your main
 
one of my accounts was not botted on for almost 2 mos and still got caught in the ban wave. and it was not an IP wide suspension as I have 2 others that are not used for botting that are fine
 
We do NOT know for sure what caused the banwave, but we strongly believe the tripwire
service would have been able to catch the detection that took place if it was working
properly.

i really really really dislike reading that, come on, if u cannot figure out how they detect you, its impossible to prevent the detection

i do not believe in tripwire, i believe in good software ....
 
Status
Not open for further replies.
Back
Top