Rookieblue

His steam ID is: STEAM_0:0:238179859 Ban Reason: RDM x2 / Player Dis While on the server I observed the above player acting extremely disrespectful to other players, calling them c*nts and b*tches multiple times, among other insults. I issued a warning to the player for their conduct. I continued to observe the player, and he continued to act extremely disrespectful to other players by swearing at them. I then observed the player RDM a D-Class in upper D-Block who was standing in line to be tested, yelling, "He stole my pizza bagel". He was killed by GENSEC and upon respawning immediately killed another D-Class in the spawn cells. Based on the players extremely disrespectful behavior and escalating behavior, I made the decision to issue a second warning as well as a 3 day ban. This was done to prevent further escalating behavior from the player, as well as to provide a cooling-off period.

Noted! We have reviewed this issue with our servers and we will be working hard to fix it ASAP! Please allow up to a week for any bug fixes to occur as we go on a first come first serve basis. Thank you!

You know what also shows that you're trapped in a cage and doesn't prevent people from seeing or being able to interact with you? The glass cage that exists in the cell. SCP 035's mask literally spawns there. The room is SCP 035's Containment Cell, which is where the character spawns. Your props prevent anyone from being able to interact with the cage, you, and SCP 035's mask had you not been playing that SCP at the time. Except you did, because literally no one could actually access you because you were completely walled off.

While on the server I noticed that you had been spawning numerous props as SCP 035. Upon investigation, I discovered that you had spawned in props that you used to fully encase SCP 035's case, which you were crouched inside. These props blocked anyone from being able to get to you inside the case and constitute prop blocking of a spawn area, which is prohibited. When I attempted to speak with you about this, you failed to respond and appeared to be AFK. I issued a warning for prop spawning as a SCP, prop blocking a spawn area, and issued a one day ban from the server, which is set to expire in approximately 2 hours from the time of this post. Regarding the warning and ban, formal warnings are required to document incidents that necessitate a ban, jail, job blacklist, or any other type of enforcement action. This allows staff to be able to track misconduct easily on the server. Please see the Gaminglight Staff Handbook, which requires to usage of a formal warning alongside other types of sanctions. To use your example, if you get a ticket IRL, it shows up on your record, which is the warning. The ban would be whatever the fine amount you have to pay is.

Accepted! The accidental ban was already removed from your account, our apologies there! But you've since received a ban stemming from misconduct that will remain in place.

Senior Researchers do good work, okay

Denied After checking the server logs myself it very clearly shows that you disconnected from the server, rather than you timing out or having internet issues. In general, an LTAP violation results in a 3-day ban + the regular punishment for whatever misconduct led to staff members making contact with you in the first place, so this is the smallest punishment you can already receive.

Partially Accepted After reviewing the evidence provided, as well as speaking with multiple parties involved in this incident, I will be rendering the following decision. Warn 1: E11 in D-Block - Appeal Denied While it is true being in D-Block as an E11 member is not allowed per the E11 SOP, and Skies was aware of this having to complete a test before joining E11, we also have to take into account the fact that the various MTF and CI branches have specific rules that aren't seen in the rest of the server. Skies was a new member to E11, and still inexperienced, but given the training focus that E11 places on not being allowed in D-Block, it is something that Skies should have been aware of. In addition, while in D-Block he fired on D-Class, adversely affecting their gameplay experience. Due to the impact of this, this warning will remain on your record. Warn 2: Staff Dis/Branch Dis - Appeal Denied After reviewing the specific comments made by Skies, I believe there is enough evidence to uphold this warning. Staff members are held to a higher standard when it comes to professionalism, and Skies displayed a disappointing lack of professionalism in his messages. This warning will remain on your record. Warn 3: Staff Dis - Appeal Accepted While the comments made in the staff chat were disrespectful, because they were made in the admin chat specifically, and not in public forums, I do not believe that a formal warning is the correct way to address this specific misconduct. It should be noted, however, that I have previously verbally warned Skies to avoid airing grievances against other staff members in a public setting, which he did in fact do here. Additional actions may be taken on an SMT level to address this misconduct at a later date. To have your warn removed, go to the "Bans" Section at the top of the forums, navigate to your profile, find the warning for this appeal, and for the reason on the appeal, link this post.

I don't even know what you're asking so I don't know how to help you.

Points of clarification I'd like to make prior to this appeal receiving further consideration: 1) The staff handbook prohibits issuing multiple warnings in instances of multiple types of misconduct being addressed at once. For example, SCP 912 enters the armory, buys a gun, and kills a GENSEC member. The situation being dealt with is FailRP / RDM. You would not separately warn the player twice for the FailRP and RDM, but rather combine them into a single warning. However, there are instances where additional misconduct occurs after the initial warning/punishment is doled out. Take the same example as before and a warning is issued. The player then makes racist comments. Staff members are absolutely entitled to address this new behavior despite a warning having already been issued for the RDM/FailRP. So there are instances where additional warnings may be warranted being issued shortly after another in certain circumstances. 2) Two warnings, those being the "Going into d block as E11" and "staff diss/branch diss" warnings, were issued by Jakub. The third, "Staff Diss", was issued by Inaccurate. In the future, I recommend making separate appeal posts for each warning to make it clear which staff member's warning is being appealed, and so you can state your case for that specific warning.

Oh, I remember reading that when you originally posted it. +/- Support on my end, you haven't caused any problems in recent history since this all happened, but at the same time you flagrantly violated a forum rule.

Player Never Banned in the First Place

Accepted To have your warn removed, go to the "Bans" Section at the top of the forums, navigate to your profile, find the warning for this appeal, and for the reason on the appeal, link this post. After reviewing what has been put forth, the D-Class in question was past the red KOS line. Whether the D-Class was able to walk back behind the KOS line or not is immaterial at that point, as GENSEC personnel are cleared to open fire on anyone past that line.

Moved to correct location

Moved to correct location

Accepted While 29 warnings in an of itself does not warrant a permanent ban, upon checking what the warnings were for, as well as seeking more information about this particular player's conduct, I believe that this player's continuous misconduct in the realm of racism, homophobia, ERP, and blatant disrespect to both players and staff members alike creates a toxic environment that has no place on this server. As such, I've decided to issue a permanent ban to this player.

Any further unnecessary comments and this thread will be locked. Enough

Erm, this will be fixed.

Please follow the suggestion format. Additionally, it would be helpful if you included more detail in your suggestion, such as what the position would be called, what donor level you would get access at, etc. Finally, requests like this would normally come from the branch in an update, but if this gets detailed out more we could discuss it.

Booo, no fun

Accepted To have your warn removed, go to the "Bans" Section at the top of the forums, navigate to your profile, find the warning for this appeal, and for the reason on the appeal, link this post.

Accepted To have your warn removed, go to the "Bans" Section at the top of the forums, navigate to your profile, find the warning for this appeal, and for the reason on the appeal, link this post.

I feel like that staff will be issuing a significantly higher amount of prop spam, prop blocking, and failrp warnings if this were to be allowed.

Says the guy with 315 posts.