What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Regarding Tripwire time window (21:05 UTC until 21:36 UTC)

S

samsmug

New Member
Joined
Feb 2, 2016
Messages
48
Reaction score
1
Here's what I was doing between 21:05 UTC to 21:36 UTC:


I had already been playing for a few hours but I was not botting at all. There's about a 3% chance I might have left DB on in the background but I never started the bot or used any tools in it. I did however have TurboHUD on and running from before 21:05 but I never initiated or turned it on again after 21:05 UTC.


So I'm not worried about DemonBuddy because I did not have it running at all during that time period, but I did have TurboHud running from before the Tripwire went into effect.


According to Raphus' post:

Status Update

The new warden scan is capable of detecting any program that is interfering with Diablo 3 and/or Hearthstone. We strongly
recommend not to use any Diablo 3 or Hearthstone tools until they are updated.

Accounts that logged in to Diablo 3 or Hearthstone after 09 Feb 2016 21:05 UTC until the tripwire event (21:37 UTC), and launched
Demonbuddy/Hearthbuddy within that time window might have been flagged by the new scan. We do not suspect accounts that were
already logged in before then to be flagged.

Summarising the above, we do not expect your account to be flagged if you:

were logged in to Diablo 3 or Hearthstone before 21:05 UTC
were logged in to Diablo 3 or Hearthstone after 21:05 UTC, but haven't launched Demonbuddy/Hearthbuddy until the tripwire event


Unfortunately, we still don't have any ETA for new releases and auths to be reopen.
Click to expand...


When he says, "We do not suspect accounts that were already logged in before then to be flagged." Does that mean that I could have been logged into D3 several hours before and still initiated TurboHUD within the tripwire window and be ok?


So basically you had to launch a new BNet/D3 AFTER the tripwire went into effect to be flagged for anything?



I know I sound like an idiot I'm just slightly unclear on the exact parameters involving being logged into the D3 before/after the Warden update.
 
Hi, Samsmug,

The 'window' Raphus gives if for Demonbuddy alone. All other tools were exposed the entire time.

There's really no point in getting hot-n-bothered over this. If you were caught, you were caught. Bliz may or may not take action. D3 isn't exactly an MMORPG with an economy you can put in jeopardy, so things may not be as dire.

cheers,
chinajade
 
chinajade said:
Hi, Samsmug,

The 'window' Raphus gives if for Demonbuddy alone. All other tools were exposed the entire time.

There's really no point in getting hot-n-bothered over this. If you were caught, you were caught. Bliz may or may not take action. D3 isn't exactly an MMORPG with an economy you can put in jeopardy, so things may not be as dire.

cheers,
chinajade
Click to expand...

So technically people that were already logged into D3 using DB before 21:05 UTC and kept running through that window were "safe" as well? Since they never launched a new BNet/D3 application? I'm assuming that in order for their new Warden scan to work the player would have to re-start their BNet or D3 application?

Unless they can "hotfix" a new Warden scan/version? Do we know if they can?
 
chinajade said:
Hi, Samsmug,

We cannot tell you whether or not you are 'safe'. Only Bliz knows.

No offense, but it sounds like you really shouldn't be botting if you are this worried about the event.

The articles also answers your question, by the way.

cheers,
chinajade
Click to expand...

Thanks for your quick responses. I am not really paranoid I was just interested in the time window that occurred and the parameters around how things were/will be detected from here on out.

Also I'm new to the service and just wasn't sure if this is an unprecedented event or not. Plus with Overwatch they could be beefing up security measures and technology due to it being a possible eSports venture

I couldn't go back to playing without DB and TH for that matter. I'm stayin, haha.
 
samsmug said:
Thanks for your quick responses. I am not really paranoid I was just interested in the time window that occurred and the parameters around how things were/will be detected from here on out.

Also I'm new to the service and just wasn't sure if this is an unprecedented event or not. Plus with Overwatch they could be beefing up security measures and technology due to it being a possible eSports venture

I couldn't go back to playing without DB and TH for that matter. I'm stayin, haha.
Click to expand...

Regarding if this is unprecedented or not, I can tell you that I cannot even remember seeing another tripwire event for D3, and I've been botting since RMAH times in vanilla.
Also, the last reported ban ever claimed on these forums were like august 2015, so there's that.

