Dark
Protector of Blanky
- Joined
- Oct 28, 2018
- Messages
- 141
- Thread Author
- #1
Today, at around 14:10 BST, I was notified by Asimo, an OTA member on how an OTA team died in the sewers. As is standard procedure, Asimo did not act on it as there is no confirmation from any of the overwatch leads or an otherwise leading figure (ordinal). I was considering to join the server, hoping that it will be swiftly voided without me, after Asimo tells the admins he will not act on it. But in the end, it seems like there was no way to avoid the incoming damage so I decided to the join the server.
Upon joining, I was flooded with questions and messages, cops were locking off the city and the socio-status was on marginal. As was decided by spine and me, my scanner lowered the socio-stability to blue and attempted to instruct the cps that this is not in-character over ROOC. Most officers decided to not go with this and wanted to take it IC. Due to the death of an event OTA at nexus ingress, I flagged on my OTA to handle the situation forcefully and IC, hoping to prevent further confusion and a rampage by civil protection. I got on, and the first thing I saw was three officers looting the remains of the dead OTA, the only thing that was left on the body was the pulse rifle. We began containing the situation, eventually retrieving the lost items and also lining the cops on the wall, tied. We searched them, and after a long while, let them go.
This is how I reacted to it in-game.
Now onto the actual issue.
I asked Asimo to find out who is leading the event and who is online. This is the /printstafflist at the time:
[SERVER_ADMIN]: Maroon, Memesky, Mulky Humberton [TRIAL_ADMIN]: Hades, McTiddies!, Uranio
Mulky allegedly was the leader of this "event".
Here is everything that went wrong:
- Staff did an OTA event without consulting any overwatch lead.
- In this event, 5 OTA died in the sewers for an unknown reason. I am still unaware why anyone would send 5 event/NPC OTA into the sewers so I presume there is no way to justify this.
- These /events were made:
- Staff gave themself OTA characters without OTA lead authorization.
- Event OTA kept radioing on tac-3 channel without an understanding on how and when OTA communicate (Meaning they did not even care enough to read the guide), creating a possibly bad image for the faction as well:
- Event OTA had a wrong name format and did not specify the sector, meaning this was a very low effort character and event.
- Dispatchers reacted to the situation IC, I am not sure how they reacted, but that most likely lead to the reaction by CPs.
This entire ordeal was completely unwarranted and the whole situation was preventable if staff would communicate with leads more. At the same time, the execution of the event was so poor it only lead to a bad image for the factions involved and a lot of headaches for the leads.
I ask the responsible staff, how did you expect us to react? If we were to take this whole thing in-character, it would have just ended with needless PKs, NLRs and many more problems for staff to handle. The fact that I decided to void it instead of proving your decision making wrong resulted in me having to deal with the faults of the staff team, instead of dealing with my own faults. This means that I likely have also not reacted appropriate enough in this situation, but that excuses nothing.
Please add these people to the thread, as I believe they are involved:
@Mulky
@Uranio
@McTiddies~!
@Maroon
@Memesky
@Hades
@Asimo1234
@Spine
@Gyrann
@Dingo8MyBud
@Ron Goodfella


If you disagree to my claims and the final conclusion turns out to be negative, I am willing to re-do the event in the exact way it happened in order to display what consequences this event would have had if taken in-character.
Upon joining, I was flooded with questions and messages, cops were locking off the city and the socio-status was on marginal. As was decided by spine and me, my scanner lowered the socio-stability to blue and attempted to instruct the cps that this is not in-character over ROOC. Most officers decided to not go with this and wanted to take it IC. Due to the death of an event OTA at nexus ingress, I flagged on my OTA to handle the situation forcefully and IC, hoping to prevent further confusion and a rampage by civil protection. I got on, and the first thing I saw was three officers looting the remains of the dead OTA, the only thing that was left on the body was the pulse rifle. We began containing the situation, eventually retrieving the lost items and also lining the cops on the wall, tied. We searched them, and after a long while, let them go.
This is how I reacted to it in-game.
Now onto the actual issue.
I asked Asimo to find out who is leading the event and who is online. This is the /printstafflist at the time:
[SERVER_ADMIN]: Maroon, Memesky, Mulky Humberton [TRIAL_ADMIN]: Hades, McTiddies!, Uranio
Mulky allegedly was the leader of this "event".
Here is everything that went wrong:
- Staff did an OTA event without consulting any overwatch lead.
- In this event, 5 OTA died in the sewers for an unknown reason. I am still unaware why anyone would send 5 event/NPC OTA into the sewers so I presume there is no way to justify this.
- These /events were made:
Code:
*As the day passes by; and the horde grows thicker—sounds of gunfight can be heard down below the sewers - distinct vo-coders acting upon the garage. It seems they have finally taken action.*
*It was all going well—until...*
*Multiple Pulse Gunshots can be heard ringing across the sector—screams; followed by distant yells - it seems there are a few survivors afterall from the whole ordeal.*
- Staff gave themself OTA characters without OTA lead authorization.
- Event OTA kept radioing on tac-3 channel without an understanding on how and when OTA communicate (Meaning they did not even care enough to read the guide), creating a possibly bad image for the faction as well:
Code:
[OTA-TAC] S10.S#-OWS.GHOST-52: "Repeat, Status RED. Ground-Team has lost control in Storm-System, GHOST is Autonomous, GHOST is Autonomous."
Code:
S10.S#-OWS.GHOST-54 says <:: J-just..get me in...ah...we're causing t-too much a scene. ::>
- Event OTA had a wrong name format and did not specify the sector, meaning this was a very low effort character and event.
- Dispatchers reacted to the situation IC, I am not sure how they reacted, but that most likely lead to the reaction by CPs.
This entire ordeal was completely unwarranted and the whole situation was preventable if staff would communicate with leads more. At the same time, the execution of the event was so poor it only lead to a bad image for the factions involved and a lot of headaches for the leads.
I ask the responsible staff, how did you expect us to react? If we were to take this whole thing in-character, it would have just ended with needless PKs, NLRs and many more problems for staff to handle. The fact that I decided to void it instead of proving your decision making wrong resulted in me having to deal with the faults of the staff team, instead of dealing with my own faults. This means that I likely have also not reacted appropriate enough in this situation, but that excuses nothing.
Please add these people to the thread, as I believe they are involved:
@Mulky
@Uranio
@McTiddies~!
@Maroon
@Memesky
@Hades
@Asimo1234
@Spine
@Gyrann
@Dingo8MyBud
@Ron Goodfella


If you disagree to my claims and the final conclusion turns out to be negative, I am willing to re-do the event in the exact way it happened in order to display what consequences this event would have had if taken in-character.
Last edited: