[Tripwire Spam Thread]: Discussion Thread for 20160219 Tripwire event

[Johnson8270]

If it would be up to God he would ban you not bless your heroes.

Thank god for Crusader Invoker build.. great for HC

 

[interloper]

thanks ;D

No problem. I have not been a demonbuddy customer for very long, but the dev's have been insanely quick to have information shared, and new versions released.

 

[tona91]

I didn't run the bot like 2 days before the 1st event and also didn't run it since then so maybe i will stay safe who knows.

 

[Jowzito]

for my fellow botters...a wise master once said...

 

[interloper]

Were any demonbuddy users banned in the chinese server banwave? Would be a good indication on what we should expect if the US servers see it as well.

Don't speak/read chinese so finding the info for me is rough

 

[Lokeboy]

Were any demonbuddy users banned in the chinese server banwave? Would be a good indication on what we should expect if the US servers see it as well.

Don't speak/read chinese so finding the info for me is rough

Yes, it's already been discussed here. Both temp and perma bans were handed out.

 

[musatolvkor]

Were any demonbuddy users banned in the chinese server banwave? Would be a good indication on what we should expect if the US servers see it as well.

Don't speak/read chinese so finding the info for me is rough

I used google translate, do it aswell bro

 

[interloper]

Yes, it's already been discussed here. Both temp and perma bans were handed out.

To demonbuddy users? Ros-bot users? some other bot's users? What?

 

[Jowzito]

Status Update

Blizzard seems to be going aggressive with their spyware attempts. The new warden update is able to detect a wider range of
applications that interacts with Diablo 3 and Hearthstone which includes Demonbuddy and Hearthbuddy.

We have about a 15 minute time window from around 19 Feb 02:08 UTC to 19 Feb 02:23 UTC for our users that logging in to the
game and started Demonbuddy/Hearthbuddy to have their accounts flagged. You should be safe if you logged in to Diablo 3 or
Hearthstone before 02:08 UTC or launched the bot after 02:23 UTC.

We are working on new builds and have no ETA as of now.


Sooo....gg for me ....i've launched the bot and client +- 7min before tripwire gg....

 

[interloper]

Status Update

Blizzard seems to be going aggressive with their spyware attempts. The new warden update is able to detect a wider range of
applications that interacts with Diablo 3 and Hearthstone which includes Demonbuddy and Hearthbuddy.

We have about a 15 minute time window from around 19 Feb 02:08 UTC to 19 Feb 02:23 UTC for our users that logging in to the
game and started Demonbuddy/Hearthbuddy to have their accounts flagged. You should be safe if you logged in to Diablo 3 or
Hearthstone before 02:08 UTC or launched the bot after 02:23 UTC.

We are working on new builds and have no ETA as of now.


Sooo....gg for me ....i've launched the bot and client +- 7min before tripwire gg....

Ironically, I had the bot launched and running about 30minutes before at 1:40UTC, it ran until tripwire shut it down..........Then at 02:26 I re-opened the bot/d3 as I was AFK when it shut down, and I re-opened wondering what was going on, it of course shut down instantly at that time.

Apparently I think that means I may not be screwed? Or since it was running during that time frame, am I screwed?

 

[kozakius]

I was botting,
I am botting,
I am going to bot.

No matter which game, no matter why - just as always - do it for fun!

 

[samsmug]

Ironically, I had the bot launched and running about 30minutes before at 1:40UTC, it ran until tripwire shut it down..........Then at 02:26 I re-opened the bot/d3 as I was AFK when it shut down, and I re-opened wondering what was going on, it of course shut down instantly at that time.

Apparently I think that means I may not be screwed? Or since it was running during that time frame, am I screwed?

I'm pretty sure you're safe. Even though you re-opened you technically never connected since the tripwire prevented you from doing so

 

[brendalwolf]

I had not started a diablo 3 session yet, I was just on the start screen, When I opened demonbuddy the first thing was tripwire. no game was even played.i just shut down the bot and started playing normally. since no game had been played by me running the bot. and the bot never logged into a new session, is there a chance that it would be caught by warden?

 

[chinajade]

Apparently I think that means I may not be screwed? Or since it was running during that time frame, am I screwed?

is there a chance that it would be caught by warden?

Requests for this kind of analysis indicate too much concern for your account, and you should probably not be botting. This article provides more insight to the topic:

