[PSA] About being Dev Struck after Dev Striking a Dev

[Radar_X]

Howdy, captains!

We would like to clarify the situation that was recently brought to everyone’s attention – with a strike to the division of AcePickles, GrizzlydamsxL and knavbot. As the strike sent according to the current rules happened shortly after this division dev-struck a WG team member in battle, and as the strike execution seemed questionable to many of you, we conducted extensive internal investigation. Here are the results:

1.The strikes sent to players AcePickles and knavbot were done in error and will be removed. We believe there is an opportunity to learn and improve players experience in the future. We will continue to look internally at workflow improvements. We are sorry for any confusion this caused for AcePickles and knavbot and hope this has cleared up any concerns they have surrounding this event.

2.The strike sent to player GrizzlyadamsxL is correct, but was not caused by behavior in a battle with the WG employee. In previous battles over the previous week this player used several direct, and quite heavy insults against other players. We cannot expose the chat logs due to our privacy policies and the offensive level of some words used, but if GrizzlyadamsxL wants clarification on this, I will gladly talk to him in NA forums DM.

3.However, having a chance to study a lot of chat logs within this case, we willI ask many other players to be more polite to each other. We all are perfectly aware of strong emotions that naval battles in WoWS can cause, as we play the game and are as passionate about it as you. But regardless of some player’s efficiency and situations in battle, we all should contribute towards a healthy and mature community. I think WoWS players deserve this.

Thank you, and fair seas!

[Gin_Blossoms]

Thanks for the feedback.  Perspective is reality...what one person types can be interpreted and reported from a completely different perspective.

[Guest]

A useful reminder to all, that being dev struck is part of the gaming experience, part of the fun, and being told, "enjoy" is a legitimate, non offensive, salute, in line with the expectations of the game.

