I'm going to try to be as thorough as I can here without being unnecessarily specific in regards to things that are said in confidence.

Night of the Incident
Walkers enumerated the events of that night, you can read the OP for that. What happened on our end was, in all fairness a failure of our process to handle potential hacks with screenshares. To this point of the post, I consider fully fair. We should be taken to task if we are failing in the duties we claim to set for for ourselves.

To the point of my saying "This conversation is over", I wasn't insinuating that the whole incident was over and not to be discussed or dealt with further. In the full text of that dm with Walkers, the argument had merely become circular and no new points were being made. At no point were we going to ban Kaph because of something like being offline on Steam. Many points have been made about what justifies as "real life", or legitimately not seeing whispers, etc.

We expect and encourage players to come to the forums and raise hell if we're not doing our jobs. We may not always agree what our jobs are perceived to be, but on this I think it was 100% fair for this to be brought up. However the timespan on dealing with this situation is somewhat unique ---


Handling the Screenshare
Quite simply, there are personal reasons why we didn't hunt down Kaph with the force and vigor that seems to be prevalent here. Not all players are the same and not all incidents are the same. Prior to this incident, we have usually followed on on hack reports to the best of our ability in the time that we could. This may not be satisfactory for some, but one thing we will not be doing is banning people general suspicion, without proof or data. Other servers do this, we will not be.

Kaph was going to be screenshared once he got back to us or logged on to Loka within 24 hours. In regards to how the log-off situation happened, much has been made of that as well. Quite simply, we tried to throw Kaph off the trail by saying "nvm, it's fine." The reasoning is that we are fully aware of self-destructing clients and we weren't confident that we could prove he was hacking at that point. In the past, we have not historically hunted down people screenshares immediately unless we see something blatantly obvious that we feel confident we can catch then and there. These kinds of hack reports are generally followed by extremely close scrutiny of the player so as to catch him/her in the act and do the screenshare.

/freeze Feature and the Future
Simply put, we did not possess at that time a /freeze feature at the time of this incident. This feature now exists, is very obvious, and is our due diligence on warning a player not to log out which is far better than a very subtle, and frankly easily-missed whisper. Further, because now have /freeze, logging out if /frozen will result in a minimum 1 MONTH BAN. This was the missing piece of the puzzle that we failed to have ready for this instance. Players can no longer effectively use "ignorance" or otherwise to claim to miss a screenshare request.

The Witchhunt
To reiterate what was said earlier, Mag and I have no issue with what I think is the main crux of this thread -- to call out the admins for failing to tackle this incident in the time or manner than it should have. It's fair, it's what we want you guys to do, it helps the server, and it helps us all.

What I, personally, have a big problem with is the usage of this incident to seemingly hunt Kaph down for justice at a level of fervor that we haven't really seen before. There have been understable situations in our (poor) handling of these things in the past, but there's no shortage of what appears to be a sustained effort to ensure Kaph goes down. These two incidents are intertwined because they involve Kaph, however the real meat here is ---