BosslandGmbH:HelpDesk:Is Botting Safe?​

If you were caught, you were caught. There is really no point in getting twisted up over the event, as there is nothing you can do to affect the outcome. Diablo 3 is mostly a single-player game nowadays. Even if you were caught, there is considerable chance that Bliz will not take action because single-player games don't affect others. But conversely, Bliz may try a 'money grab' to get botters to re-purchase their products. This would probably be a mistake on their part, as many won't return.

I was botting,
I am botting,
I am going to bot.

No matter which game, no matter why - just as always - do it for fun!

If you want to bot, ^this^ should be your mindset.
Indeed, BotTV is fun!

cheers,
chinajade

 

[lawlumad88]

I was botting,
I am botting,
I am going to bot.

No matter which game, no matter why - just as always - do it for fun!

thats the spirit. Im just waiting for bot to be back up!
yolo

 

[Booger]

I'm curious if I got caught. I was in that time frame but I was getting max sessions. Below is my log from 3 different text files:

2016-02-19 02:05:42,905 [1] INFO MainWindow (null) - Demonbuddy v1.1.2923.454 started
2016-02-19 02:06:05,736 [1] INFO MainWindow (null) - Logging in...
2016-02-19 02:06:05,823 [7] DEBUG MainWindow (null) - Logging in to BestLatency (192.99.20.72)
2016-02-19 02:06:06,034 [7] INFO MainWindow (null) -
Max Sessions
2016-02-19 02:06:06,138 [1] INFO MainWindow (null) - Will try to login again in 30 seconds.
2016-02-19 02:06:33,869 [1] DEBUG BotMain (null) - Cannot stop a bot when it is not running.
2016-02-19 02:06:33,871 [1] DEBUG MainWindow (null) - Forcing all open windows to close.

--------------------------------------------------------------------------------------------------------------------------------------------------

2016-02-19 02:07:35,372 [1] INFO MainWindow (null) - Demonbuddy v1.1.2923.454 started
2016-02-19 02:07:37,466 [1] INFO MainWindow (null) - Logging in...
2016-02-19 02:07:37,558 [4] DEBUG MainWindow (null) - Logging in to BestLatency (192.99.20.72)
2016-02-19 02:07:37,774 [4] INFO MainWindow (null) -
Max Sessions
2016-02-19 02:07:37,884 [1] INFO MainWindow (null) - Will try to login again in 30 seconds.
2016-02-19 02:08:07,885 [1] INFO MainWindow (null) - Logging in...
2016-02-19 02:08:07,952 [10] DEBUG MainWindow (null) - Logging in to BestLatency (192.99.20.72)
2016-02-19 02:08:08,140 [10] INFO MainWindow (null) -
Max Sessions
2016-02-19 02:08:08,248 [1] INFO MainWindow (null) - Will try to login again in 30 seconds.
2016-02-19 02:08:38,258 [1] INFO MainWindow (null) - Logging in...
2016-02-19 02:08:38,323 [14] DEBUG MainWindow (null) - Logging in to BestLatency (192.99.20.72)
2016-02-19 02:08:38,495 [14] INFO MainWindow (null) -
Max Sessions
2016-02-19 02:08:38,601 [1] INFO MainWindow (null) - Will try to login again in 30 seconds.
2016-02-19 02:09:08,617 [1] INFO MainWindow (null) - Logging in...
2016-02-19 02:09:08,675 [18] DEBUG MainWindow (null) - Logging in to BestLatency (192.99.20.72)
2016-02-19 02:09:08,837 [18] INFO MainWindow (null) -
Max Sessions
2016-02-19 02:09:08,960 [1] INFO MainWindow (null) - Will try to login again in 30 seconds.
2016-02-19 02:09:38,978 [1] INFO MainWindow (null) - Logging in...
2016-02-19 02:09:39,044 [15] DEBUG MainWindow (null) - Logging in to BestLatency (192.99.20.72)
2016-02-19 02:09:39,213 [15] INFO MainWindow (null) -
Max Sessions
2016-02-19 02:09:39,316 [1] INFO MainWindow (null) - Will try to login again in 30 seconds.
2016-02-19 02:10:09,317 [1] INFO MainWindow (null) - Logging in...
2016-02-19 02:10:09,375 [11] DEBUG MainWindow (null) - Logging in to BestLatency (192.99.20.72)
2016-02-19 02:10:09,541 [11] INFO MainWindow (null) -
Max Sessions
2016-02-19 02:10:09,639 [1] INFO MainWindow (null) - Will try to login again in 30 seconds.
2016-02-19 02:10:39,643 [1] INFO MainWindow (null) - Logging in...
2016-02-19 02:10:39,715 [21] DEBUG MainWindow (null) - Logging in to BestLatency (192.99.20.72)
2016-02-19 02:10:39,875 [21] INFO MainWindow (null) -
Max Sessions
2016-02-19 02:10:39,965 [1] INFO MainWindow (null) - Will try to login again in 30 seconds.
2016-02-19 02:10:42,071 [1] DEBUG BotMain (null) - Cannot stop a bot when it is not running.
2016-02-19 02:10:42,072 [1] DEBUG MainWindow (null) - Forcing all open windows to close.

