Inevitable discussion thread for Tripwire event on 30-Jun-2016

[f299]

Because I posted a snippet, as he did, imbecile.

To fend of the masses of illiterate people.

Quite amazing how stupid you people really are!

Log attached

>Calls people an imbecile
>Calls people stupid
>Can't even post the log where he stated he was on for 20 minutes past tripewire
>Bad troll is Bad

 

[kravitz]

>Calls people an imbecile
>Calls people stupid
>Can't even post the log where he stated he was on for 20 minutes past tripewire
>Bad troll is Bad

AND when and where had I stated "was on for 20 minutes past tripwire" ?!

You are clearly a troll.

You're right, you can't fix stupid.

Because you can't even back up your own claims and instead resort to name calling and just being a complete ass. So good job on you, buddy.

It's not my fault that you cannot read.

 

[ryftobuddy]

Because I posted a snippet, as he did, imbecile.

To fend of the masses of illiterate people.

Quite amazing how stupid you people really are!

You really, really, REALLY need to stop insulting people. Everyone here reading this thread can see how you are wrong and YOU in fact are the person that can't read or understand what happened when the tripwire activated.

So since you think your log is pertinent, why did you have to restart the bot when you did? Was it because you were kicked off of wow and your HB session when tripwire activated? Sure seems pretty logical to me.

BotOperator already backed up exactly what I've been saying this whole time. Yes, every user that was on when tripwire activated was booted from wow (unless you are using a pirated copy of the bot...Are you?).

I'm sorry both you and Tony are wrong here. I'm sorry you're the only person that can see that. Go ahead and continue thinking you're right here. I can assure you that you are the only person that feels that way right now.

 

[f299]

AND when and where had I stated "was on for 20 minutes past tripwire" ?!

You are clearly a troll.



It's not my fault that you cannot read.

My apologies. You stated that you were on still past tripwire though, still, not seeing a log. You claimed that you weren't able to keep a connection due to the sid error, yet, the log you provided still doesn't show that. It shows that tripwire is activated and that it shut down honorbuddy.

It's not my fault you can't back up your claims.

GG Buddy.

 

[kravitz]

My apologies. You stated that you were on still past tripwire though, still, not seeing a log. You claimed that you weren't able to keep a connection due to the sid error, yet, the log you provided still doesn't show that. It shows that tripwire is activated and that it shut down honorbuddy.

It's not my fault you can't back up your claims.

GG Buddy.

Quote my post... where did I claim that I stated I was still on past tripwire WHILE HB was running? Amazing... goes above your head.

If anyone agrees with either of you, they've proven to be just as foolish and stupid as both of you. Learn to read, then perhaps there wouldn't be an issue.

I hadn't lost my account, just annoyed by people like yourselves who clearly fail at reading and COMPREHENSION. My biggest pet peeve!

 

[f299]

Interesting to note and reiteration, I had a WOW account still online and never kicked or logged off when the sid error displayed. The only issue I had is HB wasn't able to stay online, since there was obviously an AUTH issue. So, I posted the issue within support, then went back to the arena in WOW. Then 20+ minutes later peons screaming Tripwire, sad to say I was STILL online in the arena, was HB active on my end? No, because of the issue with the sid server network issue disallowing a connection. So, does that mean every single user who in fact were affected by the sid server network issue were kicked or forced log-off from WOW via Tripwire activating? Absolutely not.

I have NEVER experienced a tripwire where my account was not turned off. It logs you off. So you are claiming that you had honorbuddy on, it would go on, but would lose connection, but you were never disconnected? Really? Are you sure? Again, log. You have YET to provide the right log, and your claims are pathetic just like you have to resort to name calling and childish behavior.

 

[Arellano]

Doest time that hb is off still counts to days I have for example taken a profile from store as trial?

 

[ryftobuddy]

Doest time that hb is off still counts to days I have for example taken a profile from store as trial?

The HB team is generally good about crediting accounts with extra time for bot downtime.

 

[ryftobuddy]

Reported.

Some sad individuals here. Show some patience and gratitude that the tripwire just saved your ass

Tripwire hasn't saved anyone yet, nor are they sure if it did save us. Go back and read what Raphus wrote:

"However, there is a possibility of a small time window where accounts that have logged in to the game before the event might get flagged."

We may not know anything for weeks.

 

[Itsonono]

You really need to stop talking about the tripwire like you know what you're talking about....

Yes, in fact, every user that had HB running at the time the event occurred was kicked and logged off from wow.

Could that be used as evidence? Probably not. Any given second during wow's peak time, there's probably hundreds of people logging in and out of the game. It would create too many false positives to simply use that...But at the same time, it could be used to gather accounts for review.

