Solidfury7 - Staff Report: Enforcement Action Taken - Detective Google

Solidfury7 - Staff Report: Enforcement Action Taken - Detective Google

What’s your BYOND key:

Solidfury7

Round ID:

28547

Your character name:

William ‘Jester’ Crimson

Their BYOND key:

Detective Google

What are you reporting?:

Enforcement Action Taken

Description of the incident:

Anyway, after many incidents in the past and the new(er) policy that logs are not public. I decided to take matters in to my own hands. I am including the following:

The chatlogs from this round

Transcript log

Video recreating the incident with 0 interruptions from Sawyer, the XO, CL, and excluding all the times she resisted, broke free and ran around, and excluding the stabbing.

I had added the following phrase “THIS IS WHERE THE LOG STARTS” to allow people and staff to see the raw chatlogs as seen in game. Beyond that addition, everything is the same. I will also be including time stamps used from a recorder which will show the timescale of handling the non-compliant colonist, this of course will not include logs over radios, speaking to staff nor actions such as the colonist search, resisting non-stop and having to be tazed.

As for what specifically happened. I woke up and was needed at CIC almost instantly, I found a colonist who I greeted and told them I’d need to disarm them and search them before I could let them in, as it is a navy vessel. They refused. Under law, they must be processed and disarmed. I told them this. They refused to disarm (Failure to Follow Procedure, 10 minutes) and they were refusing to be searched (5 minutes). They also resisted arrested, if I wished to add this, after being given multiple times and trying to leave the scene when told to halt.

They called for help from Sawyer, ICly I had no clue who it was, so I move quickly, relocated to a secure spot and began the search. Sawyer (CMB Synth survivor) then agreed that the survivor should comply with me, after they inferred I was sexually assaulting them/kidnapping them. I then processed them, checking each bit of the kit before redressing them, before moving to update their security records (so they are on the MP database) but I ran in to an issue (which I noted in LOOC) and gave up after a minute. Once this was done, I relocated to the CIC, as I needed to see if the XO was willing to give any further access. Upon arriving XO and CL were asking what was going on. Even for the CL and XO, it became apparent that the survivor was unhinged, so I gave the survivor basic IFF. I stopped grabbing them so I could untie them, they then proceeded to run around the CIC for around a minute or so. Everyone present telling them to stop. XO grabbed them, I then grabbed them again, took them outside the CIC (During this whole interaction, I’m also replying to ahelps (and sending them extracts from marine law they couldn’t find), speaking in game and handling the prisoner) and when I release the survivor, he immediately started stabbing me, breaking my skull.

That is the interaction I was noted for. Malicious Compliance. Here we are again.
Now, the handling party, Detective Google, clearly has limited experience in marine law and SoP, as I had to direct them to the laws regarding survivors being processed. Despite being corrected, they still applied a note which is factually incorrect, despite handing them the specific laws. Civilians are not allowed weapons during green alert, they also must be searched and given IFF. This is all including the fact they resisted the initial arrest, and spammed resisting for the whole duration of the processing (which slows things down), if I wished to apply that additional charge.

Now, based on my video logs, recreating the scene with 0 interruptions, no chatting and skipping the confusion which was a minute or so with the sec-records, it took 7:30, from a pure mechanical standpoint, from arrest, to processing, to release. This excludes all conversations with Sawyer, the prisoner, XO, CL, the staff member and the constant resisting from the prisoner, which usually resulted in me having to stop my actions to stun the colonist again. The actual time the prisoner was released was 6 minutes later than the “zero words” run, which excludes them running around CIC and of course, the sec-console issue I had (and leaving my ID in the cic machine oops). So, let’s say they are each a minute each. Thats 4 minutes later than the 0 words run with 0 interruptions from 3 seperate parties and a resisting prisoner.

