Found this in an error report...

[LargeInt]

So, right before the banwave yesterday I had setup VMware to pull the D3 folder through my host computer, instead of installing it on each VM as I was doing previously, and was using a stripped down version of windows on the boxes. I didn't have a firewall on the bots themselves, so I thought that was the only reason my crash reports went through (and I think those crash reports are contributing to bans, as the bots that I had banned had all crashed, and the ones that didn't get banned had not crashed). I immediately installed lightweight firewalls on each of my remaining bots, and blocked access to the blizzard error reporter.

Today, I just started thinking about how all of my DB stuff is now saved on my host PC, and it is nice to get all the logs in one place. I decided to go check the blizz error reports in my main host PC, and found that those crashes were reported there as well. Is it possible that the host PC was sending the error reports through the links? I do not remember setting a link between the inspector reporter and my VMs...

Anyway, here is what I found in the reports from before the bans. It was in each of the reports from the bots that crashed and were banned.

2012.12.13 04:06 SNOFileLoadTextFile: 'Data_D3\Locale\ruRU\declension.txt'
2012.12.13 04:06 SNOFileLoadTextFile: 'Data_D3\PC\Misc\banned_names.txt'
2012.12.13 04:06 SNOFileLoadTextFile: 'Data_D3\PC\Misc\enUS_banned_names.txt'

Ignore the times listed there. Those are the times within my VMs, and the VMs are running with a system time 12 hours ahead of actual time (just haven't fixed em). Also, I deleted part of the time, because it looked like it was down to a few digits in milliseconds, and I would rather not be identified if a Blizz employee was here with access to them...even if it is just connecting bot names to forum names.

I went back to previous reports from my main account that does NOT bot, and those lines were not found in any of them.

 

[jadox]

Hey not sure if you are onto something but i just posted 1/6 of my US accounts banned earlier.

Funnily enough the 1 account that did get banned was the one that would spit up an error report when d3 crashed or got dc'd. The others would just stay on login screen or just return to desktop screen. I dont use any reloggers.

My setup was 1 account on main and 5 vmware instances. Each instance has seperate copy of stripped down windows 7 32 bit and d3 installed.

How or where do i check that file?

 

[D3WallStreet]

How can I prevent my crashes to go into the "Error Folder"? I would like to know if there is a way to make it so everytime you crash it wont report it. Any help would be appreciated, always thought that was an easy way to get caught.

 

[LargeInt]

It is Diablo III\InspectorReporter\BlizzardError.exe

If it is a non-stripped version of Windows (at least Windows 7 has this option) you can go into your firewall settings and block the program. Just block its outgoing traffic. The error report will still show up when it crashes, but it will get blocked by your firewall when it tries to send it to Blizzard.

If it is a stripped down version of Windows without the firewall, or another version of Windows in which the firewall cannot block it for some reason, you can download COMODO Firewall. It isn't my favorite, but I found that it was the only free, decent firewall that worked with the version of Windows I was using. It requires you to do a bit of setup when it first comes online, or else it will block EVERYTHING (including D3 and Demonbuddy), but once you get that straight, you do the same thing as I explained about with the Windows Firewall.

You MUST have a firewall inside of EACH VM if you are doing VMs. They are going directly through your network connection, and are not subjected to your host computer's firewall.

If you were using the previous guide on linking your VMs to your host, without installing D3 or DB on the individual VMs, then you will want to firewall the file on your host machine as well (or if you bot on your host machine).

 

[D3WallStreet]

So I just went to my Windows 7 Firewall> Outbound Rules> New Rule> Program> %ProgramFiles% (x86)\Diablo III\InspectorReporter\BlizzardError.exe > Block Connection > Domain/Private/Public Blocked > Named it Fuck Off Blizzard. Will that do it? It will collect the reports but not send them correct?

 

[Dr.Spike]

wow ppl are paranoid.

This

[COLOR=#333333][/COLOR]2012.12.13 04:06 SNOFileLoadTextFile: 'Data_D3\PC\Misc\banned_names.txt'
2012.12.13 04:06 SNOFileLoadTextFile: 'Data_D3\PC\Misc\enUS_banned_names.txt'

Is just a list of names that are banned/cant be used on your characters, if you use any of the names in the list you will not be avaible to create your character,It wont allow you.
Now stop being so fucking paranoid

 

[D3WallStreet]

Then why do I have 13 folders of reports, 11 of them do not have the "Banned names" and that's when I didnt use to bot... The last 2 folders are from 12/11/2012 and 12/12/2012 (The week I started to bot) Seems like I got flagged already and probably will be gone next wave, who knows.

 

[Dr.Spike]

Then why do I have 13 folders of reports, 11 of them do not have the "Banned names" and that's when I didnt use to bot... The last 2 folders are from 12/11/2012 and 12/12/2012 (The week I started to bot) Seems like I got flagged already and probably will be gone next wave, who knows.

Or maybe, its because the last 2 folders are crash reports after the 1.0.5 build ?

So now, take off your and stop being paranoid

 

[CodenameG]

wow ppl are paranoid.

This

2012.12.13 04:06 SNOFileLoadTextFile: 'Data_D3\PC\Misc\banned_names.txt'
2012.12.13 04:06 SNOFileLoadTextFile: 'Data_D3\PC\Misc\enUS_banned_names.txt'

Is just a list of names that are banned/cant be used on your characters, if you use any of the names in the list you will not be avaible to create your character,It wont allow you.
Now stop being so fucking paranoid

^^This.

thread closed, ban section is for ban reports only.