Staff Complaint - Killerhurtz, TishinaStalker

[CampinKiller]

BYOND Key: CampinKiller

Staff BYOND Key: Killerhurtz, TishinaStalker (?, not sure if Tish was part of the decision, but they were the admin on at the time)

Reason for complaint: Allowing blatant gank and greentexting from the AI on a malf round, overriding transfer votes for the 'roleplay'

Evidence/logs/etc: I don't have specific logs, I'm on a different computer at the time of writing.

Regardless, let me give the gist of the round. It was malf, and the AI was doing stealthmalf/greentexting, and just hacking APCs and not providing any meaningful roleplay to the crew. Their only interactions with the crew at large were faking two Command Announcements. One was regarding the transfer shuttle being disabled, and I don't recall the other. Borgs were ordered to act normally. The AI had no interaction with the crew besides normal functions and the two mentioned announcements until after the crew transfer was voted for at the 2 hour mark. The shuttle was called because nothing was happening, and passed by a vote of like 20-4. The staff online at the time inexplicably allowed the AI to recall the voted for shuttle. The reasoning Killerhurtz provided was because the AI was doing things, but being sneaky about it (read: greentexting/stealthmalfing), and when everything hit the fan "it would be awesome." Other ghosts who'd been ghosted for a majority of the round noted how the AI had literally not done anything to that point. After recalling the shuttle, the AI told the borgs to kill Yinzr, for some arbitrary reason. Yinzr, Ro'hin'tin, and other officers were armed because of a massive carp invasion trigged by random event, but nobody suspected the AI of any malfunctions. The borgs then proceeded to walk up in Medical where Yinzr was being treated and open fire on the group of people without a word, killing Yinzr, and seriously injuring Alex Toner, Skylar Briggs, and Ro'hin'tin. For some reason this was not considered gank, and was the 'awesome roleplay' the staff promised. Shortly after this, the AI vented its core and rushed the self-destruct mechanism, and at one point considered venting the entire station. At the 2:30 mark, a crew transfer passes again, and is again allowed to be recalled by staff.

The fact that this blatant gank and greentexting was allowed, and even promoted as "awesome" by staff is laughable. If the new standard for malf AI is AIs that do nothing until suddenly ordering people to be killed, then the gamemode needs to be axed.

Additional remarks: N/A

[Skull132]

I would like the view from Killerhurtz while I go over what happened in the round.

Note that recalling the shuttle is a mechanic given to a malfAI, and as such, they can use it as they see fit. However, if they're stealthmalfing and doing fuck-all until the kill orders start flying, then regardless of whether or not they recall the transfer shuttle, it's bad roleplay and bad antagging.

[SierraKomodo]

I'd like to mention that TishinaStalker already spoke with Killerhurtz about this incident following the round. This is what Tish told me afterwards:

 

Got everything straightened out with Killer. What was going on is that he wasn't exactly understanding the concept of stealth malf. After I explained that the AI quietly hacking until being ready to call Delta is the equivalent of a changeling eating protohumans, then he understood, and said he'll keep that in mind for the future.

[TishinaStalker]

I was playing League of Legends last night while on the server. I was not part of the decision process and instead found out after the fact. I had a chat with Killer, as Sierra pointed out already. I have already cleared up with Killer why the decision is wrong and he assured me it won't happen again in the future.

[Killerhurtz]

I'll only post here for visibility's sake: SierraKomodo and Tish's posts cover it all. At the time it seemed like a valid tactic, but a short talk later I saw that I was wrong, and I assume full responsibility for it.

[CampinKiller]

Right. Since he was talked to and knows that it's an issue now, then I'm fine with closing it.

[Skull132]

Complaint resolved, archiving.