Considering that the employee was fired and the complicit players were banned, I think it was a very severe punishment.
Oh. No.
They could easily get him in some legal trouble if they wanted. Breach of contract. Damages to reputation.
Also, if they are mean about it, they could send an email to all their gaming connections and blacklist the guy from any gaming job at all.
we’re talking about Gamers™ here. nothing short of prison time and public flogging will satisfy their endless thirst for ethics in gaming journalism or whatever they’re mad about now.
Dude throwing his career away over something so trivial is genuinely insane.
This entire catastrophe is a huge PR hit. There is definitely a case to be made for a reputational damage civil suit.
Confidently incorrect as always.
Should certainly be a permaban for the 3 players that were in discord with the GM.
The bear and DK appear to be innocent.
plaintiff, what is your client seeking damages for?
well, some nerds on our game’s official forums are “super mad” at blizzard now, and they’re not actually unsubbing, but some of them are thinking about it. so, uh, a million dollars?
Blizz doesn’t need to do anything, its not even about the gaming industry alone, he torched his job in IT, period. You don’t mess around in Prod. You especially don’t do it in a way that causes reputational damage. He blacklisted himself.
I don’t think you can unring the bell–Trust is already broken. It’s coincidental that the only time this has ever happened is when the community found out before Blizzard? Or that it was disclosed by the community before Blizzard disclosed it. It brings into question, regardless of actions and reassurances, if it has happened in the past.
Streamers and RWF teams already get advantages and attention that the regular players do not, there are multiple examples of this. This latest action brings into question just how much of an advantage they are getting behind the scenes.
It’s a girlfriend caught cheating who is telling you that it was only one time and it won’t happen again–The trust is already ruined. Now resentment sets in.
We can go through the threads and have evidence of players dropping subs because of this incident. That is a civil damages case, whether yall want to admit it or not.
Naturally Blizzard would not go after small fry like this in such a way…I am just saying they could.
feel free to review all the logs out there and find other cases. it’s obviously common, so it shouldn’t take you long. right?
Christ, Pyri. This is some oblivious thinking here.
You have evidence of players dropping their subs, or players posting on the forums saying they’re going to drop their sub? Pretty big difference.
Confidently incorrect.
Why didn’t blizzard fire him over the weekend ![]()
I love the idea that lay off happy Microsoft wouldn’t be looking for any excuse to lay someone off. And it was only because of the noble activities of the community that this was brought to light, because blizzard definitely doesn’t have any of the auditing or controls that any other big tech company does no Siree
The fact that a PR statement uses the wording, “we are confident that this was an isolated incident”, along with the fact that this arose from pure community uproar, makes me very confident that this is not very isolated at all. Do I think it happens all the time? No, but I do believe this happens more than Blizz wants people to think, based on how nonchalantly this occurred.
…Naturally I do not have proof they dropped sub. And I dont need that proof, because all I am positing is that it could happen.
remove the stolen valor titles on the augs account while you’re firing the employee guy
she didnt play mop cms and has the mistwalker title because her ex husband migrated a character of his onto her account. her entire personality is a larp and she has a new story every expansion on how she isnt boosted.
I do have a question about this. So obviously we knew about this because of the public log, but did Blizzard do a full review of internal logs of this employee to determine whether he did this in other keys and were those runs invalidated? Has blizzard also began reviewing all internal logs to determine if this employee is the only employee to misuse their power like this?
What was your belief of this occurring before the incident? Zero right? Probably because it doesn’t happen and because it was an isolated incident.