Apologies for the delayed reply. This complaint happened to fall near the holidays, we were all pretty busy.
We've decided to uphold this complaint. Let's go through this bit by bit.
Scenario/Adminhelp
Firstly, the actual situation that was ahelped: Nabski made the wrong call here. Taking an ahelp involving someone with an open complaint against you is poor conduct itself (you should recuse yourself in this sort of scenario), but the actual situation was dealt with incorrectly, too. It wasn't unreasonable for the roboticist (SpookyPurpleCat) to make someone who was acting like an antagonist into a revolutionary, especially when ordered to by a security officer, who are generally thought to be an authority on crime/antagonists. Now, receiving an order to do something from security isn't always an excuse to do something, but the point is that the roboticist in this case clearly had sufficient IC reasoning to do what they did.
Nabski said it himself:
[2018-12-18 03:50:05.530] ADMINPRIVATE: ASAY: Nabski/(Gene Ball) "on one hand I hate haku" (Robotics Lab (113, 84, 2))
[2018-12-18 03:50:19.328] ADMINPRIVATE: ASAY: Nabski/(Gene Ball) "on the other I don't really think this is actionable" (Robotics Lab (113, 84, 2))
(source: raw game.log sorted by ASAY, these two lines cherrypicked. link:
https://tgstation13.org/raw-logs/basil/ ... 0/game.log)
Biases
This is when we come to the biggest issue with Nabski's conduct: bias. It wasn't enough that he had an ahelp against someone he knew he could not remain unbiased towards, but he also admitted that he hates the player and didn't think the situation should be actionable. It is doubtful that this situation would have even been pursued further, had Nabski not pursued his grudge. What is interesting is that, even after Nabski found the security officer to be fine with IC reasoning for his actions, he continued to allow the situation with SpookyPurpleCat to escalate, even though the roboticist would have been much less at fault, if anyone, than the security officer in this scenario. Eventually, Spooky was banned for adminshopping, after they pinged us headmins in Discord asking for us to look into the situation.
Adminshopping
In the end, this ban's formal reasoning was adminshopping, but we have determined that this ban isn't valid. Asking the headmins to investigate something another admin did is not adminshopping. Adminshopping is, generally, ahelping until you get the response you wish to receive from an admin, going through several admins in the process, or similar such behavior. What happened here and what adminshopping is are two situations that cannot be equated as equal.
(Disclaimer): While it's not adminshopping, pinging headmins when you disagree with an admin is shitty behavior, and won't do you any favors. If you have a problem with what an admin did, make a complaint. Don't try to start a Discord argument.
Spooky's Ban
This complaint has sort of turned into a weird hybrid of an admin complaint and a ban appeal. Typically, if someone has a problem with a ban, they should
APPEAL FIRST and the complain if they disagree with the ruling the admin makes on the appeal. Otherwise, you get complaints like these where it's just an awful mess. So I'll say this: the ban has expired, and it's just a note now. We have ruled that the ban was invalid, so I will lift the note for you.
In the future, if your complaint revolves around a ban, either
appeal first or risk keeping the punishment.
Verdict
This is not the first time the headmin team has had to talk to Nabski about his behavior. Back during the Hathkar complaint against Nabski, we opted to speak with him privately to ensure that he would be more diligent and careful in his actions.
That being said, the bias, poor judgement, and overall failure to rectify a pattern of poor behavior that Nabski has demonstrated in this complaint and others has reached a critical point, and it will no longer be tolerated.
We have decided to uphold this complaint, and remove Nabski from the administration.