Jump to content

Player complaint:Slc97


Recommended Posts

Posted (edited)

BYOND Key:Fire and Glory. (This is your Byond Login/Ckey)

Player Byond Key:Slc97.

Staff involved:Was not ahelped, or at least not by me.

Reason for complaint:Metagaming.

Approximate Date/Time:(UTC+12:00) 19th of September, 1:30-2:00 p.m.


On a malf round, it was fairly early in, when AI F.A.T.H.E.R started hacking APCs, Captain John Sayek, as Slc97, was having an engineer fix APCs in the bridge, when suddenly he decides he wants to do a "little cautionary reset" (almost definitely not exact words, but it was on those lines.), now, I was just an engineering android so I don't know what F.A.T.H.E.R might have said on the other channels, but the only indication that FATHER gave that he might have been malf was a bit of gibberish on the engineering channel at the start of the round, as for the hacked APCs, any number of things could've done it, could've been a strange anomaly messing with APCs for all he was supposed to know.


Upon finding out that his ID didn't work on the interior AI upload because FATHER turned off the ID scan, he didn't press the issue and left, but I'd say it's still metagaming.


I have no logs or such unfortunately but there are several others who saw it, I'm sure one of them will step up.

Edited by Guest
Posted

Evidence was present in the round prior to the APCs. Instances include the AI shocking someone for smoking in medbay, calling them a disturbance or the like. Constantly buzzing out ERRRRRR, constant errors. Ion law, and a few other odd things. And that was just from what I saw in Medical. The acting captain spoke with the CMO and the CE in Medbay, though I couldn't hear most of it. It was off comms where the decisions were reached I believe.

Posted

So, what happened there was the AI had been reported to have been acting weird upon my arrival. It had shocked someone for smoking in medbay and was constantly stating error in it's different communications. I went to reset it, because it had obviously broken a law in harming a crew member, and it had disabled the ID scanner on the upload door. I tried to get the AI to open and it claimed to have lost power. I whispered to an engineer about it and we both agreed that the AI may be malfunctioning due to its past and current behavior. I then gathered the heads of staff, gathered the security team, and then the AI murdered me. The end. I honestly prefer fairytales where everything ends happily ever after, but this works too. Also, Jack. The man's name is Jack.

Posted
So, what happened there was the AI had been reported to have been acting weird upon my arrival. It had shocked someone for smoking in medbay and was constantly stating error in it's different communications. I went to reset it, because it had obviously broken a law in harming a crew member, and it had disabled the ID scanner on the upload door. I tried to get the AI to open and it claimed to have lost power. I whispered to an engineer about it and we both agreed that the AI may be malfunctioning due to its past and current behavior. I then gathered the heads of staff, gathered the security team, and then the AI murdered me. The end.

 

Evidence was present in the round prior to the APCs. Instances include the AI shocking someone for smoking in medbay, calling them a disturbance or the like. Constantly buzzing out ERRRRRR, constant errors. Ion law, and a few other odd things. And that was just from what I saw in Medical. The acting captain spoke with the CMO and the CE in Medbay, though I couldn't hear most of it. It was off comms where the decisions were reached I believe.

 

Alright, sounds a fair bit more reasonable now, since I was cooped up sorting out the shield generator and such, I wasn't there to witness the AI's other actions.


Complaint withdrawn I guess.

 

Also, Jack. The man's name is Jack.

I know that, I have no idea how I got it wrong but I know that.

Guest
This topic is now closed to further replies.
×
×
  • Create New...