Hi BetterForget,
There were no admins online at the time, and thus could not be approved or denied- etc. Due to the nature of what had transpired that round, and how many were involved- we had to hand out several wave bans for those who attacked other players throughout the logs in wave one in relation to security. The second wave, we reviewed the replay for all mentioned players and are currently accumulating the context prior to the combat and killing of several other players.
Although your particular situation, you may not be directly involved- you were hit by the wave due to attacking security and leading to a critting of that player directly from your actions alone.
Several other players have been wave-banned and we are reviewing the replays further and further to gather information on all sides, but we understand that the Captain was the primary start point for this explosive round.
Players that were marked or hit were hit with an appeal-ban so that we could review their intentions and context for attacking several other crew members on what was a Traitor round.
The round is being combed through for all information that can be gathered and anything correlating to this incident, as the round quality was severely affected and many players were put into an undesirable position from the actions of the self-antagging mob.
For logging purposes, this incident occurred on Round 35746 and you may download the replay at the following link below.
The brig raid was conducted at the timestamp around 01:16:00 in which Cargo had pushed Security and proceeded to kill several players.
From the massive influx of sudden adminhelps flooding the relay, a majority of admins responded and logged on to investigate.
https://cdn.centcomm.spacestation14.com/replays/lizard/2023/10/16/lizard-2023_10_16-14_46-round_35746.zip