RE: Possible explanation for the Linux bans
by gdan on Sunday August 19th 2012, 19:02
I don't think so, however, I was banned about a month ago with the same result.
I've given up on trying with Blizzard, and it seems there is no support if your account is suspended. Just because "everyone" is not being banned means that it is most definitely not Wine and Linux at fault - and we are cheaters...
I was running PlayOnLinux, since it configured it somehow and I had no issues with it after trying with a few different patched Wine versions.
This was my startup, after the WINEPREFIX commands:
setarch i386 -3 -L -B -R wine "~/.PlayOnLinux/wineprefix/.wine/drive_c/Program Files/Diablo III/Diablo III.exe" $@
RE: Possible explanation for the Linux bans
by Tom Wijsman on Wednesday September 19th 2012, 12:25
Well, not much people use -L -B -R. I think that one of these might be the cause and would advise anyone not to use any of them. Can you actually explain to me why you use each parameter of them?.
---
I wouldn't advise anyone to attempt to cancel out which parameter it would be, as you stand a high chance getting banned in the progress. Just saying, using this parameter surely makes the memory act way different; changing the memory lay-out and disabling randomization in essence allow one to breach the memory security.
Nobody should use these, they catch you even if you did not intent to; also, don't copy suggestions for other games to your Diablo 3 shell script, if you don't know what certain things do and just try, this stuff happens.
