#154 - Oct. 13, 2012, 12:32 p.m.
Hi all,
First of all, please accept my apologies for the turnaround time on this matter. As you are aware, this occurred on a Friday evening for us here at ArenaNet, and for hopefully obvious reasons that complicates the timing of things. However, I’ve managed to identify the origin of this problem and have taken steps to correct for it.
While I’m here, I’d like to address a few concerns that have come up in this thread.
First and foremost: we do not issue automatic bans based solely on player reports. All player reports are investigated and bans are issued where appropriate. There is no reason to worry about other players maliciously and falsely reporting you; our policy is to consider hard evidence, not simply anecdotal reports.
Secondly: identifying and solving this problem is a largely technical issue, and involves many confidential aspects of our systems. Please understand that we cannot detail the process that goes into working on issues like this because of their sensitive nature. I apologize that we cannot provide frequent updates, but the fact of the matter is that we face a difficult choice between spending time updating here and actually solving the problem at hand. I trust we can all agree that solving the problem itself should take priority ;-)
Third: the root issue behind this situation was a technical failure. Obviously I cannot go into detail, but the bottom line is that our entirely human reviewed banning procedure was conducted based on corrupt data. We review all evidence prior to issuing account terminations for tampering with the game; in this situation, our evidence was incorrect. I am actively working on improving our procedures to ensure we are less likely to make incorrect conclusions based on faulty data in the future.
Thank you all for your patience and understanding.