capncrunch
New Member
- Joined
- Dec 12, 2012
- Messages
- 6
- Reaction score
- 0
What makes you think Blizzard, a multi million dollar company, can't afford a key to access the forums? Think why don't you?
Ban Theories and Ban Waves
- Thread starter Hawker
- Start date
What makes you think Blizzard, a multi million dollar company, can't afford a key to access the forums? Think why don't you?
Insomniac212
New Member
- Joined
- Dec 21, 2011
- Messages
- 28
- Reaction score
- 0
Diablo III Players Banned for Botting, Battle.net Authenticators Temporarily Unavailable, Blue Posts, Heart of the Swarm Beta Key Giveaway - News - Diablo Discussion and Community Forums - DiabloFans.com
In my opion you SHOULD STOP SELLING DEMONBUDDY bot is clearly detectable.
In my opion you SHOULD STOP SELLING DEMONBUDDY bot is clearly detectable.
Last edited:
How does one justify if he/she is botting? I mean, I could play for 12 hours for weeks not saying that would be a good thing but its possible so I am just guessing I would eventually get a ban hammer dropped on my head?
While I'm not about to reveal how we identify exploitative behavior in Diablo III (and understandably so), "playing a lot" is not criteria enough to merit an account action for botting.
Continuing this conversation http://www.thebuddyforum.com/demonbuddy-forum/97280-weve-known-blizzard-3.html
Let's check this list together.
1. I agree, that if it was a special software to detect bot, the game would not started with bot on pc\started on. But we have several thousands of people banned in one day. I hope you agree, that they can't check manually everyone. Even of they had like 20-40 supporters on it. It is too much, even for prepared wave. So, they had used a marking system or something like that.
As example. I was working on several games (dunno you know em or not, but will try to explain). It's l2 and rf online. The bot mechanics in rf was like using special coordinates. Like +1000 on Y out of location. What we get from this - the bot would not get hited by mobs. But in logs all pickups and rest were on this coordinate. So, you just check, port on it and ban. Nice and easy.
On l2 bot was working same as hb\db. It was no special coordinates and gm tool sometimes found strange characters. But we didn't understood how in works and nc couldn't explain (yes, lol). So we were working on "eye". Hope you agree, that you can see see bot, who is moving on coordinates and legal character. I had 12 people on it and we could find only 30-50 bots\day.
2. I disagree with that, because achiev is good, but you have all info in game statystic (loot\mobs\bosses). It was before cata release.
3. Well, the main rule is fear. The louder people are screaming - the better wave was. (as example, several mounthes we didn't have any night-gms, but from time to time we did night raids to ban users after. It was really fun to read surprised posts in the morning).
But again, i am 70% shure, that they have changed their ban politics. I mean, that they were not active with banning single-bot users, but now even they are gone. And after this we should ask ourselves 2 questions.
1. Was it a single wave to make botters fear, to decrease overall paragon level, or it is a new poilics. I am pretty shure, that soon we will know about it - after people, who using bot only on main acc will start botting again. We need time for this.
2. How hard for Blizz anti-bot team to get the logs about illegal users again (mb they used some special info from DB servers with help of IT-department). And this was just a single event.
I'll be glad to hear some more theories about this wave, and what we can do.
p.s.
And don't forget, that Losing is fun (c) Dwarf fortress.
We must know, an easy rule, that the bot will be banned, always. Just depends on time, when it will happen.
Let's check this list together.
1. I agree, that if it was a special software to detect bot, the game would not started with bot on pc\started on. But we have several thousands of people banned in one day. I hope you agree, that they can't check manually everyone. Even of they had like 20-40 supporters on it. It is too much, even for prepared wave. So, they had used a marking system or something like that.
As example. I was working on several games (dunno you know em or not, but will try to explain). It's l2 and rf online. The bot mechanics in rf was like using special coordinates. Like +1000 on Y out of location. What we get from this - the bot would not get hited by mobs. But in logs all pickups and rest were on this coordinate. So, you just check, port on it and ban. Nice and easy.
On l2 bot was working same as hb\db. It was no special coordinates and gm tool sometimes found strange characters. But we didn't understood how in works and nc couldn't explain (yes, lol). So we were working on "eye". Hope you agree, that you can see see bot, who is moving on coordinates and legal character. I had 12 people on it and we could find only 30-50 bots\day.
2. I disagree with that, because achiev is good, but you have all info in game statystic (loot\mobs\bosses). It was before cata release.
3. Well, the main rule is fear. The louder people are screaming - the better wave was. (as example, several mounthes we didn't have any night-gms, but from time to time we did night raids to ban users after. It was really fun to read surprised posts in the morning).
But again, i am 70% shure, that they have changed their ban politics. I mean, that they were not active with banning single-bot users, but now even they are gone. And after this we should ask ourselves 2 questions.
1. Was it a single wave to make botters fear, to decrease overall paragon level, or it is a new poilics. I am pretty shure, that soon we will know about it - after people, who using bot only on main acc will start botting again. We need time for this.
2. How hard for Blizz anti-bot team to get the logs about illegal users again (mb they used some special info from DB servers with help of IT-department). And this was just a single event.
I'll be glad to hear some more theories about this wave, and what we can do.
p.s.
And don't forget, that Losing is fun (c) Dwarf fortress.
We must know, an easy rule, that the bot will be banned, always. Just depends on time, when it will happen.
Psychiatrist
New Member
- Joined
- Nov 27, 2012
- Messages
- 3
- Reaction score
- 0
Has anyone been banned after a wave? Bans stopped or not? (after 20.12.2012 ?)
For a moderator, if he/she wants/can to check this :
Make a list with all DB versions, 13300, 12480 etc and after that go in X:/Diablo III/Data_D3/PC/MPQs/Cache/enGB ..
I think that : In diablo 3 game (from our PC), there is some kind of "bot" that collect that from our PC and when blizzard wants to take them, they will take them when they make a new UPDATE ..
edit
id someone get ban and didn't play with bot after last update from blizzard?
Make a list with all DB versions, 13300, 12480 etc and after that go in X:/Diablo III/Data_D3/PC/MPQs/Cache/enGB ..
I think that : In diablo 3 game (from our PC), there is some kind of "bot" that collect that from our PC and when blizzard wants to take them, they will take them when they make a new UPDATE ..
edit
id someone get ban and didn't play with bot after last update from blizzard?
Last edited:
Mammon
New Member
- Joined
- Jun 16, 2012
- Messages
- 413
- Reaction score
- 0
This is how my errorreports looks like. As you can see they clearly submit whole memory.
<Inspector.ProjectId:>
36
<:Inspector.ProjectId>
<Executable:>
Diablo III
<:Executable>
<Inspector.Module:>
Diablo III
<:Inspector.Module>
<Inspector.BuildNumber:>
13644
<:Inspector.BuildNumber>
<Inspector.Platform:>
All Win
<:Inspector.Platform>
<Inspector.IssueType:>
Exception
<:Inspector.IssueType>
<Version:>
1.0.6.13644 (63005-790766)
<:Version>
<Inspector.Priority:>
1 - Critical
<:Inspector.Priority>
<Inspector.Language:>
enGB
<:Inspector.Language>
<Inspector.Branch:>
1_0_6
<:Inspector.Branch>
<Inspector.HashBlock:>
DBG-OPTIONS<FunctionsOnly>
DBG-ADDR<00a429e6>("Diablo III.exe")
DBG-ADDR<00ce2fd0>("Diablo III.exe")
DBG-ADDR<00865853>("Diablo III.exe")
DBG-ADDR<008d1816>("Diablo III.exe")
DBG-ADDR<008d20e0>("Diablo III.exe")
DBG-ADDR<00dc6781>("Diablo III.exe")
DBG-ADDR<0080dfa4>("Diablo III.exe")
DBG-OPTIONS<>
<:Inspector.HashBlock>
<Inspector.PrimaryAssignment:>
.Programmers
<:Inspector.PrimaryAssignment>
<Inspector.Summary:>
***** UNHANDLED EXCEPTION: ACCESS_VIOLATION (c0000005)
<:Inspector.Summary>
<Inspector.Assertion:>
***** UNHANDLED EXCEPTION: ACCESS_VIOLATION (c0000005)
------------
Stack Crawl:
------------
DBG-ADDR<00A429E6>("Diablo III.exe")
DBG-ADDR<00CE2FD0>("Diablo III.exe")
DBG-ADDR<00865853>("Diablo III.exe")
DBG-ADDR<008D1816>("Diablo III.exe")
DBG-ADDR<008D20E0>("Diablo III.exe")
DBG-ADDR<00DC6781>("Diablo III.exe")
DBG-ADDR<0080DFA4>("Diablo III.exe")
7 frames dumped
<:Inspector.Assertion>
<Inspector.DebugModules:>
------------------------------------------------------------------------------
----------------------------------------
Loaded Modules
----------------------------------------
DBG-MODULE<00540000 00149000 "icuin49.dll" "" 0 {00000000-0000-0000-0000000000000000} 0 1333660131>
DBG-MODULE<00800000 015ae000 "Diablo III.exe" "Diablo III.pdb" 0 {88ea106f-6dcc-41da-b3595ac37e053f02} 1 1354589875>
DBG-MODULE<0B2B0000 0066c000 "battle.net.dll" "battle.net.pdb" 0 {7d76a309-d094-4a1d-ab758495bbe9ad4b} 1 1351709201>
DBG-MODULE<0FFF0000 0000e000 "HookKey32.dll" "HookKey32.pdb" 0 {9cf80870-66a7-40cf-981792588b26e21e} 2 1241579880>
DBG-MODULE<10000000 00107000 "fmodex.dll" "" 0 {00000000-0000-0000-0000000000000000} 0 1326840840>
DBG-MODULE<4A800000 00107000 "icuuc49.dll" "" 0 {00000000-0000-0000-0000000000000000} 0 1333659974>
DBG-MODULE<57330000 01122000 "icudt49.dll" "" 0 {00000000-0000-0000-0000000000000000} 0 1333660452>
DBG-MODULE<60000000 0005d000 "ijl15.dll" "" 0 {00000000-0000-0000-0000000000000000} 0 969018715>
DBG-MODULE<61760000 0029c000 "atiumdva.dll" "atiumdva.pdb" 0 {b7e5f1a5-abf7-4272-a59e55ec36719bee} 1 1348795351>
DBG-MODULE<61A00000 00553000 "atiumdag.dll" "atiumdag.pdb" 0 {9a7c4df5-d349-4484-9786ccef70825ec4} 1 1348796144>
DBG-MODULE<65A20000 000e9000 "aticfx32.dll" "aticfx32.pdb" 0 {b9db66a5-781f-4b91-8952d4bddbddd17a} 1 1348796608>
DBG-MODULE<662C0000 000e7000 "DDRAW.DLL" "ddraw.pdb" 0 {497dbeef-b385-4f24-bc6a468137860ada} 2 1247533496>
DBG-MODULE<667B0000 00019000 "atiu9pag.dll" "atiu9pag.pdb" 0 {c07adb19-050b-4dfe-a7f1dc0d71eb8f7c} 7 1348794659>
DBG-MODULE<667D0000 00006000 "DCIMAN32.dll" "dciman32.pdb" 0 {f1c0c4b3-249c-4aaa-8a5130d41835b365} 2 1247533492>
DBG-MODULE<68EF0000 000bf000 "MSVCR100.dll" "msvcr100.i386.pdb" 0 {da7b3ed8-d4af-49ef-a87d61651bd1d649} 2 1298074658>
DBG-MODULE<68FB0000 00069000 "MSVCP100.dll" "msvcp100.i386.pdb" 0 {ce7fb6a1-0ef0-4315-8107764d8fea7dc2} 1 1298074689>
DBG-MODULE<69F80000 001c3000 "d3d9.dll" "d3d9.pdb" 0 {f55aeb50-462b-473f-9733515dc6532daf} 2 1290254259>
DBG-MODULE<6D240000 00006000 "sensapi.dll" "SensApi.pdb" 0 {1f9bbfcb-f7a9-451b-89a51771ca4c47db} 2 1247533841>
DBG-MODULE<6D5B0000 0004f000 "webio.dll" "webio.pdb" 0 {a4d8edee-3211-49f4-931a8f77ff4ae154} 2 1321507702>
DBG-MODULE<6D600000 00058000 "WINHTTP.dll" "winhttp.pdb" 0 {ab606da6-47f9-4a10-8ffe404a2624d13e} 2 1290254910>
DBG-MODULE<6FAF0000 00006000 "rasadhlp.dll" "rasadhlp.pdb" 0 {9c177d0e-6fd1-4d28-bae05d9757e8182f} 2 1247533782>
DBG-MODULE<6FB00000 00038000 "fwpuclnt.dll" "fwpuclnt.pdb" 0 {eb7d55a5-3635-4ad9-87ce2e36914aaf37} 2 1290254386>
DBG-MODULE<70BE0000 00006000 "wship6.dll" "wship6.pdb" 0 {02e45101-e951-429f-85676adfcc0ea72a} 2 1247533910>
DBG-MODULE<71A40000 0000d000 "rtutils.dll" "rtutils.pdb" 0 {b7794699-4af6-4de6-b40cbffe6d34d049} 2 1290254764>
DBG-MODULE<71AA0000 00015000 "rasman.dll" "rasman.pdb" 0 {df9a8608-77f9-4fec-bb7a2cf29c7d5edd} 2 1247533791>
DBG-MODULE<71AC0000 00052000 "RASAPI32.dll" "rasapi32.pdb" 0 {b6e3857a-947f-4f9e-86d6c3a36576bf15} 2 1247533783>
DBG-MODULE<71B20000 0001b000 "AUTHZ.dll" "authz.pdb" 0 {2d43c270-b407-466c-8b640ee17bf00012} 2 1247533452>
DBG-MODULE<71B40000 00025000 "peerdist.dll" "peerdist.pdb" 0 {71032826-7640-4af4-8567ee4df4a88bc3} 1 1247533772>
DBG-MODULE<71BB0000 000f5000 "PROPSYS.dll" "propsys.pdb" 0 {d0eda507-e53d-4579-a337f875012d7b48} 2 1290254723>
DBG-MODULE<72630000 00044000 "dnsapi.DLL" "dnsapi.pdb" 0 {4b77ba91-498a-432f-8dd6e52085c4c423} 2 1299130163>
DBG-MODULE<726D0000 0000f000 "PrxerNsp.dll" "PrxerNsp.pdb" 0 {0d0bc268-1d9c-4ec4-bdc6c6be51ad67f6} 1 1332968763>
DBG-MODULE<726E0000 00005000 "wshtcpip.dll" "wshtcpip.pdb" 0 {92a92ff2-9357-4b48-9795898561f00719} 2 1247533914>
DBG-MODULE<726F0000 00008000 "winrnr.dll" "winrnr.pdb" 0 {45f8b97b-1285-48d7-88289c58e8c5b3ca} 2 1247533892>
DBG-MODULE<72730000 00027000 "WLIDNSP.DLL" "wlidNSP.pdb" 0 {1069480a-b687-4cde-af1bbe9a7518bfdf} 1 1301369476>
DBG-MODULE<72760000 00013000 "PrxerDrv.dll" "PrxerDrv.pdb" 0 {15440986-8e54-4a57-acb3314d75a65129} 1 1332968825>
DBG-MODULE<72780000 0000d000 "wshbth.dll" "wshbth.pdb" 0 {a4029cd5-2356-436b-b45283f6d1d1a710} 1 1290247216>
DBG-MODULE<727A0000 00012000 "pnrpnsp.dll" "pnrpnsp.pdb" 0 {d02619bd-04db-444d-9215d3ce9d69f106} 2 1247533814>
DBG-MODULE<727E0000 00010000 "napinsp.dll" "NapiNSP.pdb" 0 {35d1fb44-6b06-4c3c-84108202e55b284a} 2 1247533677>
DBG-MODULE<72820000 00010000 "NLAapi.dll" "nlaapi.pdb" 0 {fdeda658-3b21-4a07-8ed32201988ecffc} 2 1326438106>
DBG-MODULE<72890000 00007000 "WSOCK32.dll" "wsock32.pdb" 0 {0aae6683-a7f5-40df-b265dcd12b7bd0fb} 2 1247533923>
DBG-MODULE<728A0000 0003c000 "MSWSOCK.dll" "mswsock.pdb" 0 {5d01bc6d-4da8-4939-baf8725d60d595a6} 2 1290254568>
DBG-MODULE<729A0000 0001c000 "iphlpapi.DLL" "iphlpapi.pdb" 0 {f162d2e1-37ed-4297-8bf38c99aee2daab} 2 1290254425>
DBG-MODULE<72A10000 00007000 "WINNSI.DLL" "winnsi.pdb" 0 {f7a0c25b-1b0e-4fa6-876494d3f6bfd101} 2 1247533891>
DBG-MODULE<72B80000 00008000 "Secur32.dll" "secur32.pdb" 0 {8ef4e863-187c-45e7-8f4632152cc82feb} 2 1345827150>
DBG-MODULE<73000000 0000b000 "profapi.dll" "profapi.pdb" 0 {ca045ca9-e5c7-4d89-9b90e776b38a18b3} 2 1247526721>
DBG-MODULE<73010000 00017000 "USERENV.dll" "userenv.pdb" 0 {fd47f512-75f8-4fca-aa6071cb11cc4ab8} 2 1290254888>
DBG-MODULE<73130000 00032000 "WINMM.dll" "winmm.pdb" 0 {7afd98fc-aad3-4f6b-8b31a4667c4e2bfc} 2 1290254914>
DBG-MODULE<73180000 0003b000 "rsaenh.dll" "rsaenh.pdb" 0 {f03813e5-a055-4853-a6bc085c17a3ab35} 2 1247533792>
DBG-MODULE<731E0000 00016000 "CRYPTSP.dll" "cryptsp.pdb" 0 {9536207f-9c26-4d92-b2c50d44e77ac0a9} 1 1247533629>
DBG-MODULE<73440000 0019e000 "comctl32.dll" "comctl32.pdb" 0 {b4ce90aa-b95e-4b89-a22a7711dfd7e6ef} 2 1290254108>
DBG-MODULE<735E0000 00009000 "VERSION.dll" "version.pdb" 0 {52234e5c-7ec4-4646-b62d56357b2c9487} 2 1247533867>
DBG-MODULE<73750000 00013000 "dwmapi.dll" "dwmapi.pdb" 0 {d8d91b3f-339a-4fdc-960fc7121d146df4} 2 1247533575>
DBG-MODULE<73770000 00006000 "d3d8thk.dll" "d3d8thk.pdb" 0 {d9c3a335-615f-448e-a0b012d76716e6b7} 2 1247533480>
DBG-MODULE<73860000 000eb000 "dbghelp.dll" "dbghelp.pdb" 0 {6b19f261-ee43-4af5-9623d1791ce5a7d7} 2 1290254268>
DBG-MODULE<74390000 00007000 "midimap.dll" "midimap.pdb" 0 {49f76fa5-3b85-4e54-a748a2b4301471b6} 2 1247533700>
DBG-MODULE<743A0000 00014000 "MSACM32.dll" "msacm32.pdb" 0 {3d318d5e-38c5-4502-b64578f0710a510f} 2 1247533646>
DBG-MODULE<743C0000 00008000 "msacm32.drv" "msacm32.pdb" 0 {eb29395a-e017-43db-8c5dcb7f5a1350f9} 1 1247533647>
DBG-MODULE<743D0000 00036000 "AUDIOSES.DLL" "AudioSes.pdb" 0 {a88fcf91-9449-49a8-a1863d1592bb2fd1} 2 1290254117>
DBG-MODULE<74420000 00007000 "AVRT.dll" "avrt.pdb" 0 {a15e148a-cfc7-4f88-a0a6daf71cc91647} 2 1247533464>
DBG-MODULE<74440000 00004000 "ksuser.dll" "ksuser.pdb" 0 {7ae6bfac-128c-4c57-baaf1c0b79fa95b4} 2 1247533747>
DBG-MODULE<74450000 00030000 "wdmaud.drv" "wdmaud.pdb" 0 {f232d0b4-9257-4d79-92d5805bef84a01e} 2 1290254886>
DBG-MODULE<744B0000 00039000 "MMDevApi.dll" "MMDevAPI.pdb" 0 {941e45a6-3e8f-457d-90ce29cc508c34b9} 2 1290254482>
DBG-MODULE<74AC0000 0000c000 "CRYPTBASE.dll" "cryptbase.pdb" 0 {e62feae5-59ee-4cd9-95614215b01ac210} 2 1247526721>
DBG-MODULE<74AD0000 00060000 "SspiCli.dll" "wsspicli.pdb" 0 {c40594fd-ee2c-4889-84d245a514b2a513} 1 1345827215>
DBG-MODULE<74B30000 00090000 "GDI32.dll" "wgdi32.pdb" 0 {08a541b5-9422-42bd-b4aeabd8c87e4cff} 2 1290254931>
DBG-MODULE<74C40000 000cc000 "MSCTF.dll" "msctf.pdb" 0 {173daef8-6b25-48db-a6134eb74c4d2f23} 2 1247533673>
DBG-MODULE<74D40000 00111000 "urlmon.dll" "urlmon.pdb" 0 {36c35318-9b3b-49b8-86c071509a0e03d9} 2 1352858260>
DBG-MODULE<74E60000 0011b000 "WININET.dll" "wininet.pdb" 0 {6322bfa5-eea2-4a32-9fdc8269aca33cf5} 2 1352858236>
DBG-MODULE<74F80000 0000a000 "LPK.dll" "wlpk.pdb" 0 {c39166a5-3cce-43f0-adf876b9c637a1ea} 1 1247533883>
DBG-MODULE<75020000 00005000 "PSAPI.DLL" "psapi.pdb" 0 {a895a052-f325-481b-9e2da00a29e8d5df} 2 1247533774>
DBG-MODULE<75030000 00083000 "CLBCatQ.DLL" "CLBCatQ.pdb" 0 {00a720c7-9bac-4022-95b6ebdc14725718} 2 1247533489>
DBG-MODULE<750C0000 0019d000 "SETUPAPI.dll" "setupapi.pdb" 0 {c6b7cc38-0fcd-42c2-9edb1b61757dfd92} 2 1290254809>
DBG-MODULE<75260000 00027000 "CFGMGR32.dll" "cfgmgr32.pdb" 0 {e4c73e93-b825-413f-99e80ba656c48317} 2 1306232913>
DBG-MODULE<75290000 00100000 "USER32.dll" "wuser32.pdb" 0 {0fce9cc3-01ed-4567-a819705b2718e1d6} 2 1290254937>
DBG-MODULE<75390000 00012000 "DEVOBJ.dll" "devobj.pdb" 0 {583f4457-964d-46ca-8c36ed4903be6aa2} 2 1306232957>
DBG-MODULE<753B0000 001b8000 "iertutil.dll" "iertutil.pdb" 0 {e575ae77-7ca7-4e1f-b092ddccaa6d70d5} 2 1352857582>
DBG-MODULE<75570000 0009d000 "USP10.dll" "usp10.pdb" 0 {f49786e2-c7c5-4ea9-9e7c37120cdaeb9c} 1 1290254889>
DBG-MODULE<75610000 00060000 "IMM32.dll" "wimm32.pdb" 0 {35dd4069-eb2a-43bf-869d6e311fad0945} 2 1290254931>
DBG-MODULE<75670000 00c4a000 "SHELL32.dll" "shell32.pdb" 0 {1489bcd8-e80c-441e-91308a093631de5e} 2 1339216345>
DBG-MODULE<762C0000 000a0000 "ADVAPI32.dll" "advapi32.pdb" 0 {3f32049f-550c-42b0-9cf114a1fb8a97e9} 2 1290254086>
DBG-MODULE<76360000 00003000 "Normaliz.dll" "normaliz.pdb" 0 {9481804b-b4fd-4703-ae6ae76f8b99b476} 1 1247533780>
DBG-MODULE<76370000 0015c000 "ole32.dll" "ole32.pdb" 0 {5061f11a-9a57-4335-95ea5ea75a156f4b} 2 1290254703>
DBG-MODULE<76500000 0000c000 "MSASN1.dll" "msasn1.pdb" 0 {003d5f0e-2480-4b20-953a7a021b52fc32} 2 1290254537>
DBG-MODULE<76510000 0011e000 "CRYPT32.dll" "crypt32.pdb" 0 {c9c09a1f-f969-489d-acf298c897a447c8} 2 1338611300>
DBG-MODULE<76630000 00110000 "kernel32.dll" "wkernel32.pdb" 0 {d08f1e13-1d1f-4d97-b4ab2f64e00cfc8b} 2 1349369423>
DBG-MODULE<76740000 00035000 "WS2_32.dll" "ws2_32.pdb" 0 {18c960b9-5840-4c4f-80f686ee978a33d4} 2 1290254952>
DBG-MODULE<76780000 00045000 "WLDAP32.dll" "wldap32.pdb" 0 {a0183052-c47e-4652-bfc983cc603c1244} 2 1290254946>
DBG-MODULE<76830000 00019000 "sechost.dll" "sechost.pdb" 0 {7af14d02-d41e-4cd6-942745fe0e6372b1} 1 1247533828>
DBG-MODULE<76850000 00057000 "SHLWAPI.dll" "shlwapi.pdb" 0 {e128b1ce-e2eb-438c-8646e6967118f33e} 2 1290254818>
DBG-MODULE<768B0000 000f0000 "RPCRT4.dll" "wrpcrt4.pdb" 0 {fac24015-130d-4d7f-aaa77ea36ed5af1c} 2 1290254937>
DBG-MODULE<769A0000 00047000 "KERNELBASE.dll" "wkernelbase.pdb" 0 {e1609de3-233b-4edf-8211cf7e83211b40} 1 1349369424>
DBG-MODULE<769F0000 0008f000 "OLEAUT32.dll" "oleaut32.pdb" 0 {68047829-a475-4e78-9ac1c8035ba168cd} 2 1314418730>
DBG-MODULE<76A80000 000ac000 "msvcrt.dll" "msvcrt.pdb" 0 {f1d253f9-555c-46df-8076400a52b3a929} 2 1324021538>
DBG-MODULE<773C0000 00006000 "NSI.dll" "nsi.pdb" 0 {d15a8167-9fae-4a73-92344b6fd2686794} 2 1247533785>
DBG-MODULE<773F0000 00180000 "ntdll.dll" "wntdll.pdb" 0 {d74f79eb-1f8d-4a45-abcd2f476ccabacc} 2 1321507727>
------------------------------------------------------------------------------
<:Inspector.DebugModules>
<Operating_System:>
Windows 7-64 SP1 (Version 6.1.7601)
<:Operating_System>
<CPU_Vendor:>
GenuineIntel
<:CPU_Vendor>
<CPU_Details:>
Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz
<:CPU_Details>
<CPU_Processors:>
1
<:CPU_Processors>
<CPU_Cores:>
4
<:CPU_Cores>
<CPU_Threads:>
8
<:CPU_Threads>
<System_Memory:>
24543.14 MB
<:System_Memory>
<System_Memory_Binned:>
3700 - 9999 MB
<:System_Memory_Binned>
<CommandLine:>
-launch
<:CommandLine>
<AuroraDLLVersion:>
Battle.net Aurora 127cc0376a_public/471 (Oct 31 2012 11:44:48)
<:AuroraDLLVersion>
<AuroraLIBVersion:>
Battle.net Aurora 127cc0376a_public/471 (Oct 31 2012 11:44:48)
<:AuroraLIBVersion>
<Locale:>
enGB
<:Locale>
<Video_Card:>
AMD Radeon HD 6900 Series
<:Video_Card>
<Video_Driver:>
8.17.10.1151
<:Video_Driver>
<Video_Memory:>
2014 MB
<:Video_Memory>
<Sound_Card:>
AMD HDMI Output (AMD High Definition Audio Device)
<:Sound_Card>
<Sound_Speaker_Mode:>
Stereo
<:Sound_Speaker_Mode>
<GameAccount:>
{ high: 144115196665807923 low: 10829106 }
<:GameAccount>
<GameServerAddress:>
80.239.211.3:1119
<:GameServerAddress>
<Inspector.ProjectId:>
36
<:Inspector.ProjectId>
<Executable:>
Diablo III
<:Executable>
<Inspector.Module:>
Diablo III
<:Inspector.Module>
<Inspector.BuildNumber:>
13644
<:Inspector.BuildNumber>
<Inspector.Platform:>
All Win
<:Inspector.Platform>
<Inspector.IssueType:>
Exception
<:Inspector.IssueType>
<Version:>
1.0.6.13644 (63005-790766)
<:Version>
<Inspector.Priority:>
1 - Critical
<:Inspector.Priority>
<Inspector.Language:>
enGB
<:Inspector.Language>
<Inspector.Branch:>
1_0_6
<:Inspector.Branch>
<Inspector.HashBlock:>
DBG-OPTIONS<FunctionsOnly>
DBG-ADDR<00a429e6>("Diablo III.exe")
DBG-ADDR<00ce2fd0>("Diablo III.exe")
DBG-ADDR<00865853>("Diablo III.exe")
DBG-ADDR<008d1816>("Diablo III.exe")
DBG-ADDR<008d20e0>("Diablo III.exe")
DBG-ADDR<00dc6781>("Diablo III.exe")
DBG-ADDR<0080dfa4>("Diablo III.exe")
DBG-OPTIONS<>
<:Inspector.HashBlock>
<Inspector.PrimaryAssignment:>
.Programmers
<:Inspector.PrimaryAssignment>
<Inspector.Summary:>
***** UNHANDLED EXCEPTION: ACCESS_VIOLATION (c0000005)
<:Inspector.Summary>
<Inspector.Assertion:>
***** UNHANDLED EXCEPTION: ACCESS_VIOLATION (c0000005)
------------
Stack Crawl:
------------
DBG-ADDR<00A429E6>("Diablo III.exe")
DBG-ADDR<00CE2FD0>("Diablo III.exe")
DBG-ADDR<00865853>("Diablo III.exe")
DBG-ADDR<008D1816>("Diablo III.exe")
DBG-ADDR<008D20E0>("Diablo III.exe")
DBG-ADDR<00DC6781>("Diablo III.exe")
DBG-ADDR<0080DFA4>("Diablo III.exe")
7 frames dumped
<:Inspector.Assertion>
<Inspector.DebugModules:>
------------------------------------------------------------------------------
----------------------------------------
Loaded Modules
----------------------------------------
DBG-MODULE<00540000 00149000 "icuin49.dll" "" 0 {00000000-0000-0000-0000000000000000} 0 1333660131>
DBG-MODULE<00800000 015ae000 "Diablo III.exe" "Diablo III.pdb" 0 {88ea106f-6dcc-41da-b3595ac37e053f02} 1 1354589875>
DBG-MODULE<0B2B0000 0066c000 "battle.net.dll" "battle.net.pdb" 0 {7d76a309-d094-4a1d-ab758495bbe9ad4b} 1 1351709201>
DBG-MODULE<0FFF0000 0000e000 "HookKey32.dll" "HookKey32.pdb" 0 {9cf80870-66a7-40cf-981792588b26e21e} 2 1241579880>
DBG-MODULE<10000000 00107000 "fmodex.dll" "" 0 {00000000-0000-0000-0000000000000000} 0 1326840840>
DBG-MODULE<4A800000 00107000 "icuuc49.dll" "" 0 {00000000-0000-0000-0000000000000000} 0 1333659974>
DBG-MODULE<57330000 01122000 "icudt49.dll" "" 0 {00000000-0000-0000-0000000000000000} 0 1333660452>
DBG-MODULE<60000000 0005d000 "ijl15.dll" "" 0 {00000000-0000-0000-0000000000000000} 0 969018715>
DBG-MODULE<61760000 0029c000 "atiumdva.dll" "atiumdva.pdb" 0 {b7e5f1a5-abf7-4272-a59e55ec36719bee} 1 1348795351>
DBG-MODULE<61A00000 00553000 "atiumdag.dll" "atiumdag.pdb" 0 {9a7c4df5-d349-4484-9786ccef70825ec4} 1 1348796144>
DBG-MODULE<65A20000 000e9000 "aticfx32.dll" "aticfx32.pdb" 0 {b9db66a5-781f-4b91-8952d4bddbddd17a} 1 1348796608>
DBG-MODULE<662C0000 000e7000 "DDRAW.DLL" "ddraw.pdb" 0 {497dbeef-b385-4f24-bc6a468137860ada} 2 1247533496>
DBG-MODULE<667B0000 00019000 "atiu9pag.dll" "atiu9pag.pdb" 0 {c07adb19-050b-4dfe-a7f1dc0d71eb8f7c} 7 1348794659>
DBG-MODULE<667D0000 00006000 "DCIMAN32.dll" "dciman32.pdb" 0 {f1c0c4b3-249c-4aaa-8a5130d41835b365} 2 1247533492>
DBG-MODULE<68EF0000 000bf000 "MSVCR100.dll" "msvcr100.i386.pdb" 0 {da7b3ed8-d4af-49ef-a87d61651bd1d649} 2 1298074658>
DBG-MODULE<68FB0000 00069000 "MSVCP100.dll" "msvcp100.i386.pdb" 0 {ce7fb6a1-0ef0-4315-8107764d8fea7dc2} 1 1298074689>
DBG-MODULE<69F80000 001c3000 "d3d9.dll" "d3d9.pdb" 0 {f55aeb50-462b-473f-9733515dc6532daf} 2 1290254259>
DBG-MODULE<6D240000 00006000 "sensapi.dll" "SensApi.pdb" 0 {1f9bbfcb-f7a9-451b-89a51771ca4c47db} 2 1247533841>
DBG-MODULE<6D5B0000 0004f000 "webio.dll" "webio.pdb" 0 {a4d8edee-3211-49f4-931a8f77ff4ae154} 2 1321507702>
DBG-MODULE<6D600000 00058000 "WINHTTP.dll" "winhttp.pdb" 0 {ab606da6-47f9-4a10-8ffe404a2624d13e} 2 1290254910>
DBG-MODULE<6FAF0000 00006000 "rasadhlp.dll" "rasadhlp.pdb" 0 {9c177d0e-6fd1-4d28-bae05d9757e8182f} 2 1247533782>
DBG-MODULE<6FB00000 00038000 "fwpuclnt.dll" "fwpuclnt.pdb" 0 {eb7d55a5-3635-4ad9-87ce2e36914aaf37} 2 1290254386>
DBG-MODULE<70BE0000 00006000 "wship6.dll" "wship6.pdb" 0 {02e45101-e951-429f-85676adfcc0ea72a} 2 1247533910>
DBG-MODULE<71A40000 0000d000 "rtutils.dll" "rtutils.pdb" 0 {b7794699-4af6-4de6-b40cbffe6d34d049} 2 1290254764>
DBG-MODULE<71AA0000 00015000 "rasman.dll" "rasman.pdb" 0 {df9a8608-77f9-4fec-bb7a2cf29c7d5edd} 2 1247533791>
DBG-MODULE<71AC0000 00052000 "RASAPI32.dll" "rasapi32.pdb" 0 {b6e3857a-947f-4f9e-86d6c3a36576bf15} 2 1247533783>
DBG-MODULE<71B20000 0001b000 "AUTHZ.dll" "authz.pdb" 0 {2d43c270-b407-466c-8b640ee17bf00012} 2 1247533452>
DBG-MODULE<71B40000 00025000 "peerdist.dll" "peerdist.pdb" 0 {71032826-7640-4af4-8567ee4df4a88bc3} 1 1247533772>
DBG-MODULE<71BB0000 000f5000 "PROPSYS.dll" "propsys.pdb" 0 {d0eda507-e53d-4579-a337f875012d7b48} 2 1290254723>
DBG-MODULE<72630000 00044000 "dnsapi.DLL" "dnsapi.pdb" 0 {4b77ba91-498a-432f-8dd6e52085c4c423} 2 1299130163>
DBG-MODULE<726D0000 0000f000 "PrxerNsp.dll" "PrxerNsp.pdb" 0 {0d0bc268-1d9c-4ec4-bdc6c6be51ad67f6} 1 1332968763>
DBG-MODULE<726E0000 00005000 "wshtcpip.dll" "wshtcpip.pdb" 0 {92a92ff2-9357-4b48-9795898561f00719} 2 1247533914>
DBG-MODULE<726F0000 00008000 "winrnr.dll" "winrnr.pdb" 0 {45f8b97b-1285-48d7-88289c58e8c5b3ca} 2 1247533892>
DBG-MODULE<72730000 00027000 "WLIDNSP.DLL" "wlidNSP.pdb" 0 {1069480a-b687-4cde-af1bbe9a7518bfdf} 1 1301369476>
DBG-MODULE<72760000 00013000 "PrxerDrv.dll" "PrxerDrv.pdb" 0 {15440986-8e54-4a57-acb3314d75a65129} 1 1332968825>
DBG-MODULE<72780000 0000d000 "wshbth.dll" "wshbth.pdb" 0 {a4029cd5-2356-436b-b45283f6d1d1a710} 1 1290247216>
DBG-MODULE<727A0000 00012000 "pnrpnsp.dll" "pnrpnsp.pdb" 0 {d02619bd-04db-444d-9215d3ce9d69f106} 2 1247533814>
DBG-MODULE<727E0000 00010000 "napinsp.dll" "NapiNSP.pdb" 0 {35d1fb44-6b06-4c3c-84108202e55b284a} 2 1247533677>
DBG-MODULE<72820000 00010000 "NLAapi.dll" "nlaapi.pdb" 0 {fdeda658-3b21-4a07-8ed32201988ecffc} 2 1326438106>
DBG-MODULE<72890000 00007000 "WSOCK32.dll" "wsock32.pdb" 0 {0aae6683-a7f5-40df-b265dcd12b7bd0fb} 2 1247533923>
DBG-MODULE<728A0000 0003c000 "MSWSOCK.dll" "mswsock.pdb" 0 {5d01bc6d-4da8-4939-baf8725d60d595a6} 2 1290254568>
DBG-MODULE<729A0000 0001c000 "iphlpapi.DLL" "iphlpapi.pdb" 0 {f162d2e1-37ed-4297-8bf38c99aee2daab} 2 1290254425>
DBG-MODULE<72A10000 00007000 "WINNSI.DLL" "winnsi.pdb" 0 {f7a0c25b-1b0e-4fa6-876494d3f6bfd101} 2 1247533891>
DBG-MODULE<72B80000 00008000 "Secur32.dll" "secur32.pdb" 0 {8ef4e863-187c-45e7-8f4632152cc82feb} 2 1345827150>
DBG-MODULE<73000000 0000b000 "profapi.dll" "profapi.pdb" 0 {ca045ca9-e5c7-4d89-9b90e776b38a18b3} 2 1247526721>
DBG-MODULE<73010000 00017000 "USERENV.dll" "userenv.pdb" 0 {fd47f512-75f8-4fca-aa6071cb11cc4ab8} 2 1290254888>
DBG-MODULE<73130000 00032000 "WINMM.dll" "winmm.pdb" 0 {7afd98fc-aad3-4f6b-8b31a4667c4e2bfc} 2 1290254914>
DBG-MODULE<73180000 0003b000 "rsaenh.dll" "rsaenh.pdb" 0 {f03813e5-a055-4853-a6bc085c17a3ab35} 2 1247533792>
DBG-MODULE<731E0000 00016000 "CRYPTSP.dll" "cryptsp.pdb" 0 {9536207f-9c26-4d92-b2c50d44e77ac0a9} 1 1247533629>
DBG-MODULE<73440000 0019e000 "comctl32.dll" "comctl32.pdb" 0 {b4ce90aa-b95e-4b89-a22a7711dfd7e6ef} 2 1290254108>
DBG-MODULE<735E0000 00009000 "VERSION.dll" "version.pdb" 0 {52234e5c-7ec4-4646-b62d56357b2c9487} 2 1247533867>
DBG-MODULE<73750000 00013000 "dwmapi.dll" "dwmapi.pdb" 0 {d8d91b3f-339a-4fdc-960fc7121d146df4} 2 1247533575>
DBG-MODULE<73770000 00006000 "d3d8thk.dll" "d3d8thk.pdb" 0 {d9c3a335-615f-448e-a0b012d76716e6b7} 2 1247533480>
DBG-MODULE<73860000 000eb000 "dbghelp.dll" "dbghelp.pdb" 0 {6b19f261-ee43-4af5-9623d1791ce5a7d7} 2 1290254268>
DBG-MODULE<74390000 00007000 "midimap.dll" "midimap.pdb" 0 {49f76fa5-3b85-4e54-a748a2b4301471b6} 2 1247533700>
DBG-MODULE<743A0000 00014000 "MSACM32.dll" "msacm32.pdb" 0 {3d318d5e-38c5-4502-b64578f0710a510f} 2 1247533646>
DBG-MODULE<743C0000 00008000 "msacm32.drv" "msacm32.pdb" 0 {eb29395a-e017-43db-8c5dcb7f5a1350f9} 1 1247533647>
DBG-MODULE<743D0000 00036000 "AUDIOSES.DLL" "AudioSes.pdb" 0 {a88fcf91-9449-49a8-a1863d1592bb2fd1} 2 1290254117>
DBG-MODULE<74420000 00007000 "AVRT.dll" "avrt.pdb" 0 {a15e148a-cfc7-4f88-a0a6daf71cc91647} 2 1247533464>
DBG-MODULE<74440000 00004000 "ksuser.dll" "ksuser.pdb" 0 {7ae6bfac-128c-4c57-baaf1c0b79fa95b4} 2 1247533747>
DBG-MODULE<74450000 00030000 "wdmaud.drv" "wdmaud.pdb" 0 {f232d0b4-9257-4d79-92d5805bef84a01e} 2 1290254886>
DBG-MODULE<744B0000 00039000 "MMDevApi.dll" "MMDevAPI.pdb" 0 {941e45a6-3e8f-457d-90ce29cc508c34b9} 2 1290254482>
DBG-MODULE<74AC0000 0000c000 "CRYPTBASE.dll" "cryptbase.pdb" 0 {e62feae5-59ee-4cd9-95614215b01ac210} 2 1247526721>
DBG-MODULE<74AD0000 00060000 "SspiCli.dll" "wsspicli.pdb" 0 {c40594fd-ee2c-4889-84d245a514b2a513} 1 1345827215>
DBG-MODULE<74B30000 00090000 "GDI32.dll" "wgdi32.pdb" 0 {08a541b5-9422-42bd-b4aeabd8c87e4cff} 2 1290254931>
DBG-MODULE<74C40000 000cc000 "MSCTF.dll" "msctf.pdb" 0 {173daef8-6b25-48db-a6134eb74c4d2f23} 2 1247533673>
DBG-MODULE<74D40000 00111000 "urlmon.dll" "urlmon.pdb" 0 {36c35318-9b3b-49b8-86c071509a0e03d9} 2 1352858260>
DBG-MODULE<74E60000 0011b000 "WININET.dll" "wininet.pdb" 0 {6322bfa5-eea2-4a32-9fdc8269aca33cf5} 2 1352858236>
DBG-MODULE<74F80000 0000a000 "LPK.dll" "wlpk.pdb" 0 {c39166a5-3cce-43f0-adf876b9c637a1ea} 1 1247533883>
DBG-MODULE<75020000 00005000 "PSAPI.DLL" "psapi.pdb" 0 {a895a052-f325-481b-9e2da00a29e8d5df} 2 1247533774>
DBG-MODULE<75030000 00083000 "CLBCatQ.DLL" "CLBCatQ.pdb" 0 {00a720c7-9bac-4022-95b6ebdc14725718} 2 1247533489>
DBG-MODULE<750C0000 0019d000 "SETUPAPI.dll" "setupapi.pdb" 0 {c6b7cc38-0fcd-42c2-9edb1b61757dfd92} 2 1290254809>
DBG-MODULE<75260000 00027000 "CFGMGR32.dll" "cfgmgr32.pdb" 0 {e4c73e93-b825-413f-99e80ba656c48317} 2 1306232913>
DBG-MODULE<75290000 00100000 "USER32.dll" "wuser32.pdb" 0 {0fce9cc3-01ed-4567-a819705b2718e1d6} 2 1290254937>
DBG-MODULE<75390000 00012000 "DEVOBJ.dll" "devobj.pdb" 0 {583f4457-964d-46ca-8c36ed4903be6aa2} 2 1306232957>
DBG-MODULE<753B0000 001b8000 "iertutil.dll" "iertutil.pdb" 0 {e575ae77-7ca7-4e1f-b092ddccaa6d70d5} 2 1352857582>
DBG-MODULE<75570000 0009d000 "USP10.dll" "usp10.pdb" 0 {f49786e2-c7c5-4ea9-9e7c37120cdaeb9c} 1 1290254889>
DBG-MODULE<75610000 00060000 "IMM32.dll" "wimm32.pdb" 0 {35dd4069-eb2a-43bf-869d6e311fad0945} 2 1290254931>
DBG-MODULE<75670000 00c4a000 "SHELL32.dll" "shell32.pdb" 0 {1489bcd8-e80c-441e-91308a093631de5e} 2 1339216345>
DBG-MODULE<762C0000 000a0000 "ADVAPI32.dll" "advapi32.pdb" 0 {3f32049f-550c-42b0-9cf114a1fb8a97e9} 2 1290254086>
DBG-MODULE<76360000 00003000 "Normaliz.dll" "normaliz.pdb" 0 {9481804b-b4fd-4703-ae6ae76f8b99b476} 1 1247533780>
DBG-MODULE<76370000 0015c000 "ole32.dll" "ole32.pdb" 0 {5061f11a-9a57-4335-95ea5ea75a156f4b} 2 1290254703>
DBG-MODULE<76500000 0000c000 "MSASN1.dll" "msasn1.pdb" 0 {003d5f0e-2480-4b20-953a7a021b52fc32} 2 1290254537>
DBG-MODULE<76510000 0011e000 "CRYPT32.dll" "crypt32.pdb" 0 {c9c09a1f-f969-489d-acf298c897a447c8} 2 1338611300>
DBG-MODULE<76630000 00110000 "kernel32.dll" "wkernel32.pdb" 0 {d08f1e13-1d1f-4d97-b4ab2f64e00cfc8b} 2 1349369423>
DBG-MODULE<76740000 00035000 "WS2_32.dll" "ws2_32.pdb" 0 {18c960b9-5840-4c4f-80f686ee978a33d4} 2 1290254952>
DBG-MODULE<76780000 00045000 "WLDAP32.dll" "wldap32.pdb" 0 {a0183052-c47e-4652-bfc983cc603c1244} 2 1290254946>
DBG-MODULE<76830000 00019000 "sechost.dll" "sechost.pdb" 0 {7af14d02-d41e-4cd6-942745fe0e6372b1} 1 1247533828>
DBG-MODULE<76850000 00057000 "SHLWAPI.dll" "shlwapi.pdb" 0 {e128b1ce-e2eb-438c-8646e6967118f33e} 2 1290254818>
DBG-MODULE<768B0000 000f0000 "RPCRT4.dll" "wrpcrt4.pdb" 0 {fac24015-130d-4d7f-aaa77ea36ed5af1c} 2 1290254937>
DBG-MODULE<769A0000 00047000 "KERNELBASE.dll" "wkernelbase.pdb" 0 {e1609de3-233b-4edf-8211cf7e83211b40} 1 1349369424>
DBG-MODULE<769F0000 0008f000 "OLEAUT32.dll" "oleaut32.pdb" 0 {68047829-a475-4e78-9ac1c8035ba168cd} 2 1314418730>
DBG-MODULE<76A80000 000ac000 "msvcrt.dll" "msvcrt.pdb" 0 {f1d253f9-555c-46df-8076400a52b3a929} 2 1324021538>
DBG-MODULE<773C0000 00006000 "NSI.dll" "nsi.pdb" 0 {d15a8167-9fae-4a73-92344b6fd2686794} 2 1247533785>
DBG-MODULE<773F0000 00180000 "ntdll.dll" "wntdll.pdb" 0 {d74f79eb-1f8d-4a45-abcd2f476ccabacc} 2 1321507727>
------------------------------------------------------------------------------
<:Inspector.DebugModules>
<Operating_System:>
Windows 7-64 SP1 (Version 6.1.7601)
<:Operating_System>
<CPU_Vendor:>
GenuineIntel
<:CPU_Vendor>
<CPU_Details:>
Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz
<:CPU_Details>
<CPU_Processors:>
1
<:CPU_Processors>
<CPU_Cores:>
4
<:CPU_Cores>
<CPU_Threads:>
8
<:CPU_Threads>
<System_Memory:>
24543.14 MB
<:System_Memory>
<System_Memory_Binned:>
3700 - 9999 MB
<:System_Memory_Binned>
<CommandLine:>
-launch
<:CommandLine>
<AuroraDLLVersion:>
Battle.net Aurora 127cc0376a_public/471 (Oct 31 2012 11:44:48)
<:AuroraDLLVersion>
<AuroraLIBVersion:>
Battle.net Aurora 127cc0376a_public/471 (Oct 31 2012 11:44:48)
<:AuroraLIBVersion>
<Locale:>
enGB
<:Locale>
<Video_Card:>
AMD Radeon HD 6900 Series
<:Video_Card>
<Video_Driver:>
8.17.10.1151
<:Video_Driver>
<Video_Memory:>
2014 MB
<:Video_Memory>
<Sound_Card:>
AMD HDMI Output (AMD High Definition Audio Device)
<:Sound_Card>
<Sound_Speaker_Mode:>
Stereo
<:Sound_Speaker_Mode>
<GameAccount:>
{ high: 144115196665807923 low: 10829106 }
<:GameAccount>
<GameServerAddress:>
80.239.211.3:1119
<:GameServerAddress>
diavol
New Member
- Joined
- Nov 12, 2012
- Messages
- 2
- Reaction score
- 0
my main that not got banned got 130 milions farming and not get banned my bots acc are banned but if u dont bot the sure is that this acc dont get banned so keep one acc for backup drops unselled gold that sure on any banwave not get lost ! anyway db looks lot of safe but when blizzard do research and wanna do bans for get more customers too sell cd keys yeah it will kick the existing bots of this period that do research and bot the period that wanna do the banwave so dont bot with the acc name that you lose your tears if banned bot with a cheap russian cd key for farming gold and testing thinks and got a secont one acc that you can play also if u like that not Bots
BTW is realy fun too try collect more gold from a bot if u can play diablo for 3 hours is nearly impossible ! u lose time on id move and THINKING STUFFS! bot is a cleary better mind and FARMER for d3 and better do it just for this and yeah it worth all of it!
Job2k9
New Member
- Joined
- Feb 11, 2010
- Messages
- 841
- Reaction score
- 3
http://www.thebuddyforum.com/demonbuddy-forum/97285-odd-bot-behavior-before-ban-4.html#post958745
Bots started their jumpy movements again. We shall see if bans hit. Could just be a side effect of some change in db or diablo.
Bots started their jumpy movements again. We shall see if bans hit. Could just be a side effect of some change in db or diablo.
darthtater
New Member
- Joined
- Nov 20, 2012
- Messages
- 14
- Reaction score
- 0
I wonder if the way DB opens a new game has anything to do with it. My settings can be set to act 3 hell but if its an inferno profile it will start in inferno.
I agree and have tried to point this out also. If people feel that having certain windows open when IDing/selling/salvaging matters, then so should changing games. The fact you can join at any quest/act from anywhere should be a major flag.
Also, another theory I had is the fact that only higher ilvl items are picked up (Trinity) which would look suspicious because the typical player would never know what is on the ground.
packetloss
New Member
- Joined
- Jul 29, 2012
- Messages
- 222
- Reaction score
- 1
That is not true. Most people actually playing the game only pick up level 61+ items, often only level 63+. You hit the control key and hover over the item and you can see what it is.
plus most ppl already memorized ilvl63+ item names so its not really suspicious to pick them so fast... even I am doing that on my private games... well i WAS
