Veesus

+/- support No idea how this would even be implemented. Players are hardcoded to be knocked back based on how much damage they take. To nerf the knockback you'd need to nerf the damage per bullet, or add EFL_NO_DAMAGE_FORCES to all players, and then manually apply knockback in a PostEntityTakeDamage hook. Ultimately, I don't even know if it's worth the development effort, but I can not deny that it would definitely make combat a lot more satisfying if you weren't knocked around as much, especially for SCP's.

+Support Its part of a donator pack it should have something special to it

+SUPPORT PLEASE

+SUPPORT As long as they are updating the map they might as well remove mapping oversights like this.

This is actually very easy to implement. You can even remove the effect for on duty staff so they won't have any trouble dealing with a 8286 who is lying about having a valid ID. And an actual rudimentary ID system would not be hard to implement either. Overall, all the problems that would arise from implementing this can be easily solved, and the only tangible downside is that you might have to take more than 3 seconds of looking at the tab menu when finding out who the 8286 is disguised as. +SUPPORT

It would be a 45 minute project to make a version of the voice amplifier swep that only works on the foundation site and let 079 spawn with it so +support

Staff response speed is at an all time low so I have to give this a heavy +SUPPORT At least for maintenance As for SCPs I have to agree with this:

+SUPPORT

Messing with limb damage might help the match up a bit but I think there are some glaring issues with hitboxes in general that need to be addressed first: Some models don't have their hitboxes classified correctly. They are all specified as "generic" which means they do one to one damage. This means they don't get any damage multipliers from headshots, or any damage nullifiers on limbs. A lot of issues with low damage even after pumping an entire mag into a D-Class are frankly just down to hitreg. So +/- NEUTRAL I think rebalancing hitbox damage should definitely be addressed in some manner, but a lot of other things need to be addressed along side it.

You could very easily repurpose 079's teleport menu and make it openable and useable by staff members, so they can use it to get around the map much easier. +SUPPORT

It is possible to do non laggy sightline checking on serverside using various optimizations such as only ticking on players in the same pvs or within a certain radius, only checking a percentage of the server pop per tick or even checking like once every 10 ticks or something and also general optimizations such as extensive variable localization and proper management of the player table in a way that doesn't create much garbage collection. In fact, I made a library a couple months ago just for performant serverside sightline checking that uses FOV and client aspect ratio for super accurate view checking which can be found here https://github.com/veesusmikelheir/gmod-sightlines/tree/master/lua The swep would probably have to be custom made for the server with performance considerations as the top priority, as well as taking into account things like gaminglights low tickrate. So it certainly is possible to implement this in a performant way. Which is why I'm going to: +SUPPORT

Any cloaking class (mostly MTF) since they removed levels over peoples heads. It's actually possible to completely surprise people now without them metagaming. Makes for some really fun moments where I can just completely destroy d-class with a knife when they don't know I'm there or flank CI when they raid.

ok buts its a freakin sweet progress bar its green and everything

+SUPPORT IVE LOST SO MANY FIGHTS FROM ACCIDENTALLY SWITCHING TO A CIGAR INSTEAD OF MY SECONDARY

Gmod and source engine games in general have a system in place called lag compensation in which the server keeps a history of player positions so it can estimate where a player was on a given clients screen using their ping and interp settings. Lag comp is automatically enabled when using the default gmod swep shoot function but it's incredibly easy to overlook on sweps that use custom attack logic like the scp sweps, which is what happened.

