Hex-G

If you look at the clip you can clearly see the immense amount of lag and rubber banding on the server. In the clip you can also count the seconds. I shoot my shotgun at around the 18 second mark. You can then see a major lag spike and during this spike I go to heal myself and during the time I input my heal while the server is lagging I heal (This is around the 26 second mark, well over 7 seconds). You can see in the clip that I heal at nearly the same time I get shot. I would also like to mention that "being shot at" does not constitute combat healing if you are not getting hit. As I am running you can see all the shots the D-Class are shooting at me hit the wall. I do not move from getting shot nor do I have a blood splatter until the single deagle shot during the lag spike. I also immediately put away my medkit after I get shot, because I know I am now in combat again. The fact that you went to sixx with the report and also the forums for something that is very clearly lag is confusing to me. I am pretty proud of the fact I have no warns on the server. I have followed the rules pretty diligently and know the motd quite well. Overall -Support. This is clearly lag on the server and an overreaction in general.

All I wanted to state in my post was that I have talked with Meeseeks almost every day since his blacklist and I know how he was when he got blacklisted and how he is today. It is a perspective I wanted to bring to the discussion. I have person bias but I gave my honest opinion.

I would like to give context. I have known Meeseeks longer than most people in security. We were LCMD together and got accepted to SCMD at the same time. We were MAJs together for 3 months. About a month later is when he got blacklisted from the security and later banned from the discord. No one knows Meeseeks better than I do. I have talked with him almost daily since his blacklist almost 3 months ago. I know that he has gone though some very difficult personal struggles that I can confidently say he is working on to better himself and those he cares about. If I didn't think he wanted to come back and show a better image I would not be writing this. I think that the reason for his blacklists were questionable and his discord ban was for something outside GL. I know that he feels remorse for the things he said and did. Please remember that this is not an unblacklist from every branch on the server but rather an unban on the discord. I very clearly have a bias as I have talked with Meeseeks frequently and know that he has been working on himself in his absence from the server. I think he should be allowed to come back.

It’s of no question wether rhynnos character is in question. He is an extremely active and dedicated member. It was a lapse is judgement and it auto banned him. I’m sure next time he will think twice. I like how Yato put it “gamer mistake”. + Support

FROM A SECURITY POINT OF VIEW this was handled correctly. When researches (including Bright + Maynard) take a D-Class without an escort, the D-Class becomes KOS. Even if the Security is refusing to escort for some reason they can still KOS a D-Class (If there are no riots and plenty of Security than they should not refuse to escort). From a staff point of view (which I have never been staff on this server but plenty others) I would understand why you would want someone from another branch to handle it. That much makes sense and I have no issue with. HOWEVER, I think that the sit was a case of being uneducated on how security operates and once the clip is seen there is not much else to do. The comment from the SM in the clip (when he says something like this guy will take a while to be explained too) is implying they have some cognitive issues. I think that would not exactly count as player diss since you can argue he didn't mean that but I digress. Overall, this sit was not the greatest but it was also not incorrect. I think tank COULD have given the sit to someone else of another branch, COULD have let the person who called the sit more time, or COULD have talked to the person who made the unneeded comment, but didn't have too. I would say that this sit was not in a state where you can say "Tank did this wrong" but also not in a state where "Tank did this good".

+Support Based Branch Update

This is actually a thing I think most SCPs should have. I mean, 106 is a joke. If you have a med kit you literally can not die to him. He needs a way to deal direct damage to players otherwise its just avoid him or escape when he catches you.

A very large and important incentive is the recommendation of an NCO or possible promotion. The ability to show the completion of a difficult task (capturing a D-Class rather than killing them) would merit praise. That, along with making it very clear that capturing is our preferred choice would be the incentives. As I said in my original post. This would also only be during low intensity site codes (blue and yellow). Prioritizing the return of D-Class during any hazardous situation is a clear bad choice. It would be far easier to implement the "all the time recommended" approach rather than "Mandatory during these codes" approach.

Its not complicated at all. Its one extra line while doing basic training. "If you see D-Class outside of D-Block you can either try and arrest them or KOS them if they run or have a weapon." If you wanted to make it hands up than D-Class could technically run with hands up and use that loophole. Its an easy fix just to shoot running D-Class but it needs to be written out properly if it would be something added to the SOP.

What bug is occurring? When someone who is under level 40 tries to join the "Juggernaut Brute (level 35)" job they will get a message saying they are too low level. Is it tied to a specific job, swep, player model, etc? Yes, the "Juggernaut Brute (Level 35)" job. Has it only occurred once, or is it continuous? Only once due to most people who join Juggernaut being above level 40. Please provide screenshots or a short video of the bug in action: Image is low res, blame steam's screenshot system.

The hope is that we would encourage security to do so unless it is absolutely necessary to kill them. We train security for encouraged rules very frequently. Many Enlisted believe crossing the red line to be against the rules when in reality it is only encouraged. This affect would be easy to replicate and anyone in security would have many reasons to KOS a D-Class and would receive praise for bringing one back alive. Making this act commendable through NCO encouragement and possibly showing a level of skill would help in the long term.

Enjoy your vacation, we will await your return o7

Kovic, you've been in SCMD for such a long time. You have done an awesome job in Wardens and been a great mentor to so many Command. Enjoy your retirement, and let us know if you ever want to come back o7.

