Catalyst

ROA or LOA: LOA Name: Catalyst Rank: SET Start Date: 12/12/23 End Date: 12/26/23 Reason: Private

ROA or LOA: LOA Name: Catalyst Rank: ETM Start Date: 9/5/22 End Date: 9/15/22 Reason: pc dead need a new motherboard

HOW? HOW COULD YOU DIE LIKE THAT? HOW DAGGER? Imma be real ender, you were one of the few people on this server that had that fire that I admired. You always would fight for change and you never backed down from a challenge. You continued to do your best even after others tried to bring you down, coming back to the server after so many resignations and you still went as hard as you could. You never took anything at face value, never was a yes man, was always willing to challenge a statement, something we needed now more than ever. I will always respect how you were always relatable and down to earth in many matters. You led EOI and many others to glory, and I’m glad I got to see some of that good old insurgency spark before you left. it’s truly sad to see another piece of the insurgency old blood go down. Hang in there ender, you are number one. o7

Name: Catalyst Steam ID: STEAM_0:0:184128807 Rank in Event Team: ETM Date of Joining Event Team: 06/12/2023 Date since last promotion: 06/12/2023 Why should you be remaining as an Event Team Member? (ALL ET RANK | 100+ words)? I joined ET because I saw gaminglight in a state where more detail oriented RP was needed, and joining ET has been able to give me the ability to do so. I've been able to take situations in a different light, creating new RP scenarios while helping branches develop their own identity. Event Team is one of the few things on gaminglight I plan on continuing with, to create and develop my skills, and I hope I am able to stay in the team to continue progressing, and bring more of my idea's to the server, such as the expedition events I've been hosting. Any Notes, Questions, or Concerns?: N/A

What are you suggesting? - Remove the restriction that command of rp branches can only transfer to other rp branches, and likewise for combat branches How would this change better the server? - Right now there are 3 RP branches and 6 combat branches. People from RP branches are at a complete disadvantage, only being able to request a transfer to 2 other branches, compared to combat command, which can transfer to 5. The qualifications to be command between an rp focused branch and a combat focused branch are nearly identical. It makes no sense to have this restriction anymore. Are there any disadvantages of making this change to the server? If so, explain. - No Who would this change mostly benefit? - Command Please link any workshop content, screenshots, or anything that you think may be helpful to those who view this suggestion - N/A

-support The idea behind having capture points in the first place is to give both E11 and CI a reason to use surface for their own gain. Capture points= more need for active E11 and Ci which = more activity Both E11 and CI both need a decent amount of power and making it something people actually fight over (creating an actual need for active CI and E11 outside of raids) is better than straight up buffing those branches

Steam Name: Catalyst Ingame Name: Catalyst SteamID: STEAM_0:0:184128807 Job Blacklisted From: CI Reason for the Job Blacklist: Leaving and rejoin over five times, got banned for NITRP and LTAP for 2 weeks, other behaviors that are unwanted in CI Dispute: Leading up to the blacklist, I had been upset with the state of the server, and had done a bunch of things that I regret in hindsight. I had rejoined GL knowing the blacklist was in place, hoping to earn my reputation back across the server, as well as CI. Hopefully through what I've done in the past few months I've shown my motives have changed, and I'm willing to take accountability for the mistakes I've made, as well as showing a change in maturity.

ROA or LOA: LOA Name: Catalyst Rank: ETT Start Date: 6/26/23 End Date: 7/3/23 Reason: Busy

https://docs.google.com/document/d/1S4YkMxihBDSgTmbhEsmjf0xgSzdGk3wbz1oi_3i36_o/edit?usp=sharing

A lot of people come to the server to roleplay and get material for writing, and given how unique the lore can be for the server in specific, it would be nice to have a specific section on the forums for writing GL specific SCP tales, since they are a key part of the original SCP wikidot. I'm mainly making this suggestion cause I personally have wanted a better place to write and share GL specific tales, but perhaps adding this to the SCPRP section will allow others to do the same, since the only other forms of heavy writing are within research and utility, which often aren't very good ground to make tales on.

https://docs.google.com/document/d/12a9Hj2PcmA-q2Gmc7VyfKrv91PPVHti19HOzDBAb1vw/edit?usp=sharing

Grade: 65/100 Lore: 20/25 Honestly a really interesting test. Not only is it creative, it actually fits the foundations theme of learning new ways to contain anomalies, as well as preventing danger when a breach does occur. Format: 10/25 Standard research format. Nothing very interesting or new. If you do want more points in this category, you can alter the format if you wish, or even create your own document. Presentation: 15/25 Easy to read, but the formatting is standard and is basically already designed to be that way. Similar to the above, feel free to alter the format if you feel like you can add more spice to the log, or an entry for new information. Writing: 20/25 Good usage of standard research terms. Feels like an official entry, but on a much smaller scale. Notes: This is a pretty short entry for a foundation document; it likely could have been suitable just as an activity log. A good way to get more material for these documents is to bundle together multiple tests, much like a "Study" of a specific SCP instead of a singular test.

Grade: 45/100 Lore: 20/25 The test is decently realistic, and the test logs helps explain the details of the experiment pretty well. The conclusion is properly used and gives room for future testing, which is a massive benefit in any type of document. Format: 10/25 Uses the basic enforced research format, but not a lot of creative use. If you are not creating a formal document, you can use the features the forums provide to make your logs more appealing and possibly easy to understand. Presentation: 10/25 A decent attempt was made, but the professionalism of the log could use work. A good way to do this is by looking at official SCP documents from the wiki, or looking at other works by more proficient researchers. You can understand and inherit some of their habits. Writing: 5/25 Many spelling and grammar mistakes that tend to take away the effect of the research log. Notes: A lot of these issues can be easily solved by proof-reading your documents. It may not seem like it but you tend to notice more mistakes when you actually go back and read your work in full. With more practice, and proof-reading to erase silly mistakes, you may find great success in your future research documents.

+support

https://docs.google.com/document/d/1PI34b0yQP6XOeqnek_w6oaXkPeFaY4a0cxno6NwJzEU/edit?usp=sharing