What is your in-game name?: Veesus What is your steam name?: Veesus What is your steam ID?: STEAM_0:0:43277070 What is your discord username (Ex: Rookieblue#2667): DanieI#9746 Do you have any other experience with staffing?: (If yes, explain) Yes, I was a staff member on SCP RP for ~3 months as a senior mod What date did you start playing on the community? (roughly) September 2020 What date did you make your forums account? September 18th 2020 How many warnings do you have on all GL servers? 2 warns, one for NLR and one for having a negev as 343 What is your donor rank? (User, Silver, Gold, etc) Platinum Are you a staff member in another community? No Have you read the staff handbook? Yes Timezone: EST Why do you believe that you deserve the rank? (150 Word Minimum) I used to be a member of the staff team, but I was removed due to inactivity. I was inactive due to a combination of a lack of freetime in my life and frankly just losing interest. But now due to recent circumstances my interest in the server is at an all time high, and I have more freetime since I don't have to work a full time job like I did in the summer. Ever since I first joined gaminglight SCP RP I've been extremely passionate about the server and its community, and I would be honored to volunteer my time to making the server a better place. I think I would be a perfect fit for staff due to my past experience with staffing and even more experience with the community itself. I also have a lot of experience with customer service in general, due to my day job, and I believe staffing is primarily a customer service job, as your priority is to ensure that all players are having the best experience possible. I believe I have the makings of a good staff member since I am generally extremely patient, and diplomatic in all of my user interactions. Scenario questions: Select any two of the following four questions to answer for this section. Please note, in the scenario questions we are not expecting perfect answers. We are accessing your critical thinking skills, your ability to use the staff handbook, and come to reasonable conclusions. Q1: How would you handle someone that is Mass RDMing and when you bring him/her to an admin sit all they do is curse at you? First I would jail them in one of the staff rooms, away from other players to give them time to cooldown a bit. Then I would gather evidence in the combat logs and gather player testimony, and other evidence if necessary. Then I would return to the perpetrator and unjail them, and see if they were willing to cooperate. If they are I'd explain to them their punishment. If not then I'd just go ahead and issue the punishment. Regardless of how they act after being jailed I'd still issue a formal warning, and refer them to a higher level staff for a 5 day ban, whom I'd give the evidence I gathered to. Q4: There is a player abusing a known bug, and he has been reported to staff. He swears he followed the server rules when you talk with him. What's the best way to handle this? First I'd explain to them exactly what they did wrong and why it was against the rules. If they try to claim that that specific bug isn't in the MOTD so it can't be against the rules I'd explain how they were abusing a glitch and how it falls under Rule 3. From then on tt depends if they were abusing it knowingly. It's possible to accidentally abuse a bug without knowing it was a bug. If they were not abusing it knowingly and it isn't a major bug I'd explain to them how to avoid the bug in the future and let them off with a warning, and then spectate them to make sure they don't do it again. If it can be determined they were intentionally abusing it (ie alt e abusing, which you cant accidentally do) or if their abuse of it affected other players experiences I'd warn them, and have a ban issued for server exploiting.

Name: Veesus Rank: Trainee Time of LOA(MM/DD/YYYY): 05/19/21 - 5/22/21 Reason(Put Private if you do not wish to say): Private

When buying frags or smoke grenades from the armory, it is unable to process buying multiple grenades. It simply takes your money and does nothing, instead of say, giving you more grenade ammo. I understand the potential consequences of having too many grenades, but could it be made so that instead of eating your money it simply tells you can't buy it again?

SCP-682's SWEP has an issue where you go slower after your burst fire has ended. Before using your burst speed once you have a sprint speed of 240. After you use your burst ability and it ends, your sprint speed is reduced to 180. This is actually slower than your walking speed, which is 185. So basically this means that if you use your burst ability you get a -60 slower speed after its over, indefinitely. Another bug with the burst ability is that if you flag onto another job while in your burst ability mode, you'll end up with these bugged speed stats on that job, no matter the job.

It's based off the Keep Upright tool in gmod that we were able to use on the server before the context menu was disabled. People really enjoyed knocking over chairs so I made a chair that couldn't be knocked over and wrote this document about it for some free RP

Name: Lipo Rank: LCPL SteamID(Ex: STEAM_0:1:174348602): STEAM_0:0:43277070 Current Sub-Branches your in: Why should you retain your rank (Command ONLY | 150+ words): AMONG US Any Notes, Questions, or Concerns?: Riding crop for command to keep their enlisted in check??

Item #: SCP-7887 Object Class: Safe Description: SCP-7887 is a standard issue foundation desk chair. SCP-7887 has proven to be impervious to all types of physical damage, including but not limited to bullet fire, blunt force damage, and damage that would be sustained due to its primary effect. SCP-7887's primary anomaly manifests when it is offset from a completely upright orientation. The object is capable of applying a self-righting force proportional to the angular deviation from upright. As a result, SCP-7887 is capable of resisting all attempts to tip it off axis, and no tested method has succeeded in offsetting the object more than 5 degrees. The method with which it applies this force is still under investigation. When SCP-7887 encounters a physical obstruction preventing it from righting itself, it will increase the righting force exponentially, measured to reach an excess of ███████ newtons per square inch. This invariably results in either the obstruction being dislodged, or extreme amounts of damage to the obstruction, due to the massive force involved. Testing involving attempting to obstruct the object over is restricted to level 3+ due to this property, as it may lead to extreme damage to foundation assets. Addendum A - Discovery: SCP-7887 was discovered on October 2nd outside of Research Bunks in Site 10. The origin of the object is unknown due to LCZ surveillance malfunctioning on that day, and no on-site personnel being able to corroborate the object’s origin. Attached to the object was a note, reading: “For the guy who keeps tipping my chairs over: [EXPLETIVE REDACTED] you.” Special Containment Procedures: SCP-7887 is to be kept in low security anomalous item storage in Site-50 light containment zone. SCP-7887 is not to be tilted more than 3 degrees off of its upright orientation outside of testing, at risk of damage to foundation assets and personnel. Recontainment Procedures: Upon recovery, SCP-7887 is to be brought back to containment using custom built gyroscopically stabilized dolly cart. SCP-7887 is to be surrounded by 3 inch bullet proof glass at all times during transport, in the event of a tilting incident.

Test Log Lore Name: Schittlips Rank: Lead Researcher SCP: SCP-087 Background Research: Slinky's are a classic children's toy constructed out of a spiral of metal ribbon. The toys act somewhat like a spring, "slinking" back to a rest position when extended. A common activity carried out with these toys is to send them down a flight of stairs. If done properly, the toy will descend the flight of stairs in a periodic fashion, repeatedly slinking and unslinking, until it reaches the bottom of the flight stairs. Question / Idea: What would happen if you sent a slinky down the staircase of SCP-087? Procedure: A generic brand titanium slinky measured 3.5 x 3.5 x 3 inches was procured from foundation aligned toy store. The slinky was then placed at the top of SCP-087. After multiple attempts, the slinky was successfully slinking down the staircase. The slinky was then remotely observed for 1 hour. During this hour, it was observed to slink successfully down the stairs, without any impediments. Slinky proceeded outside of visual contact range at T+1.11 hours. A D-Class personnel was then deployed into SCP-087 to observe the Slinky's progress. D-Class followed slinky for another 14 flights before testing was suspended at T+6:00 hours into the test Testing was then fully suspended for a period of 3 days. Another D-Class was sent into SCP-087 to ascertain the progress of the Slinky. Item was located 124 flights down in SCP-087. Item was reported to appear extremely rusted, and made an audible creaking sound while moving. The slinky was still advancing at a steady rate. D-Class was unable to be retrieved from SCP-087. Further expeditions into SCP-087 have been unable to locate the Slinky. Test suspended indefinitely. Addendum 1 - [T+3 months after initial test]: During an unrelated expedition, D-class reported hearing a period metallic creaking, the source of which they were unable to ascertain. Later the sound was confirmed to be consistent with the sound of a highly rusted slinky. Further investigation pending.