My post ONLY applies to people who were banned but were honestly not using a bot, maphack, or other unauthorized 3rd party software that might be responsible.
Here's the quiz for you:
1) Did you disable DEP, also referred to as the NX bit?
(If you are unsure, do either of these things look familiar to you. If so then you should answer 'Yes')
A] Editing the boot.ini file to show - /noexecute=AlwaysOff
B] Entering in the command line - bcdedit.exe /set {current} nx AlwaysOff
2) If you have DEP disabled, did you then add the /PAE option to enable that?
(If you are unsure, do either of these things look familiar to you. If so then you should answer 'Yes')
A] Editing the boot.ini file to show - /PAE
B] Entering in the command line - bcdedit /set [{ID}] pae ForceEnable
3) Regardless of the above settings, did you enable the LargeAddressAware option?
(If you are unsure, do either of these things look familiar to you. If so then you should answer 'Yes')
A] Editing the boot.ini file to show - /3GB or /userva=
B] Entering in the command line - bcdedit /set increaseuserva
If you answered Yes to any of these options, and you genuinely were not cheating at all, then that's probably what caused you to be banned. Here is a killer link showing that Steam's Anti-Cheat (VAC) also doesn't function with DEP disabled. Keep in mind this is an official support help page from Steam, and if you do some Googling you can see many forums topics about VAC issues being resolved by re-enabling DEP:https://support.steampowered.com/kb_article.php?ref=2117-ilzv-2837&l=english
Obviously all of this is VERY easy to test. It doesn't matter what version of Windows you are on. If you don't believe that this could be the culprit, then instead of replying to this thread with the expected insults, go ahead and disable DEP and PAE for a full gaming session or two. If you survive a week afterword or through the next banwave then you are truly a brave and courageous individual and I will bow down and worship you.
And finally, for anyone who is experiecing the slow loading and freezing issue while trying to open your inventory screen, you are probably using a 32-bit operating system. If you add the /3GB option it completely resolves this problem. However, it's not actually fixing the problem by allowing Diablo to use more memory, because I don't even think Diablo is LargeAddress aware, but it re-maps the memory and circumvents a bug in Diablo's engine that was introduced in Patch 2.4: https://www.reddit.com/r/Diablo/comments/4jz6qb/fix_for_those_affected_by_inventory_screens_that/
I play on a Mac OSX but was still wrongfully banned on 14th June 2016. Just checking back here to see if there are more innocent folks like myself who never used 3rd party tools and yet still get banned.
I would assume that there are more wrongful bans since that fateful day after seeing this post.
Though 3 months have passed, my wrongful ban is still so fresh to me.
I myself don't edit any .ini file but did make a parameter change in BNET launcher that allows me to switch regional server based on instruction provided by Blizzard support. I don't think that caused the ban either.
The flag is likely caused by falsely identifying bot behaviours based on system resources / apps / or whatever that they use to trigger it. I am very sure that there is no human behaviour check in place to further identify if a player truly bot. E.g. it is very very common for a legitimate player to frequently call out the map to see where to go next while playing the game. Social behaviours are also not part of the identification process. It is very flawed in my opinion with such detection in place.
I have since parted ways with Blizzard and will never buy their games anymore since I will not know when I will be wrongfully ban again for something I never do. My money and time is better spent on a company who truly cares for their customers.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
My post ONLY applies to people who were banned but were honestly not using a bot, maphack, or other unauthorized 3rd party software that might be responsible.
Here's the quiz for you:
1) Did you disable DEP, also referred to as the NX bit?
(If you are unsure, do either of these things look familiar to you. If so then you should answer 'Yes')
A] Editing the boot.ini file to show - /noexecute=AlwaysOff
B] Entering in the command line - bcdedit.exe /set {current} nx AlwaysOff
2) If you have DEP disabled, did you then add the /PAE option to enable that?
(If you are unsure, do either of these things look familiar to you. If so then you should answer 'Yes')
A] Editing the boot.ini file to show - /PAE
B] Entering in the command line - bcdedit /set [{ID}] pae ForceEnable
3) Regardless of the above settings, did you enable the LargeAddressAware option?
(If you are unsure, do either of these things look familiar to you. If so then you should answer 'Yes')
A] Editing the boot.ini file to show - /3GB or /userva=
B] Entering in the command line - bcdedit /set increaseuserva
If you answered Yes to any of these options, and you genuinely were not cheating at all, then that's probably what caused you to be banned. Here is a killer link showing that Steam's Anti-Cheat (VAC) also doesn't function with DEP disabled. Keep in mind this is an official support help page from Steam, and if you do some Googling you can see many forums topics about VAC issues being resolved by re-enabling DEP:https://support.steampowered.com/kb_article.php?ref=2117-ilzv-2837&l=english
Obviously all of this is VERY easy to test. It doesn't matter what version of Windows you are on. If you don't believe that this could be the culprit, then instead of replying to this thread with the expected insults, go ahead and disable DEP and PAE for a full gaming session or two. If you survive a week afterword or through the next banwave then you are truly a brave and courageous individual and I will bow down and worship you.
The PAE portion is important as well. It seems to cause its own set of problems. From my research, this appears to have actually been what may have caused those WINE users to be banned in 2012. Look at the "HOWTO: Run Diablo III on a 64-bit machine" section, Diablo doesn't play nicely when PAE is disabled: (Reaper of Souls) https://appdb.winehq.org/objectManager.php?sClass=version&iId=29952 and (Diablo III) https://appdb.winehq.org/objectManager.php?sClass=version&iId=25953.
And finally, for anyone who is experiecing the slow loading and freezing issue while trying to open your inventory screen, you are probably using a 32-bit operating system. If you add the /3GB option it completely resolves this problem. However, it's not actually fixing the problem by allowing Diablo to use more memory, because I don't even think Diablo is LargeAddress aware, but it re-maps the memory and circumvents a bug in Diablo's engine that was introduced in Patch 2.4: https://www.reddit.com/r/Diablo/comments/4jz6qb/fix_for_those_affected_by_inventory_screens_that/
I play on a Mac OSX but was still wrongfully banned on 14th June 2016. Just checking back here to see if there are more innocent folks like myself who never used 3rd party tools and yet still get banned.
I would assume that there are more wrongful bans since that fateful day after seeing this post.
Though 3 months have passed, my wrongful ban is still so fresh to me.
I myself don't edit any .ini file but did make a parameter change in BNET launcher that allows me to switch regional server based on instruction provided by Blizzard support. I don't think that caused the ban either.
The flag is likely caused by falsely identifying bot behaviours based on system resources / apps / or whatever that they use to trigger it. I am very sure that there is no human behaviour check in place to further identify if a player truly bot. E.g. it is very very common for a legitimate player to frequently call out the map to see where to go next while playing the game. Social behaviours are also not part of the identification process. It is very flawed in my opinion with such detection in place.
I have since parted ways with Blizzard and will never buy their games anymore since I will not know when I will be wrongfully ban again for something I never do. My money and time is better spent on a company who truly cares for their customers.