I wasn't kicked out of game. I was observing my screen the whole time, and saw the second HB went down. HB just closed and that was it.

 

[raphus]

Tripwire hasn't saved anyone yet, nor are they sure if it did save us. Go back and read what Raphus wrote:

"However, there is a possibility of a small time window where accounts that have logged in to the game before the event might get flagged."

We may not know anything for weeks.

I remember you saying this same thing for the tripwire event on 8th of June as well. And the result is obvious, Blizzard trying again to detect us instead of doing a mini banwave.

Even if there is a really small chance for some accounts to get flagged, we have to announce that. The chance of no accounts being flagged is lots more higher which is not mentioned at all in our announcements.

Please, stop picking up only the negative parts of the things.

 

[UnderratedPost]

Tripwire hasn't saved anyone yet, nor are they sure if it did save us. Go back and read what Raphus wrote:

"However, there is a possibility of a small time window where accounts that have logged in to the game before the event might get flagged."

We may not know anything for weeks.

That's what you said last time if they are making new attempts to detect us then it's pretty obvious the last attempt was foiled by Tripwire! I just wish they would leave us alone FFS

Great job again buddy team!

 

[r0sc0]

I remember you saying this same thing for the tripwire event on 8th of June as well. And the result is obvious, Blizzard trying again to detect us instead of doing a mini banwave.

Even if there is a really small chance for some accounts to get flagged, we have to announce that. The chance of no accounts being flagged is lots more higher which is not mentioned at all in our announcements.

Please, stop picking up only the negative parts of the things.

Exactly, never been banned with HB been botting since it was released. great job lads! keep up the good work! raphus messaged you on skype.

 

[ryftobuddy]

I wasn't kicked out of game. I was observing my screen the whole time, and saw the second HB went down. HB just closed and that was it.

As BotOperator said, the only reason that wow wouldn't have closed is if you're using a pirated copy of the bot...

The HB team may want to look at your log to see if they can see any reason you wouldn't be disconnected. What you should really see is something similar to what I posted earlier in this thread in your logs.

 

[ryftobuddy]

I remember you saying this same thing for the tripwire event on 8th of June as well. And the result is obvious, Blizzard trying again to detect us instead of doing a mini banwave.

Even if there is a really small chance for some accounts to get flagged, we have to announce that. The chance of no accounts being flagged is lots more higher which is not mentioned at all in our announcements.

Please, stop picking up only the negative parts of the things.

And I'll continue to say it...Your staff has made it crystal clear throughout the years that Blizz does not immediately ban after a tripwire event. I mean seriously, there was months...literally MONTHS where the tripwire wasn't working at all (go ahead and look at when the second banwave occurred...Your excuse was that tripwire wasn't even functioning.) They could easily roll out a banwave in the next couple weeks from the previous tripwire event...And you won't even have a clue from where the banwave comes from.

You want me to stop being negative? Post some actual, real information instead of brushing everything off with your constant excuse about "we're protecting our users by not giving you any information". You don't have to mention anything about the potential for anything, you make that very clear every time anything bad happens.

 

[UnderratedPost]

And I'll continue to say it...Your staff has made it crystal clear throughout the years that Blizz does not immediately ban after a tripwire event. I mean seriously, there was months...literally MONTHS where the tripwire wasn't working at all

how is that relevant to when the tripwire IS working and it's literally been proven to work twice in the last month or so

 

[Sneeds44]

what wil you guys do if blizzards adds an automatic scanner for honorbuddy then you need to update the bot evryday that would be alot of work?

 

[raphus]

Post some actual, real information instead of brushing everything off with your constant excuse about "we're protecting our users by not giving you any information". You don't have to mention anything about the potential for anything, you make that very clear every time anything bad happens.

I guess you just can not understand the fact that any actual, real information we share on the forums is sharing it with Blizzard directly.

Sorry, but we will not be doing that.

 

[ryftobuddy]

how is that relevant to when the tripwire IS working and it's literally been proven to work twice in the last month or so

Once again, it hasn't been proven to work at all...The tripwire has failed several times times in the last years. Raphus will probably come back here and tell me I have no idea what I'm talking about...If your tripwire works so well, why has there been 3 major banwaves in the last 2 years? It's pretty obvious that tripwire does absolutely nothing if blizz can just bypass it whenever they want.

And again, Blizz never has, nor will they ever, act immediately on flagged accounts. Keep that in mind. Come back in another month or so, and then in another month after that, and if another banwave hasn't occurred then you can tell me "I told you so".

 

[Giwin]

Thanks for saving everyones accounts.