RukoFamicon Admin Report (from CGI_ Gaychild)

[CGI_Gaychild]

In-game misconduct:

CKEY: CGI_Gaychild

Offender’s CKEY: RukoFamicon

Date: 2025-05-14

Round Number: 52570

Rules Broken (if relevant):
“Rolling for antags + extremely poor antagonist contact. you are clearly not a good fit for this server.”
I did not break any server rules. I had rules invalidly and mistakenly applied to me, and I had nonexistent “rules” applied to me as part of the ban justification. Original appeal here: CGI_Gaychild banned by RukoFamicon

Part of Admin/Mentor Conduct Broken (if relevant):
The admin banned me even though I did not break server rules, as I will explain. The given rules are either:

1. Real rules that do not apply to me at all, as shown in the exact video (that I made it impossible to revive a sec officer I eliminated. That is an invalid application of the rule, as I simply took his body out of the halls and store it in a locker)
2. Stated rules that do not exist (RukoFamicon said that it’s illegal to eliminate a security officer “too quickly” after they join the round. There is no such server rule and there has never even been attempt to pretend that there is. I eliminated the sec officer in the middle of the station when I happened to cross him)

Incident Description:

My last last appeal thread was immediately locked without permitting a discussion or even making valid points at all.

First of all, I did not antag roll. I’ve been rolling antag often though, and I’ve had spurts of disconnection/AFK during both antag rounds and non-antag rounds, as I play during work hours sometimes. Proof of my lack of antag rolling is that I’ve never even been warned for such alleged behavior.

Moving on… The banning admin hurriedly locked the thread after giving the following non-argument:

@Ruko

You approached, shot on sight without a word, disabled his sensors and shoved him into a locker which you then hid in maints more or less as soon as they joined the round. They hadn’t even made it past the arrival hallway yet - this is shown via a video.

