Cyborg delams sm twice with crew friendly laws

Byond Account: Akride
Character Name(s): Luck Nepal
Discord Name: 𝖇𝖇𝖖 π–˜π–†π–šπ–ˆπ–Š 𝖔𝖓 π–™π–Žπ–™π–™π–Žπ–Šπ–˜#8706
Round ID: 19050
Date: 25/02/2022
Griefer IC name: Service Cyborg-934 and possibly Default Android-513
Griefer Byond account (if known): Cybercotlet 2077 (934) and Bobbussus (513)

What happened:

As CE, I am building BSA north of AI sat with an atmos mate when SM leaves nominal status. As I rush to it, I see an engie borg leaving, which I don’t quite catch the name of. After clearing the delam because he’s terrible at sabotage, I go back to building BSA. At that point, I cannot trust AI anymore and when I come across 513 in space near SM, I disable it, because evac has already been called and I’m short on time, so I give myself the benefit of the doubt. (Also as you can see, 934 is titled service. I saw him snooping around earlier but it was clear he was a service bot. I didn’t expect a borg to get respecced just to sabotage, so I killed 513 thinking it was likely him that sabotaged.) I finish the BSA, but as I’m fixing a minor power issue in its own satelite, SM leaves nominal status yet AGAIN. This time I catch 934 red handed, kill it, and clear the delam.


As you can see, he wasn’t antag at all, and sabotaged twice for no reason. Nush, in discord, also mentionned he saw 934 beat up someone for no reason in maints.

I included 513 in this report because I killed him out of doubt, so he might grief patrol me, so I’m including him for transparency.

TLDR : Service Cyborg-934 Sabotaged SM twice in 10 minutes as crew friendly laws, as wall as allegedly murdered someone.

To add to this grief report i as a ghost saw 934 beat up a sleeping atmos tech, but got revived before i got to check it’s laws to ahelp.

This has been dealt with- thanks!