How to see if blizzard got your account flagged

[Mistz]

Hi guys, a friend and i tried doing some testing, on how to see if your flagged for botting, or any other kind of cheat.

So we got around 25 diablo games, that we bot with, mostly useing IB, 4 of them we use to test diffrent exploits and hacks, " accs that can be sparred to be lost " one day we ran into something funny, and decidet to keep a watch on it.

on 2 of our accs, we saw when we went to our diablo folder, it said in our log cheat was enabled, at first we laught a bit at it, but after sometime we got to find those 2 accs banned,

they both had the cheat enabled stated in the document of our lunch profile, unlike all our regular bots running with IB, it says cheat disabled, we have a theory this can be a warning to detect if your flagged, but then again it could had been pure luck, it was those 2 accs where it said cheat enabled that got banned, just very unlikely since the others was safe.

but here is how we found it.

- how to check -

1: go to your D3 folder, find the text document called " D3Debug.text " if you open this file, and look around 4th line, it should say cheat disabled, or cheat enabled.

as said the 2 accs we had showing cheat enabled has been banned, but the remaining accs where it says cheat disabled are still running mostly 15-20 hours a day.

[yellowspark]

2012.07.01 (nothingtosee) Cheats: DISABLED
Sup
But doesnt that mean we can change it to read only and it will forever be DISABLED so it will upload the log as DISABLED lol?

[travis2861]

Unless this is just a reflection of information stored on blizzards servers

Sent from my HTC One X using Tapatalk 2

[haitianboy420]

2012.06.30 19:14:25.278950700 Cheats: DISABLED

well this seems very promising but i do not believe it can be accurate.
with your theory it looks like it flags your client and not your account which is not what blizzard does. (at least to my knowledge)

suppose for a second you have 2 accounts. 1 PC. NO Virtual machines. and you play both accounts separately.

ACCT 1. Your MaIN.
ACCT 2. you bots.

so you are on acct 2 over night while you sleep. and you get flaged and it says ENABLED...
the next day you log off the bot and turn on the acct 1. you main..

with your theory. both accts get banned because it flaged your client? even though u never violated anything with acct 1.

2012.07.01 (nothingtosee) Cheats: DISABLED
Sup
But doesnt that mean we can change it to read only and it will forever be DISABLED so it will upload the log as DISABLED lol?

that wont work..
remember when you login and accept TOS & EULA you accept that blizz can look at your files and contents of your pc etc..
with that said seeing how that file is in there folder and the game request it to read/write. your diablo III.exe can overwrite it and make it read/write an dchange it back everytime u make it read only

[Mistz]

well we got a diablo folder for each game client, so can only tell what happend to us, hopeing it could help you guys, cause incase you do find it to be "cheat: enabled" its about time to figure out how to change that status rapidlly

this is only a guide line, i advice you check it once pr day, as said it takes what? less then 1 minute, and incase it says enabled, leave the char on standby till patch or something

[snwy]

makes sense
thanks for the advice

[naniqs]

I see looool

But i dont think that you will be able to change it to DISABLED and dont get banned:P, cause as Haitianboy says its on your client not your account it says it

[warzonebg]

Maybe some of the hacks u used change that?

[sunshoes]

np feel free to rep, if you can find a way to twist this in feathure.

Asking for rep is against the rules on Ownedcore.

The biggest issue with this, as was stated above, is that your D3Debug.txt is for your client, not your account.

[who knows]

I don't even have this file in either my d3 docs folder or my installation folder, can someone say the full pathname of where they found theirs?

[naniqs]

I don't even have this file in either my d3 docs folder or my installation folder, can someone say the full pathname of where they found theirs?

mine is called this:
D:\Diablo III..... and here i can find the D3Debug.txt

[who knows]

mine is called this:
D:\Diablo III..... and here i can find the D3Debug.txt

Strange I guess I didn't have one, I launched the client and a new one was recreated with a timestamp of a few minutes ago.

Edit:
Oh wow the debug file lists your account names, and your accounts unique database ID. Also interesting:

attributes=min_players={ int: 2 }|PlayerGroup={ int: 1 }|num_teams={ int: 1 }|Game.CurrentQuest={ none: (NONE) }|version={ string: "1.0.3" }|DifficultyLevel={ int: 3 }|max_players={ int: 4 }|

Looks like theres support for more/less max_player counts. Hmmmm?

LOL:

Initializing client world trOUT_Town...

Apparently theres also server checks on the MPQ datafiles. I'd suggest not model swapping or editing:

OpenMpq - opening update mpq success: Data_D3\PC\MPQs\base\d3-update-base-10235.MPQ size=3649 local=3649

[Feldeath]

Well seems possible, if they have their 25 game on 25 diff accounts it is completely possible.
If they had all their game on the same account, they would be all ban I suppose.

Anyway, thanks for sharing mate!

[naniqs]

Strange I guess I didn't have one, I launched the client and a new one was recreated with a timestamp of a few minutes ago.

Yeah i was in Diablo the time i found it maybe it automatic make a new one idk :S

[Beaving]

The logfile has nothing to do with Blizzard flagging you or detection of cheats. They could've added a clientside check for programs like Cheat Engine as they did in SC2, but that's just clientside and will just tell you to restart the game without the program.