Like China said, this isn't WoW were you ruin the games for others (except top top TOP leaderboards) so doing a mass ban is not really in their best interest. Same with banning TurboHUD users.
If blizzard implemented some of the features fans have been screaming for, they wouldnt even have a problem with TurboHUD.

I would be thoroughly surprised if a "massive banwave" came of this.
 
I'm going to laugh my ass off if my bot account isn't getting banned and my legit account is. I was using TurboHUD when the 'tripwire' event happened and I was using it on the account I'm not botting on. I wasn't however botting on my botting account.
 
boater said:
I'm going to laugh my ass off if my bot account isn't getting banned and my legit account is. I was using TurboHUD when the 'tripwire' event happened and I was using it on the account I'm not botting on. I wasn't however botting on my botting account.
Click to expand...

Exactly the same situation for me.
 
If I was to get banned from this tripwire event, should I expect a permanent ban or how does it usually work in D3?
 
Gnrsrv1 said:
If I was to get banned from this tripwire event, should I expect a permanent ban or how does it usually work in D3?
Click to expand...

fooOoo said:
bans for botting in d3 are always perm bans
Click to expand...

joni1337 said:
i think d3 does always perm for botting/*****ing
Click to expand...

This may not be true any more. Blizzard said in a Blue post that i can not find ATM that if you Temp BAN some one there is a lower chance that they will Continue doing it.

If you Perma ban some one they have a high chance of saying FUCK IT and Starting over with in hours.

This is what they now do for at least First Offenders in WoW and have seen ^this to be true

But Wont know for sure until the ban-wave happens
 
Last edited:
SIL3NT-DE4TH said:
This may not be true any more. Blizzard said in a Blue post that i can not find ATM that if you Temp BAN some one there is a lower chance that they will Continue doing it.

If you Perma ban some one they have a high chance of saying FUCK IT and Starting over with in hours.

This is what they now do for at least First Offenders in WoW and have seen ^this to be true

But Wont know for sure until the ban-wave happens
Click to expand...

That's for WoW, not Diablo.

Diablo has always been Permanent bans.
 
Shylari said:
That's for WoW, not Diablo.

Diablo has always been Permanent bans.
Click to expand...

And it was the same for wow it use to always be permanently.

You nor I can say what there going to do with d3. We have to wait and see. I'm just say it's possible that they do 6 month since they might changed there philosophy about permanent ban
 
The only thing you can say for sure about Blizzard and the way they handle bans is that they are random at best.

Just because they used to be perma-bans, it doesn't mean that they won't changed their stance now.

Who's to say that they'll even ban any of us. We won't know anything until the bans start getting passed out, and if the way things have been managed in the past, it could be days or even weeks before we see bans.
 
ryftobuddy said:
The only thing you can say for sure about Blizzard and the way they handle bans is that they are random at best.

Just because they used to be perma-bans, it doesn't mean that they won't changed their stance now.

Who's to say that they'll even ban any of us. We won't know anything until the bans start getting passed out, and if the way things have been managed in the past, it could be days or even weeks before we see bans.
Click to expand...

Agreed
 
ryftobuddy said:
The only thing you can say for sure about Blizzard and the way they handle bans is that they are random at best.

Just because they used to be perma-bans, it doesn't mean that they won't changed their stance now.

Who's to say that they'll even ban any of us. We won't know anything until the bans start getting passed out, and if the way things have been managed in the past, it could be days or even weeks before we see bans.
Click to expand...

Why are people starting to think bans are incoming? Just because of the tripwire?

I thought there have been tripwires in the past and ppl have botted through it every day for years with no ban
 
Because the battle.net forums and reddit were going crazy about the warden changes. Saying that it means blizzard is about to do a giant banwave. Funny thing is how would they know that blizzard made changes to their warden and a bot shut down without actively participating in this forum.
 
Yea but the DemonBuddy guys stopped their old build with the tripwire and made another one that I assume makes it no longer detectable? They said the new one is "just as safe as before". With no one ever really being detected and banned in the past, wouldn't that mean no one should be afraid to bot again?
 
when you sign in and start botting you assume that you can be banned in any minute, no matter if its a tripwire event or not.

don't tell me that blizzard didn't banned d3 bots for long time and that's the reason why you sign in and start botting.
 
You must log in or register to reply here.
Back
Top