Is that malicious compliance? God, forbid I speak to other players and staff questioning me. This was handled so poorly by the staff member that I was actually frustrated from maybe the 2nd message because from the loaded language of the staff member, I knew that I’d have to waste my time explaining all of this on this because it was clear they already had their mind made up from the get go, and then they didn’t do their due dilligence in regards to marine law, and when told the exact sections of marine law, and the crimes they were guilty of which are more than 5 minutes, they ignore it and apply the note with incorrect information.

An armed civilian on a navy ship doesnt want to be searched, keeps breaking cuffs, refusing to be processed or hand over a gun and accusing me of sexual assault before stabbing me to critical and breaking my skull after I release them. And I’m being told it was malicious compliance. I’ve nothing against the staff member, but my god, this was sloppy.

Evidence:

Evidence and formatting will be attached separately,

Edit: Staff deleted my evidence logs. I wish I was joking so I’m having to edit this *AGAIN *because forum tool is buggy (worked this time but including secondaries in case it breaks again). Luckily, I had a backup for the backups. Fortunately, I am skilled in countering the 1984. So here is my NEW backups.

1: Video Recreation - https://youtu.be/_zFayPwpZ0U
2: Transcript:
Transcript_Log2.txt (10.4 KB)
2: BACKUP OF BACKUP - Transcript: https://litter.catbox.moe/3qgy3tju0nuzp4r3.txt
3: FULL CHAT LOGS:
Log1.html (777.4 KB)
3 - BACKUP OF BACKUP: FULL CHAT LOGS: https://litter.catbox.moe/osh7v468jj6qbekk.html

4: Note details - qAhNu1csyc

Here we go. Full transparency. I’ve got a few other pieces of evidence but they cover the same things, I may include them when I have time. But yes, being noted for taking longer than 5 minutes searching, processing and releasing a nutjob is one of the spicier takes I’ve heard.

32 Likes

msedge_ij62QXX2hA

After reviewing the definition of Malicious Compliance as enforced by staff,(attached above), and comparing it with the reason provided in the staff members note. I believe it’s necessary to highlight a significant misapplication of the rule enforcement here.

According to the official rule definition:

“Malicious Compliance is using IC Military Law to impose excessive punishments, make an arrest on a technicality of someone non-disruptive who is acting in good faith, or causing intentional delays in the jailing and appealing process.”

In this case, the individual in question was:

  • Armed while on a Navy vessel as a civilian during green alert (which is explicitly disallowed).
  • Refused to disarm
  • Refusing to be searched.
  • Resisting arrest near constantly prior to the arrest and during the whole interaction , delaying processing.
  • Making outrageous in-character claims (accusations of sexual assault, kidnap).
  • Attempted to flee and later stabbed the CMP, breaking their skull.

This cannot reasonably be considered “a non-disruptive individual acting in good faith.”

A mechanically “ideal” recreated scenario, confirms the whole process, with no resistance or interruptions, no talking and no roleplay, took roughly 7:30 minutes. The actual situation only took a few minutes more, hardly an excessive or punitive delay, when you account for interactions of 3 different parties, the resisting arrest and anything I said or misc. moments.

I’ve included this separately, just for clarity.

14 Likes

Hello there, @SolidFury!

The primary reason for the warning was that the failure to complete the processing within a certain period of time. However, upon reviewing Marine Law and SOP, we couldn’t find any clause that mandates processing must be completed within a specific timeframe. Of course, there are situations such as appeals that require timely handling, but there is no rule stating that every processing must be completed within 5 minutes. While there was once a rule suggesting a 10 minute limit, it is no longer in effect. Therefore, there is no violation of Mandatory Obedience.

When it comes to Malicious Compliance, we discussed this matter for a long time, and it was a difficult decision to make. Ultimately, the majority of Management believes that the delay in the processing was not made in good faith and that the situation could have been handled better. However, considering that both parties were injured as a result of the fight, and that the extended ahelp chat between staff and Crimson contributed to the delay in the processing, therefore we have decided to remove the Warning and issue a Note instead for record keeping. I will also talk to Detective Google and inform them about this, however, we will take no action against Detective Google.