--------------------------------------------------------------------------------------------------------------------------------------------------


2016-02-19 02:16:17,016 [1] INFO MainWindow (null) - Demonbuddy v1.1.2923.454 started
2016-02-19 02:23:25,976 [1] INFO MainWindow (null) - Logging in...
2016-02-19 02:23:26,053 [3] DEBUG MainWindow (null) - Logging in to BestLatency (192.99.20.72)
2016-02-19 02:23:26,245 [3] INFO MainWindow (null) - TRIPWIRE
2016-02-19 02:23:26,304 [4] WARN MainWindow (null) - Tripwire Active, shutting down Demonbuddy!
2016-02-19 02:23:26,346 [1] INFO MainWindow (null) - Authentication failed.
TRIPWIRE

2016-02-19 02:23:31,307 [1] DEBUG BotMain (null) - Cannot stop a bot when it is not running.
2016-02-19 02:23:31,309 [1] DEBUG MainWindow (null) - Forcing all open windows to close.
2016-02-19 02:23:31,310 [1] DEBUG MainWindow (null) - Closing window: Demonbuddy Login

 

[chinajade]

I'm curious if I got caught. I was in that time frame but I was getting max sessions. Below is my log from 3 different text files:

Hi, Booger,

The answer to this is "you should probably not be botting". More info in this post.

cheers,
chinajade

 

[interloper]

Requests for this kind of analysis indicate too much concern for your account, and you should probably not be botting. This article provides more insight to the topic:

BosslandGmbH:HelpDesk:Is Botting Safe?​

If you were caught, you were caught. There is really no point in getting twisted up over the event, as there is nothing you can do to affect the outcome. Diablo 3 is mostly a single-player game nowadays. Even if you were caught, there is considerable chance that Bliz will not take action because single-player games don't affect others. But conversely, Bliz may try a 'money grab' to get botters to re-purchase their products. This would probably be a mistake on their part, as many won't return.



If you want to bot, ^this^ should be your mindset.
Indeed, BotTV is fun!

cheers,
chinajade

Thats ridiculous. It's like speeding down the road. Do you just not care if you get a ticket, or do you use a little common sense, think about things, and take steps to avoid getting the ticket?

Not sure about you, but I try to avoid the tickets.

Analyzing something to see where you stand on a situation is not too much concern, it's just simple mathematics and a thought process.

If I end up banned, there will be no freak out, I can assure you

 

[Booger]

Hi, Booger,

The answer to this is "you should not be botting". More info in this post.

cheers,
chinajade

You misunderstand. I don't care if I was caught. I was just curious since the max sessions may have made it so warden didn't pick it up.

 

[brendalwolf]

Requests for this kind of analysis indicate too much concern for your account, and you should probably not be botting. This article provides more insight to the topic:

BosslandGmbH:HelpDesk:Is Botting Safe?​

If you were caught, you were caught. There is really no point in getting twisted up over the event, as there is nothing you can do to affect the outcome. Diablo 3 is mostly a single-player game nowadays. Even if you were caught, there is considerable chance that Bliz will not take action because single-player games don't affect others. But conversely, Bliz may try a 'money grab' to get botters to re-purchase their products. This would probably be a mistake on their part, as many won't return.



If you want to bot, ^this^ should be your mindset.
Indeed, BotTV is fun!

cheers,
chinajade

Actually what I was getting at is when trip wire kicks in is the bot already loaded or does it stop before it interfaces with game? don't care if I get caught, I'm seein how trip wire works.