+/- Support Mostly leaning towards -support only because it seems unnecessary. Most branches have a very high rank limit you can hit before it counts as a life. Security: LCPL | Research: Researcher | Maintenance: Command | Medical: Command | Nu-7: NCO | E-11: NCO | D5: NCO | CI (both): RCT This mostly applies to being in command in more than 2 branches. One person could be | Security PVT, Associate Researcher, Maintenance Expert, Elite Medic, Nu-7 (LIFE 1), E-11 CPL, *no D5*, CI (LIFE 2) In this example, this person can be in every branch except 1 combative branch, and 1 of the two CI. This may not even be correct and they may have even more options. It sounds a bit scummy but I would be ok if it was some form of premium to have more than 2 lives. If you had to buy some $10-$15 package that granted you a third life it would show the command that you are dedicated to the server and willing to dedicate time to be these high ranks in these different branches.

Big +Support I think a map update and a few small content update could provide A HUGE amount of rp possibilities for D-Block. 1. Updating the map to have upper D-Block make sense: Having the checkpoint doors that can seal off D-Class and Security makes perfect sense. They are prisoners and allowing them to have an open space with the threat of a red line between them and possible freedom makes 0 sense. Creating a D-Block where they would need to work together to climb up to a ledge, keycrack open a door, or take advantage of a Security member and sneaking through should be their ways of escape, not jump and crouch spamming on a CC and killing all 4 enlisted holding d-block with nothing but a knife. 2. Give D-Class and Security more to do. Right now the only things D-Class can do is mine and riot. Having some games (chess tables, gambling machines, perma-propped basketball court) would give them entertaining and enriching options. Security could also do contra ban inspections in Lower D-Block and introduce some new protocols that would require D-Class to line up to gather them for testing/SCPs (testing could add a lot to the D-Class experience and I hope Research HCMD take that into consideration). D-Class should ideally not be able to escape/overpower Security on their own. Having easy ways of escape That Require D-Class to work together is imo the only real way it should be done.

Having a new D-Block would be ideal for a multitude of reasons. I think these are some cool idea's for Security to be able to interact with D-Class. I also really like the researcher one where they are looking for a D-Class. I think having a server where D-Class have activities to do and to entertain themselves/interact with Security in other ways besides rioting would add a new, enjoyable, and healthy level of rp to the server.

Not going to give a + or - support. All I will say is that after spending months in D-block with D-Class, I can say that there are 2 brands of mic-spammers. Both are incredibly annoying. A: D-Class/Security (can be any rank from OFC->CPT) who play music when there is low activity or energy in D-Block. This is mostly alright as it does not affect rp and people will usually stop if you ask them too. B: This one is like 90% D-Class: Playing repetitive annoying sounds through their soundboard. Its funny the first time you see a D-Class spam youtube poops in vc but after that first time it just makes you want to leave D-Block. I think that ANY micspam is bad and I am personally not a fan of constant audio stimuli. I also think that allowing "people to play a song that includes the N-word" will allow all the brainlets to add a "N-word" button to their soundboard and its a technical loophole for the staff. For those reasons I am not a fan.

+ Support I think this is a good idea WITH some restrictions. I think that if it was only on blue and yellow, not having a weapon out, and not resisting are good restrictions. I would also just add that if they are able to escape the encounter they are still KOS. By this I mean that if they would be too far away to fear rp them. Example: You are running from interrogation to Research bunks and see a D-Class down the hallway at the greenhouse checkpoint. In this scenario they would still be KOS because they are too far away to fear rp. Also, like Ein said, this would need to be an encouraged and not required addition.

+Support @Tomato Thank you for saying all the things I wish I could say as a Security member. It has been an upward fight to be in this branch. Don't get me wrong, I absolutely love it here and know everyone by name. I think that it gets progressively more difficult as time goes on. Security is in a state where we need to have number advantages against D-Class. None of the main jobs are a threat, only the CCs (and mobsters can be dangerous too). We recently made a Sub-Branch called Juggernauts in an attempt to promote more activity as well as have some stronger jobs to deal with the constant "sandwich battle" between D-Class and CI. Even then, getting any buff for Security was a massive battle with the higher ups and is still a struggle to get what we were told we could have. I miss escorting researchers with genuinely interested D-Class to an SCP to see what it does. Now, D-Class get even more chaotic with no researchers and when there are researchers the D-Class target them and kill them almost instantly. The only way to fix the downward spiral is to do some form of overhaul. This is become a server that is not "SCP-RP", its "SCP-Deathmatch". Pick a side and shoot all the other people. And if you wanted to play: Medical, Maintenance, Research, or RnD, good luck. I mostly feel bad for new players. They will join the server and see a warzone and most people will play for a while and never come back. The ones that stay will likely buy a CC and get banned a while later for toxicity of some kind, that's just the player base this game mode attracts.

Even though our interactions where sparse, you have always shown yourself to be committed and worked hard with our DHFTOs to make the FTO program as good as you could. Thanks for all your hard work Akrew, well see you again soon o7.

ACCEPTED Your application to Initiate Juggernaut has been Accepted! Please see any JGE+ for training. Welcome to Juggernaut o7

ACCEPTED Your application to Initiate Juggernaut has been Accepted! Please see any JGE+ for training. Welcome to Juggernaut o7

ACCEPTED Your application to Initiate Juggernaut has been Accepted! Please see any JGE+ for training. Welcome to Juggernaut o7

DENIED Unfortunately your resignation letter has been denied. You may try again never. All Jokes aside, thank you for being such a dedicated HCMD member for so long. You have given your all since day 1 and I speak for everyone in command when we say you have helped in so many ways. Remember to stop by every once in a while man, o7.

PENDING Your application to Juggernaut Initiate is currently being decided upon by Jugg Command please wait 24 hours while we review your form some more.