| dyna... LISTEN TO ME!! lol
im not saying that people are getting banned because an AV or Firewall is stopping an incoming ping.. in order for you to be able to even get on battle.net you would have to give D2 full access rights (in and out) therefore (EDIT: SPELLING) anY subordinate D2 process is going to have access to your computer, and your AV or Firewall will not stop it... What i AM saying is that the files that reside in running processes / open ports could be detected by Warden.. and if Warden and Blizz's banning system are one-in-the-same, then it is possible that Warden detects an "un-original" .exe.dll and reports it to the squasher.. but i dont know how blizz handels their banning.. i think it might be computerized, and if it is.. it is possible to be detected for a program that has nothing to do with hacking D2...
and the whole point to my arguement is that you might NOT have to be USING Sh!t.. think about this.... ok you have a list and size of all legit running d2 processes.. Warden scans for any irregularies in either of these feilds.. knowing that you would have to change 1 of them in order to hack.. therefore.. if there are any .exe 's that are "attacking" or "tied to" any legit d2 process, you would get "detected" by Warden. Additionally if there are any game files or any .dll's that are irregular or over/under sized. this would get you "detected".. the whole point is that an AV client or Firewall is going to attach .exe.dll's, the worst possible combo to be detected by Warden, to the open port(s) on your running diablo 2 processes.. and if they are there and Warden is as crude as i and others believe it to be.. people Could and probably ARE getting banned who were NOT hacking. |