(It does come across as half hearted, mean back tracking, with the harsh treatment of Grizzly - and Pulicat -. An apology isn't an apology if incomplete.)

[212thAttackBattalion]

Good to hear that this has been resolved quickly and efficiently and the strikes removed... sending a cheeky banter message when dev striking an enemy is commonplace in WOWs and isn't all that bad... going "o7" , "oof" or "Boop" or something similar is just friendly banter and most people take it in stride.

[EpicLeveler]

Thank you gor explaining and admitting the mistake made with the two being associated with the player at hand. 

I would, however, like to question whether or not the player at fault would have been reviewed had he not been in this situation in the first place (ie. Dev struck a dev and make a snyde comment).

With you coming out and saying this radar, I hope this means that wg will have more employees dedicated to combatting toxicity in the community and that personal grudges from wg staff, mods, and CCs dont directly affect whether a person is put under review, but rather consensous from multiple sources warrenting a review.

Just my two cents though.

[Shigure_DD]

This really dose come down to people not knowing if the person in chat is joking around or not.. sometimes I take getting  something said to me after getting dev struck as a joke sometimes I don’t... I am a DD player I had someone going off on me for not spotting/capping vs 3 radar ships and a gun bote dd when he was hiding behind a island. This is a game we play for fun let’s have fun and not get toxic about people trying to have fun playing the game they like.

[Forum_Troll]

1 hour ago, Radar_X said:

Howdy, captains!

We would like to clarify the situation that was recently brought to everyone’s attention – with a strike to the division of AcePickles, GrizzlydamsxL and knavbot. As the strike sent according to the current rules happened shortly after this division dev-struck a WG team member in battle, and as the strike execution seemed questionable to many of you, we conducted extensive internal investigation. Here are the results:

1.The strikes sent to players AcePickles and knavbot were done in error and will be removed. We believe there is an opportunity to learn and improve players experience in the future. We will continue to look internally at workflow improvements. We are sorry for any confusion this caused for AcePickles and knavbot and hope this has cleared up any concerns they have surrounding this event.

2.The strike sent to player GrizzlyadamsxL is correct, but was not caused by behavior in a battle with the WG employee. In previous battles over the previous week this player used several direct, and quite heavy insults against other players. We cannot expose the chat logs due to our privacy policies and the offensive level of some words used, but if GrizzlyadamsxL wants clarification on this, I will gladly talk to him in NA forums DM.

3.However, having a chance to study a lot of chat logs within this case, we willI ask many other players to be more polite to each other. We all are perfectly aware of strong emotions that naval battles in WoWS can cause, as we play the game and are as passionate about it as you. But regardless of some player’s efficiency and situations in battle, we all should contribute towards a healthy and mature community. I think WoWS players deserve this.

Thank you, and fair seas!

About point #2.  Let us be honest here.  If your employee had not gone full nerd rage, those logs would have never been read.  You are digging to save face.  All three had the same exact penalty leveraged at the same exact time.  That means they were all given for the same reason by the same person.  You decided to dig through some chat logs to make it seem like it wasn't done in the way it was.  That is manipulating the truth.  Not all of us are stupid enough to just eat that whole sale.  If you want to up hold the penalty based on that, fine, I get it.  But, to say he had his penalty imposed because of his previous interactions is straight up lying.  

[Sovereigndawg]

[Akeno017]

1 hour ago, Radar_X said:

3.However, having a chance to study a lot of chat logs within this case, we willI ask many other players to be more polite to each other. We all are perfectly aware of strong emotions that naval battles in WoWS can cause, as we play the game and are as passionate about it as you. But regardless of some player’s efficiency and situations in battle, we all should contribute towards a healthy and mature community. I think WoWS players deserve this.

I feel that this is to take away from this situation now, a little battle banter is fine but sometimes people go too far.

[Turbotush]

Just had a Ranked battle where our CV had 9 battles total in there CV.  As the battle started he then froze and clamed that his "UI" was bugged and then proceeded to sit in the back to await a inglorious death.  You don't want to know the language I used to describe my displeasure of the situation, but I have to tell you it was directed at WG and the CV player in equal measure.  I'm just glad I didn't use it in chat.

[Crucis]

12 minutes ago, JonnyFreedom said:

About point #2.  Let us be honest here.  If your employee had not gone full nerd rage, those logs would have never been read.  You are digging to save face.  All three had the same exact penalty leveraged at the same exact time.  That means they were all given for the same reason by the same person.  You decided to dig through some chat logs to make it seem like it wasn't done in the way it was.  That is manipulating the truth.  Not all of us are stupid enough to just eat that whole sale.  Sure, if they guy is volatile in chat, then that is one thing.  But to say he had his penalty imposed because of his previous interactions is straight up lying.  

This bugs me too, JF.  Using the initial interaction between a player and a WG employee in battle as an excuse to go back and read chat logs just to drag up an excuse to punish the player anyways is just plain wrong.  Sounds more like CYA than any sort of real justice.

@Radar_X

[Guest]

10 minutes ago, Crucis said:

This bugs me too, JF.  Using the initial interaction between a player and a WG employee in battle as an excuse to go back and read chat logs just to drag up an excuse to punish the player anyways is just plain wrong.  Sounds more like CYA than any sort of real justice.

@Radar_X

@Pulicat also recieved a strike, relating to this matter. Of course, the OP does not mention it.

[Nachoo31]

Talk about being nice to each other. Don't come into the match and blare out, THIS IS A LOSS, because you have the Match Maker up.  Just made some dude eat crow when he mentioned 4 people on our team had a 30% win rate.  We zero'd out the other team.

[Radar_X]

12 minutes ago, Crucis said:

This bugs me too, JF.  Using the initial interaction between a player and a WG employee in battle as an excuse to go back and read chat logs just to drag up an excuse to punish the player anyways is just plain wrong.  Sounds more like CYA than any sort of real justice.

@Radar_X

From my understanding, when someone is reported for chat violations there can be a review of recent chat logs especially if it provides further context.   In this particular instance, this player violated our game guidelines pretty repeatedly in the past and action was taken on that.    If a violation of some kind is brought to our attention, it's pretty hard to turn a blind eye.  

[Radar_X]

8 minutes ago, LoveBote said:

@Pulicat also recieved a strike, relating to this matter. Of course, the OP does not mention it.

If you have general concerns about our moderation policy, please drop me a PM.  I'm very happy to discuss it!

[Guest]

7 minutes ago, Radar_X said:

If you have general concerns about our moderation policy, please drop me a PM.  I'm very happy to discuss it!

I will do, thanks for the invitation. Pulicat is an invaluable member of our community.

[BrushWolf]

20 minutes ago, TRACER___ said:

I was issued a forum warning related to this today. I made a joke about it, and technically I did violate the rules of going "off topic", but still I feel the punishment was worst due to the subject.

In a post titled "CV bug" I replied with

"Is it the bug where you dev strike a WG employee rusults in an account strike?"

In not more than 2 minutes my post was deleted and my first ever video game or forum warning was waiting for me in my inbox.

Hindsight, my crap humor was not worth my first (permanent??) warning.

I wish I could give you two plus ones. The first for not debating the mark and the second for having a sense of humor about it, good for you sir.

[Crucis]

11 minutes ago, Radar_X said:

From my understanding, when someone is reported for chat violations there can be a review of recent chat logs especially if it provides further context.   In this particular instance, this player violated our game guidelines pretty repeatedly in the past and action was taken on that.    If a violation of some kind is brought to our attention, it's pretty hard to turn a blind eye.  

Radar, it is still a crappy policy because IN THIS INSTANCE it looks a lot more like CYA than it does anything else, because it seems to me that the situation was instigated by a butt hurt WG employee who get dev struck.

[Dasha_Eyes]

45 minutes ago, JonnyFreedom said:

About point #2.  Let us be honest here.  If your employee had not gone full nerd rage, those logs would have never been read.  You are digging to save face.  All three had the same exact penalty leveraged at the same exact time.  That means they were all given for the same reason by the same person.  You decided to dig through some chat logs to make it seem like it wasn't done in the way it was.  That is manipulating the truth.  Not all of us are stupid enough to just eat that whole sale.  If you want to up hold the penalty based on that, fine, I get it.  But, to say he had his penalty imposed because of his previous interactions is straight up lying.  

Truth!

12 minutes ago, Radar_X said:

From my understanding, when someone is reported for chat violations there can be a review of recent chat logs especially if it provides further context.   In this particular instance, this player violated our game guidelines pretty repeatedly in the past and action was taken on that.    If a violation of some kind is brought to our attention, it's pretty hard to turn a blind eye.  

This is a great point of view!   (if it works this way, I like it.)

The problem of course is that the WG employee manipulated the system in order for this person to receive a strike. (dishonest)

 

This screams of retroactive justification, rather than a sincere apology.

[Whisky_A_Go_Go]

10 minutes ago, Crucis said:

Radar, it is still a crappy policy because IN THIS INSTANCE it looks a lot more like CYA than it does anything else, because it seems to me that the situation was instigated by a butt hurt WG employee who get dev struck.

That.

What's more, what are the odds that the strike for things of the past came down at essentially the exact moment that they were platooned and Knavbot one shot Gneisenau013?

What's more, you mean to say that a strike applied to one person for things he did a ways back are somehow magically teleported over to guys he was platoon-mates with after the fact? I mean, I've heard of guilt by association, but that's a bit much.

[cavscout1739]

11 minutes ago, BrushWolf said:

I wish I could give you to plus ones. The first for not debating the mark and the second for having a sense of humor about it, good for you sir.

I covered you.

[Forum_Troll]

41 minutes ago, Radar_X said:

From my understanding, when someone is reported for chat violations there can be a review of recent chat logs especially if it provides further context.   In this particular instance, this player violated our game guidelines pretty repeatedly in the past and action was taken on that.    If a violation of some kind is brought to our attention, it's pretty hard to turn a blind eye.  

The reason he was even investigated was because of what your employee did.  You found other evidence because of the false statement.  It is like a police officer pulling you over for an illegitimate reason and finding drugs.  When it comes out the search was un-warranted, they throw out the case because it was found under illicit means.  You literally went on a witch hunt to try to vindicate your staff member, which to me is unacceptable on all levels.  Why do you guys have such a hard time delivering decent customer service?  Almost every week WG has some CS Snafu for the last month.  Just boggles my mind why things are handled so freaking poorly. 

[Turbotush]

WG, please fix the crapy MM.

Crickets...….

WG, please help to make Ranked battles less of a cancer fest.

Crickets...….

WG, CV's suck in this game, instead of balance how about we make them less of a one shot threat.

WG employee gets one shot div struck by a CV and is buthurt so warnings get justified for reasons that look like retaliation.

I don't think you all at WG understand how this is making you look to us.

[dmb47]

"We investigated ourselves and found ourselves to be completely right in our investigation of ourselves....."

[neptunes_wrath]