Kotov_Syndrome - Staff Report: Enforcement Action Taken - Detective Google

Kotov_Syndrome - Staff Report: Enforcement Action Taken - Detective Google

What’s your BYOND key:

Kotov_Syndrome

Round ID:

31217

Your character name:

Jayden Denoril

Their BYOND key:

Detective Google

What are you reporting?:

Enforcement Action Taken

Description of the incident:

Well, hello everyone. I am a bit unsure if my case can be considered valid under 7th rule of the Staff Report Rules, so if it’s not, feel free to close it.
After the elimination of the last XX-121, my character, Squad Leader at the moment, has received an order to move back to the ship via command announcment. Once at the ship, he eventually finds out that the CO is negotiating with CLF cell leader, which is considered to be the terrorist group as far as I know it. The object of negotiations was a hostage held by CLF. From my character standpoint, there can be no negotiations with terrorists, except for the rarest circumstances, and those were not like that - hostage was barely guarded, and marines were outnumbering CLF about 1 to 10. But either way, despite actively not agreeing with COs decision, my character was following his order to not to shoot at them.
But then, as far as I understood the situation at the moment, my squad spec made his way to the CLF ship or somewhere near it , and they killed him. With hindsight I now know that it was CO who BEed the spec, but, you may have my word for it, I’ve wholeheartedly thought it was CLF who killed my spec. I can swear that I haven’t seen CO BEing pyro and/or moving from her tile at all. As my character seen the terrorist cell killing my squadmate, reacting on emotions, my character started to shoot at their leader, which can be seen on the video attached via discord message link. I am unsure why some shots hit the CO, maybe because I was following CLF Cell Leader sprite with my cursor and he moved up, and because of that the line between me and CLF leader was through the CO and I FFed him, or due to burst scatter, or due to me being pushed, or for any other reason. I can state that I had no intention to shoot CO, hostage, or any other fellow marine.
After that my character was BEed (and I am 100% okay with this), and CLF were killed and then revived in the handcuffs. All the hostages were alive and quite well in the end, and only marine casualties, as far as I believe, were due to BE and OT nades, known for their FF capabilites.
After that I was PMed by said admin, with a question “why did you shoot the CO”, which has surprised me, because at the moment I never knew my shots ever connected to the CO. After some chat with DetectiveGoogle, I’ve been banned for the reason stated in the attached picture. Moreover, admin misinformed me that I’ve only hit the CO, which is not true according to the attached video.
First, I don’t consider this End of Round Grief, maybe it is by the letter, but not by the spirit of the rule. Usually after round ends and marine major stated by the game nothing really happens, some players keep roleplaying, some stay AFK, and round ends quite briefly. In this case there was an event, and, as far as I believe, round end was delayed for the event to continue, and this all happened as part of an event.
Second, I don’t consider my actions grief, since, as stated by the rules, “Griefing is the intent of one player wanting to cause grief or annoyance to other players or the server without a valid roleplay reason”. I had no intent to cause grief or annoyance to other players, I wanted to roleplay my character and play the game. Even if my roleplay reasons for this course of action won’t be considered valid, I still believe this can’t be considered griefing according to the spirit of the rule.
Third, I don’t consider my actions being violation for Rule 2: Roleplay, and reasons why my character has reacted like this are stated in my description of the situation up there, and for the staff members to decide where they valid or not.

Evidence:

Screenshot_1

image

1 Like

Hello. In that video it is indeed clear that you did not “only” hit the CO; I must’ve screwed up my logs query for it to not show up. My apologies for the mistake there.

That being said, that would not have changed my ruling in this matter, and the error is not present in the note on your account.

1 Like

Hi there, was the SEA that tried to keep things calm, and in that video grab you to halt you shooting at the CLF and CO.

I didnt see the BE on the Pyro, but we all heard the shots, the CO bringing the corpse down and throwing it at you then returning to speak to the CLF Commander should have been the biggest clue that hostilities had ended and the CO had control of the situation.

Throughout the interaction it was mostly you and the SO I was trying to calm down from acting in any way to break the negotiations before the Pyro decided to do something stupid and I get the feeling you were waiting for just any excuse to open fire regardless of whether things were going in that direction or not.

1 Like

About the pyro body and the CO, as I’ve stated previously, I can swear that I haven’t even noticed CO moving, most possibly cause I’ve heard some shots or something from the north, and my attention was driven to the upper part of the screen, and also I was eating IRL in the process. As someone stated in discord that I have medhud and must have seen pyro BEed by his HUD icon, most possibly I haven’t noticed it ‘cause it all happend quite fast and pyro’s actual HUD was hidden for the most of the time except for a split second.

UPD: And also yeah, I wanted to start a firefight with CLF for a reason stated in my main message, but I wasn’t actually doing it before I saw my squadmate killed by, as far as I believed, CLF

2 Likes

Howdy, I’ll be denying this report. I watched the video, and to put it simply, there are some times where you just shouldn’t shoot. Look at what it caused. You also didn’t escalate shooting the guy properly.

1 Like