Urytion - Staff Report: Violation of Event Protocols - Ro3ger

Urytion - Staff Report: Violation of Event Protocols - Ro3ger

What’s your BYOND key:

Urytion

Round ID:

23557

Your character name:

Darrel “Dingo” Sturt

Their BYOND key:

Ro3ger

What are you reporting?:

Violation of Event Protocols

Description of the incident:

I was the XO in this round. The ASO was given an objective as a part of an objective event to “kill the XO”. That’s the event. No other instructions.

To do this, the ASO threw an M15 grenade into the CIC, destroying an OW console, and then when I attempted to run, I was gunned down, and post-death decapitated. I don’t necessarily blame the ASO. He did what he was told by staff. And to his credit, the RP was good, just unexpected.

This round was already a mess before the event. Because staff had encouraged players to go MP, we had more MPs than in two of the squads, so groundside was messy. We had a player break into the brig and try to kill MPs, which apparently wasn’t even part of the event. CIC was two new SOs and me. Groundside only had one medic for most of the round. It was a bad time to run an event.

Event protocols say:
Objective events should bring variety and RP opportunities for shipside roles and should not affect flow of the round. Antag objectives are okay, but should be kept within reason, and allow for non-violent conclusions. Objectives can be given at any point during the round, at round start or in response to a fax or player-created RP. Objectives do not have to be antag, but can be within reason. If you give an antag objective, please make sure it is not round disrupting (ie destroy CIC Command Bubble, Kill all MPs, Ect) and that it can be completed without violence (through lies/bribes/stealth for example).

This event was highly disruptive. ASO threw a grenade into the CIC, which destroyed an overwatch console, depowered the CIC, and killed me and at least one of the SOs. I also don’t see how an objective to kill the XO could possible be non-disruptive (especially on lowpop) and be completed without violence.

I complained to Ro3ger that it was a bad one sided event, which I had no indication I would be involved in (especially being perma’d in). Postround on the previous round he indicated that it would be an MP focused event by telling players he would only run an event if there was enough MPs. He defended himself by saying that:

  1. He triggered an explosion north of the CIC and that should be sufficient warning that I would be targeted. This isn’t warning. Shit explodes all the time. And I did what I’m expected to do in that case. Red alert, sic the MPs on it. Back to running the op.

  2. He hoped the MPs and SOs would be “watching the CIC like a hawk” after the explosion. Everyone was busy because of the clusterfuck of a round. And after the attack, SOs and MPs just fell in line anyway, because anything further would be even more of a disruption to the round.

Evidence:

Mod announce in the following round:

A round of traitors, naomi Sanders and Tao Jian - Objectives failed(Perma the CMP-Failed,Steal Jones-Failed, blow up part of CIC)- Susscess, Ronald Viso - Objective complete (Kill the XO)

I was expecting the SO’s and MP’s to be watching CIC like a hawk AFTER IT GOT EXPLODED

Otherwise you’ll need to check logs and presumably such a high impact event was logged in #event-logbook.

6 Likes

Hello Urytion,

I’m sorry you had an issue with this round and that the event that was ran was not fun for you. However, this was not an “Objective Event” as per the event guidelines, but was rather a “Major Event” since it was applied for and approved (approvals are done by Assistant Managers and up); thus it must be measured along the description for which it was approved.

The event was authorized with the description:

1-8 Players will be chosen from the marines - no CO/XO/MP’s. at least two MP’s are required per 1 traitor to be online to use this event
Each traitor should get one to three objectives. These can be steal X valuable item such as, Jones, Codebook or anything else of high value and only has 1-2 in existance
Kill X target preferably HVT such as the CO or another command member (can be done once or until perma)
Sabotage Power, Sabotage X thing, Blow up X area
Sabotage the entire operation
These traitors can skip escalation steps and griefing rules within reason

While I question the wisdom of this event, it was approved by a member of management, and thus any misgivings cannot be attributed to Ro3ger’s running of the event. That said, the event seemingly did not to go in accordance with Ro3ger’s expectations, and they did make an attempt to reconcile the issues that arose including offering you a respawn. This report against Ro3ger is denied.

2 Likes