Leaderboard

Bro not emmit! @Cammy Wasn't me i swear.

I'm just unable to find time to play. Thank you all for everything.

give him a chance its been a whole year!

+ Support Kids be saying dumb shit, it happens, and it's almost been an entire year. Though IP Threats are not to be tossed around lightly I believe in second chances.

Racism / IP Threats are a big nono. i mean, ur text seems kinda long and it seems like ur really sorry for what u said/did, kinda +support

@Jon Shoeshiner ??????

+ MASSIVE SUPPORT I dug, and I dug deep. Prepare for a long slideshow. First things first, establishing when the reporter arrived on the server. All times mentioned shown and discussed in this reply is in EST. Below establishes the profile picture tied with the reporter including the exact timestamp of when they finally connected to the server: 10:15:31 PM 18NOV22. Now, to establish the different RP names that they had during the time they were on. They logged on as ST PVT Mr Kuhn 1992 eventually changing to BIM Kuhn, MoH BIM Kuhn, and finally ST PVT GoofyLooneyTunesBugsBunny. From here forward I will be showing each and every Player Combat where the reporter was the Instigator in chronological order. Shortly after joining committed two counts of ARDM, but looked like they toed the line shortly thereafter as the next instance took place at least an hour later which is the next point below this one. One count of what would be an *RDM* IF it wasn't in the middle of a SIM as per the name at the time (BIM Kuhn). Continuing down the line are incidents taking place either involved at a PUBLIC EXECUTION (where friendly fire sometimes happens and he shoots one person accidentally) or when they were defending themselves or assisting in defending against a Bounty Hunter. The rest of the ARDMs that take place were accidental friendly fire during an event where people have already reported there was lag/connectivity issues. Also, as you can see in that last combat log where he was defending against a Bounty Hunter, he was pulled randomly, there were several Staff members in TeamSpeak that stated there was no ticket regarding the reporter as our Staff are like steroid-induced Cerberuses when it comes to taking tickets. There is no evidence pointing to any valid MRDM nor valid MARDM. Now, explicitly with just this information at hand along with the reporter's statement, there seems to be a confusing piece of information in that the warn for the ban-able offense took place at 9:40 PM 18NOV22 yet the ban took place FOUR hours later at 1:41 AM 19NOV22. Not to mention it is quite odd that an Admin would ban on behalf of a member of JMT when the reported individual is capable of banning by themselves. On top of this, the reporter was never pulled and told what they did wrong prior to receiving their punishment which is one of the absolute basics of being a Staff member, HOWEVER we have yet to hear @KLONDU's side. To both parties, if you have any clips in regards to the sit to provide more evidence that would be great. In light of all that I've seen from the evidence gathered thus far, I firmly believe there was an incredulous lack of due diligence in executing the duties of a Staff member in regards the the reported individual. EDIT: Utilizing Deep Storage and Advanced Search I was able to find evidence tied to the reporter's SteamID showing that it was NOT four hours apart between the warn and the ban it was within 60 seconds of each other. NOTE: When it comes to bans, they are logged as disconnections stating they the player is disconnecting due to being banned with the reasoning and length.

The admin who brought me the first time was @KLONDU around 20 minutes AFTER the supposed MRDM, then he asked why i was killing a bunch of people and i was very confused and told him it was probably crossfire from the event with shock, he said something along the lines of he would give me the benefit of the doubt and returned me. Then, around 10 or so minutes later, @KLONDU brought me and informed me he was banning me for 10 days for MRDM.

+1 I was with him during the event, some crossfire but no kills. Feel like the staff just had it out for him here and made up the whole MRDM thing, kinda overreacting.

Thank you for everything you've done emmit! You were truely what EMS needed for awhile for command wise. Thank you!

Your In-game: Lowerguy The admin's name in-game: Matilda The admin's steam name (If you know it): [GL] Matilda What warning did you receive: ARDM Evidence of the warn (REQUIRED): Why do you think this warn was false: because i thought someone disrespecting me and my family gives me the right to gun someone down because that reporter said "Imagine Being In SL" I took that seriously and i thought that gives me the right to gun him down. Any extra information:

To give more context another SL member said "imagine owning a fucking BMW" which the reporter answered with "imagine being in SL" and then drove away while Lowerguy started shooting the reporters car. Clip: https://medal.tv/games/garrys-mod/clips/J5Jh2PWqxL1bL/y1PLofbwk1OF?invite=cr-MSxxa0IsMTA1MDU1OTA5LA

Denied After review, the SCP-RP SMT team has decided not to accept your promotion application. This can be because of your application, experience, behavior, feedback, or other unstated reasons. You may re-apply in 1 week.

In fact like Klondu said, there was about 6 STs minging all last night and were just messing around. Now you (pretty sure it was you) decided AFTER the event to hop in the rotary ball of a LAAT and shoot into a crowd of people that were standing there in the middle of MHB. I then deleted the ship after multiple times telling everyone to get out and other people telling people to get out and stop shooting. You however didnt stop and kept shooting until I deleted the ship. I have also got proof of you saying the c slur multiple times after I said "lets not be saying that rn" which counteracts what you said about you trying to clean up your profile to join battalions. I gave you the benefit of the doubt but you ended up ruining that chance AFTER the mission.