Nydekore

As an avid roleplayer powerful SCPs /= better RP. If anything half these SCPs would be so much easier to RC because the foundation has discovered methods to recontain them. SCP breaches are combat, not roleplay, and long duration breaches keep roleplayers locked up in bunks or otherwise incapable of performing their duties. +Support as 610 is far too powerful right now, giving 10 seconds from infection to infection makes more sense in lore anyways as infections are not immediately contagious from one person to the next.

BRO WTF? Fat o7 man

Damn, all the old CI guys… Skela better not be next o7 Orange, big respect to you

We didn’t always see eye to eye but o7 nonetheless, even if we didn’t always agree I’ve still got massive respect for you, best of luck man

Written Test Log Format If you are creating a written log, include all of this information in your writing. Lore Rank/Name: SCP #: Test Idea: Background Research: Hypothesis: Observations (what happened?): Evidence/Visual Stimuli (Images): Analysis/Conclusion (was your hypothesis correct, why or why not, how can this discovery benefit the foundation?): Audio/Visual Test Log Format If you are creating an audio/visual log, include all of this information in the audio or video. Lore Rank/Name: SCP #: Test Idea: Background Research: Hypothesis: Observations (what happened?): Further Evidence: Analysis/Conclusion (was your hypothesis correct, why or why not, how can this discovery benefit the foundation?): Notice: Try your best to keep OOC interaction out of your audio/video logs. We know it is not always possible due to the nature of the server but it greatly improves the quality of your log. Incident Log Format Did something unusual happen on site causing you to take a deeper look? Use this format to document this incident. Lore Rank/Name: SCPs/Personnel involved: Date/Time of Incident: What occurred in this incident? (Causation, Hazards, Casualties): Ideas to prevent this from happening again?: Google Docs Templates While forum posts are acceptable, we find that google docs allow for more freedom and creativity. Feel free to use any document formatting you like but we find these to be easily utilized and of great quality. Foundation Document Format 1 By Cecil Foundation Document Format 2 By Dr Placeholder McDoctorate (Billybob) Notice: All content inserted into a test log should be your own or properly credited. We do not condone plagiarism in any way. Unauthorized usage of another person's work will result in disciplinary action.

-Support On top of already receiving a ban, they've also been removed from research recently due to troublesome behavior.

-Support for just one reason Many job codes start with the branch they belong to, i.e. "research_high_command" There are chat commands you can to do access these jobs which is simply /(job code here) But because of comms, if I were to do /research_high_command it would think that I was trying to access research comms because the command I did started with "/research" The only way to get around that is to capitalize the job codes name as the comms don't pick up on that. It's a small thing but there have been times where the f4 menu has broken and I've had to use those commands, this would disrupt that alternative option.

If Zeeptin banned him it’s likely because he did something to personally annoy Zeeptin and it’s likely he would do so intentionally. It’s really hard to unintentionally get noticed by Zeeptin for anything which means annoying him was likely intended. Don’t play games you don’t win. -Support

Topic moved

DENIED We here in Research High Command do believe in second chances. However, we find that your prior conduct is inexcusable. While you only touched on your disobedience with command in your appeal, your full blacklist reason is as follows: "ERPing, Breaking ROE, Cuffing Researchers, Breaking SOP." Your blacklist will be over April 6th which is about 1 month away, at that point you will be able to return to the branch in, what we hope to be, much better conditions for all parties involved.

While this is not necessarily what this suggestion is about as SCPs CAN breach during testing already, I will look into making a proper "incident report" format to put perhaps in the Foundation Test Logs forum.

-Support While I agree researchers shouldn’t abuse this, it’s something Moonrose and I can work to enforce. This could lead to minges breaching SCPs by claiming it was “for testing”

Was worried when I saw the comments about this situation, however I am satisfied with this response and with the overall quality of this application. +Support

-Support unless you can provide actual specifics.

What are you suggesting? - I suggest that the NLR timers of any "-2" SCPs (anyone that is infected by an SCP, essentially) begin when they were infected, not when they die. How would this change better the server? - This will benefit the server as a whole as 049-2's, 610-2's, and 035-2's will no longer be trying to die as quick as possible in order to just start the clock on the NLR timer as, for the most part, if they survive 2-3 minutes as a -2 instance they can leave spawn again pretty much right away (though, of course, still losing any RP information.) Personally I HATE playing as -2's as I am not much of an SCP player so it sucks being forced into being one. It would make the experience more bearable if I didn't have an experience I did not much enjoy just to then sit in spawn for 3 minutes after. Are there any disadvantages of making this change to the server? If so, explain. - It might get foundation combatants back into fighting these types of SCPs quicker, however I think that is a fair trade off considering how powerful 035 and 610 are currently and also they obviously can't just run back to the -1 as that would be metagaming. Who would this change mostly benefit? - Mostly MTF because they are probably the most prone to infection (because they have to deal with the breaches) however I think most people will find this change to be a net positive. Please link any workshop content, screenshots, or anything that you think may be helpful to those who view this suggestion - N/A

Not really, GOC is essentially the UN, it is HIGHLY against CI’s tactics as they commit themselves to what is essentially guerrilla warfare

+Support, I believe CI are responsible enough to regulate this

I would be more accepting of this if he weren't so god damn tanky. He's legit 450 | 100 if I remember correctly, grabbing maintenance and medical -2's would make him invincible. Would be willing to trade cooldown being moved to 3 minutes (2 would be too few considering the health and equipment of its -2's) in exchange for banning usage of medkits OR a health nerf of -1.

-Support, he put “helpey bot” in the title Jk, +support, I see him on maintenance quite a bit, I think he’d be good for it

+Support He has many prior warnings for FailRP on SCPs, should have read the MOTD by now. Shows laziness/carelessness to have not.

-Support Nu7 CMD (and I hope D5 CMD) work to keep them out already. No need for MOTD change as you can report to a CMD member if they’re in there when they shouldn’t be

Nope ;’(

Noooooooooooooooooooooo funny PT guy

-Support We'll miss you Shin

-Support Kinda obvious that if you aren’t breached you shouldn’t be doing that stuff, at least in my opinion