This kind of antagonist behavior of preemptively eliminating security without prior escalation is explicitly allowed in the official Beestation Rules under Antagonist conduct (Rules#13_Antagonist_Conduct on the wiki), Rule 13-3.1. The verbatim text:

• You may pre-emptively eliminate official, and acting, members of security.

This was done throw a low-impact method: shooting him and him alone, and then hiding his body. Recovery of the body was not made impossible, I simply took him the corpse away from the hallways, and in fact left a trail of blood to it. This video, that was used in the bizarre and summary denial of my appeal, actually proves that I merely stored the body in a locker.

I also didn’t know this player joined the round recently – we weren’t near arrivals, and I happened upon security in the main hallway and did some quick acting to get rid of him as a threat. And it doesn’t matter, as antagonist are also no rules against eliminating people who recently joined the round.

@Ruko

Going out of your way to prevent revival is against antagonist conduct in most cases, and even in cases where it isn’t it should only be done when necessary. You should read the rules of the server before insisting you did nothing wrong.

Hiding a corpse in a locker (which I did – with a trail of blood leading to it, as show in the video) simply isn’t a violation of any rule found anywhere in the Beestation wiki. You just made that up. I actually read the rules thoroughly before this round – the only rule is against making revival impossible, which would mean doing things such as

1. Cremating a body
2. gibbing a body in the kitchen
3. spacing a body

and I did none of these. I put his corpse in a locker in maint and left a trail of blood to it. I basically stopped short of personally delivering the body of an enemy sec officer to medical.

Hiding a body as an antagonist is very normal behavior. I eliminated a security officer, and this is explicitly permitted in rule Rule 13-3.1 of the server. There’s nothing about antags being compelled to leave corpses of eliminated security officers out on the open or fully tracked. The only rule is against making it impossible (rule 13-3.5)

@Ruko

Even outside of rules, if you can’t see issue in immediately jumping to permanently remove someone who just joined I stand by my statement that you are not a good fit for the server.

Again, I didn’t know he just joined, I ran into him in a normal main thoroughfare of the station — actually the (I think) center intersection of the main halls where “Cardinalstation” is printed on the floor. This is show on the video that the banning admin posted in the original thread. I repeat: I *did not kill anyone off spawn. We crossed paths over the central part of the station’s hallways, where the very name of the station is written. I believe this was when I was returning from R&D after performing my objectives there.

And I also didn’t empty the server – that’s outright false and in fact impossible, because I was robusted in medbay and promptly killed by several crew members who were alive and well after my death.

Because the conversation was shut down by the banning admit before I or anyone had a chance to respond, I am making this admin report. Please treat it as a higher ban appeal.

I invite others on the admin team to address my concerns, particularly higher admins. The most charitable interpretation this kneejerk ban was that its very flimsy with dubious reasoning, and a typical interpretation of it would be flat out admin misconduct, especially considering the closing of the the original thread without allowing a reply.

[RKz]

@CGI_Gaychild

Part of Admin/Mentor Conduct Broken (if relevant):
The admin banned me even though I did not break server rules, as I will explain. The given rules are either:

1. Real rules that do not apply to me at all, as shown in the exact video (that I made it impossible to revive a sec officer I eliminated. That is an invalid application of the rule, as I simply took his body out of the halls and store it in a locker)
2. Stated rules that do not exist (RukoFamicon said that it’s illegal to eliminate a security officer “too quickly” after they join the round. There is no such server rule and there has never even been attempt to pretend that there is. I eliminated the sec officer in the middle of the station when I happened to cross him)

This part of the form is for citing the parts of the conduct that were broken by the admin in particular. This is just restating the alleged rulebreak from the player report.

[Ruko]

First and foremost I’m going to say this:

---

@CGI_Gaychild

impossible to revive

You did not make the officer technically impossible to recover, but you made them practically impossible to recover. You made the body untraceable and hide it in a secluded location making the odds of being found near zero. You also claim to have sabotaged medical with the direct intent claimed to be making revivals harder. That makes this high impact action twice over:

---

@CGI_Gaychild

Stated rules that do not exist (RukoFamicon said that it’s illegal to eliminate a security officer “too quickly” after they join the round.

Attacking someone as soon as they leave the shuttle is pretty much the same thing in intent.

---

@CGI_Gaychild

First of all, I did not antag roll.

You have a long and proven history of this, and the round immediately prior to this you joined and left immediately after not getting antag. That is antag rolling.

---

@CGI_Gaychild

Again, I didn’t know he just joined

@CGI_Gaychild

Another security officer joins the server. I fear for my ability to leave the station alive

You literally tried to justify your actions because you had just noticed him joining.

---

@CGI_Gaychild

we weren’t near arrivals

Blurry image because low quality video, but yes you were:

That said, the player did state they hadn’t just joined to me as I was writing this post up. It was just a coincidence of locations.

---

Above all of these, the biggest violation is this:

This is the core for which all other antagonist rules are made. Can you tell me you were trying to make the round more enjoyable and engaging for others?

---

Ground I’ll leave:

This was originally going to be just a permanent antagonist ban upon discovery of the additional antagonist rolling, given you’ve already reached that point in escalation of your antagonist bans, but when seeing the video and your troubled history on other servers I decided you were probably not someone we wanted to keep giving more chances to given how little time you’ve spent here despite the history you already have.

Continuing to give you additional chances to break other rules would only degrade the quality of the server further, and if you decided to leave on your own, probably just serve to give you a chance to spout something transphobic or similar again as you’ve already proven to do elsewhere.

[ro5490]

Please correctly fill out the Staff Report format.

Rules Broken refers to which of our main rules the admin in question has broken, not what you’re appealing.

Admin/Mentor Conduct Broken refers to specifically any of our Admin Policy and Conduct that the admin in question may have violated, as RKz stated earlier.

You may link to your previous ban appeals in either the Incident Description or Additional Information sections.

–

Also, for reference, we have RAW(Rules as Written) and RAI(Rules as Intended), both are explained under Rule 0 - Admin Discretion.

Text from R.0 Relating to RAW/RAI

Just because you bend the wording of a rule into a pretzel and don’t break the specific RAW (Rule As Written) does not mean you didn’t break the RAI (Rule As Intended). Rules are subject to interpretation and if an admin believes you broke a rule as it is intended to function, you can expect the same consequences. Rules as intended always trump the rules as written, and “Toeing the line” is not permitted.

The Head Admin team will process this report when they have time. For now I suggest you go over your admin remarks and your bans, as you do have a history of similar and repeated behavior.

[CGI_Gaychild]

You did not make the officer technically impossible to recover, but you made them practically impossible to recover. You made the body untraceable and hide it in a secluded location making the odds of being found near zero. You also claim to have sabotaged medical with the direct intent claimed to be making revivals harder. That makes this high impact action twice over:

So I made it of difficult to revive the player I am explicitly allowed to eliminate? Which is “sorta kind of impossible?” if we twist words and meanings into a pretzel? Ok, I guess. What I did was fairly standard antag gameplay in the very mainstream tradition of SS13 play. I am not a giga-expert in the unwritten connotations of Beestation procedure – I will concede that. I made a minor procedural error by being slightly too cavalier in antag gameplay by hiding a body and then causing a bit too much incovenience that didn’t even amount to a hull breach with a welder bomb. If you think making a minor procedural error warrants a first-time permaban, that’s insane. That’s what’s at issue with this report.

Attacking someone as soon as they leave the shuttle is pretty much the same thing in intent.

You literally tried to justify your actions because you had just noticed him joining.

I didn’t know when this person left the shuttle. I was leaving sec and moving through the halls normally and I had to make a quick decision when I looked suspicious as fuck and saw a sec officer. This is maybe the second time I’ve played Cardstation, a gigantic, labyrinthine map that’s peculiar to BeeStation. I don’t have encyclopedic knowledge of the map layout, and in fact I am completely unfamiliar with it. I didn’t know where the sec officer was coming from and I had to think fast. If you’re trying to come after me for happening to have been near arrivals without knowing it and not having encyclopedic knowledge of the layout of an obscure map, this outright proves that you’re rules lawyering and that you don’t have leg to stand on. That’s simply ludicrous reasoning for a permaban.

You literally tried to justify your actions because you had just noticed him joining.

I was talking about a different security officer who joined after I killed the first officer (Odako). I never interacted with the second officer who I noticed joining. I never even saw him. Check your timeline.

You have a long and proven history of this, and the round immediately prior to this you joined and left immediately after not getting antag. That is antag rolling.

You’re using evidence from last year to ban me? I disconnect sometimes because I play during the workday. I am more likely to do this in low-stakes situations such as not being antag, but I don’t disconnect because I didn’t roll antag. Using 2024 evidence for a mid-2025 ban means this is not solid reasoning.

Above all of these, the biggest violation is this: https://forums.beestation13.com/uploads/default/original/3X/6/e/6e2142f3efd5455dbeeb5a40afbc71205c7ec27a.png

This is the core for which all other antagonist rules are made. Can you tell me you were trying to make the round more enjoyable and engaging for others?

I actually intentionally tried to make the round interesting for other players.

I made an effort to scout around, talk to players, and gather intel on what they were doing to see if there was anything interesting I could add to it, and to see if there were interesting projects or narratives I could avoid fucking up or at least work within. I stopped by the library, chatted up two players to see what they were doing, and tried (badly?) to make a creepy mystique for myself by asking one of them to find me the creepiest most mysterious book they could find from the library computer, and I made conversation in that regard.

Half the reason I set off tiny bombs (welderbombs, no hull breaches) was to make some excitement for players who seemed bored, who were just sitting in the library on the couch together, who seemed excited to help me when I asked for something as small as a book. At least one of them was medical staff, which made that a more exciting target for some low-level SS13 mayhem.

To this end of creating a creepy mythology for myself, I’d often go up to players with a mask on and no ID, stand there still and look at them wordlessly to create a creepy vibe. My character was a self-mythologizing sadist who wanted to create a mystique for himself through RP interactions like that.

When I was pursued by validhunters, I only fired my weapon to slow them down and defend me when I could have easily taken them out of the round - this happened multiple times, please check the logs. I restrained myself every time, and you argument against me vanished when you actually look at those real facts of the situation.

You attempted to make the case against me as a mindless murderboner who caused as much chaos as possible, but it’s a matter of public record that something very different happened. My actions were measured and restrained within the spirit of the BeeStation rules. I let people live when i could have killed, I was sensitive to the population of the server, and I tried to add some SS13 antag fun to a low-energy round without griefing.

At the end of the day, I played a pretty middle-of-the-road antag, which makes this ban against me pretty bizarre. Someone complained because they were upset they died to an antag. That’s not the end of the world in the game of Space Station 13, man. Headmins, this is an open and shut acquittal, there’s just nothing here and it’s slightly embarrassing for the server that this ever made it to a permaban in the first place.

[Ruko]

I’ll leave it for headmins to review. I’ve made my points and admitted the mistake that did contribute to the ban in good faith, but stand by the ruling that you aren’t fit to play here. Some part of me wants to post all 39 of your say logs in this round or press you for more explanation about your interactions with others, but I know it isn’t going to go anywhere with you at this point.

I hope you can eventually reflect on the fact that perhaps the problem is you and your behavior as the list of servers you are permanently banned from continues to grow.

[CGI_Gaychild]

So what’s the status of this

[Ruko]

Admin reports require all heads to be available at the same time, it’ll be handled eventually

[h42]

Hey there, thanks for reporting this!

First of all, I would like to apologize for the wait on this. There were a few things that needed to be checked on and it took quite a long time to process and confirm.

That being said, I can’t find anything wrong with the action taken here. This was not a ban for shooting a security officer and stuffing their body into a locker. This was a ban because the admin in question felt it necessary to do so since you were doing such a poor job of driving the round per our Admin Discretion rule. To put it into perspective, your actions caused ~70% of the server’s players to close the game.

Typically this would be fine, learning how to play the game takes time, and there’s bound to be struggle before a player gets a good feel on how to keep things engaging as an antag. However, we’ve had to talk to about this several times throughout your playtime here, to the point where in your 120 hour playtime, we have had to to sit down and talk with you every 7 hours.

No action will be taken. You are welcome to rejoin the server in a year from the ban date, provided another reputable server is willing to vouch for your actions.