Rule Suggestion Allow Class-D to breach 008

["Businessman"]

What does this suggestion change/add/remove:
Removes the rule:


Has something similar been suggested before? If so, why is your suggestion different?:
I don't believe so

Possible Positives of the suggestion (At least 2):
+More RP Possibilities for Class-D
+No more RP dictating rule
+Encourages people to play Class-D

Possible Negatives of the suggestion:
- 4% increase in 008 breaches.

Based on the Positives & Negatives, why should this suggestion be accepted:
Using rules to protect something from being breached is just a lame way.

 

[Emilia Foddg]

I think another thing to mention here is that by viruue of both increasing the complexity of how 008 is allowed to breach and the fact that thsi is a Staff-enforced measure, whether through miscommunication, misinterpretation or just outright minging, it may spur failbreaches (i.e. people taking the rule change wrong and thinking they can do it in circumstances they can't, or otherwise trying to use the changes as cover for intentional failbreach (such as feigning the former)) - And to my understanding, 008 failbreaches are notoriously the worst to deal with because of the way spores work (In the past, it's been possible for them to get into some really weird places most notably being tight map geometry, such as in train station or even outside of the map bounds, which means they can stay unnoticed and continue spreading from there until discovered).

So this could add extra unnecessary hassle & headache from a Staff perspective - Which also to my understanding is another reason why 008 breaches are confined to being causable by CI only. Not sure why I didn't cover this before in the thread, as I went over it in my prior suggestion on this topic.

 

[Sule Goodman]

r y'all stupid.. i dont even play the server and even i know it says
'DANGER, ZOMBIE VIRUS, DANGER, ZOMBIE VIRUS, 100% LETHAL' around 008 chamber...

talkin about 'how they gonna know' they got eyes lil homie...

Thats only on UK btw, US server doesnt have that

 

[Doug 'TrippleD']

Also, let’s be honest breaching SCP-008 as a D-Class would be extremely difficult. The rule requiring at least 12 MTF members online ensures that these breaches only happen during high-pop rounds, where there’s enough personal to handle the situation. On top of that, a Class-D would still have to:

• Escape D-Block,
• Navigate into LHCZ,
• Hack through multiple clearance levels (CL4 Bio and CL5),
• And finally reach the containment chamber to trigger a breach.

This is not something that will happen easily or often. But when it does, it would be amaizing, "a Class-D managed to breach 008 wow".

We're talking about d-class in low pop who sit around disguised for 3 hours then call a metagame sit as soon as they die to anything.
Additionally, d-class wont really give a shit about the 12 MTF requirement, its happened before where d-class have breached 008 in low pop and its taken over an hour to get resolved and the entire day for staff to investigate what happened.

D-class know how to hack, its not that difficult.
The hardest part for them would be getting a hostage to inject it into, but they'd probably inject themselves or another d-class.

 

[Fexxyzin]

We're talking about d-class in low pop who sit around disguised for 3 hours then call a metagame sit as soon as they die to anything.

This is a player behavior issue, not a problem with SCP-008 or the rule itself. If certain players are abusing disguises or misusing sits (what in the context you gave they'r aren't), that should be dealt with individually, not by restricting RP possibilities for everyone. Bad behavior from a few palyers shound't define the rules for the entire community.

---

Additionally, d-class wont really give a shit about the 12 MTF requirement, its happened before...

If that’s true, then the issue is enforcement, not the idea of the breach itself. If the 12-MTF rule is being broken, the solution is clearer logging, better communication, or staff warnings, not a complete ban on 008 breaches from Class-D individuals.

---

D-class know how to hack, its not that difficult.

Knowing how to hack ≠ being able to successfully breach 008. The physical access to the chamber, avoiding detection and injecting someone, these are all major steps that take time and expose the Class-D to risk. The breach isn’t meant to be impossible, just very difficult and rare. And with the 12-MTF rule, it's already a stuggle.

---

The hardest part for them would be getting a hostage to inject it into, but they'd probably inject themselves or another d-class.

Exactly and that’s not a problem. That’s RP. If a D-Class injects another, that becomes a containment emergency. That’s gameplay. If they inject themselves, they’re basically sacrificing their life to cause chaos and that’s no different than breaching any other SCP or going in a killing spree.

 

["Businessman"]

We're talking about d-class in low pop who sit around disguised for 3 hours then call a metagame sit as soon as they die to anything.
Additionally, d-class wont really give a shit about the 12 MTF requirement, its happened before where d-class have breached 008 in low pop and its taken over an hour to get resolved and the entire day for staff to investigate what happened.

D-class know how to hack, its not that difficult.
The hardest part for them would be getting a hostage to inject it into, but they'd probably inject themselves or another d-class.

If they don't listen the rules, what stops them from breaching it anyways?

 

[Doug 'TrippleD']

If that’s true, then the issue is enforcement, not the idea of the breach itself. If the 12-MTF rule is being broken, the solution is clearer logging, better communication, or staff warnings, not a complete ban on 008 breaches from Class-D individuals.

Staff arent on 24/7. USA has has problems with lack of staff for a while and this is simply something from lack of manpower. UK staff hop on sometimes to help out but they cannot be relied on.

Logs are already very clear and precise, there is a limit on what you can do and you have to go up the chain of command, gather opinions and a lot of things before making a decision. Additionally, staff like to wait to bring people into sits so we can talk to them and get their side of the story and they arent always online.

This is a player behavior issue, not a problem with SCP-008 or the rule itself. If certain players are abusing disguises or misusing sits (what in the context you gave they'r aren't), that should be dealt with individually, not by restricting RP possibilities for everyone. Bad behavior from a few palyers shound't define the rules for the entire community.

Are you seriously calling an SCP-008 breach an rp possibility? Thats one of the worst arguments I've ever heard. (please fix your spelling also, this was painful to read)

Knowing how to hack ≠ being able to successfully breach 008. The physical access to the chamber, avoiding detection and injecting someone, these are all major steps that take time and expose the Class-D to risk. The breach isn’t meant to be impossible, just very difficult and rare. And with the 12-MTF rule, it's already a stuggle.

E-11 aren't known on the UK server to be extremely active, and its not fair for anybody to be guarding the containment chamber 24/7 and getting bored just to protect the chamber from pesky d-class who b-line down there and claim metagame when they get killed for killing half the site staff.

Exactly and that’s not a problem. That’s RP. If a D-Class injects another, that becomes a containment emergency. That’s gameplay. If they inject themselves, they’re basically sacrificing their life to cause chaos and that’s no different than breaching any other SCP or going in a killing spree.

Injecting a member of your team with 008 purposefully is against server rules. Yet again, causing a massive breach and wasting hours of staff time and player time cleaning up some d-class's mess on the daily is NOT roleplay. Causing chaos (to promote roleplay, ie causing crimes and getting tribunalled, etc) and giving the middle finger to server health are completely different.

 

[Alex Bones]

This could be good and it could also be a disaster, from what I see D-Class would not willingly inject themselves with SCP-008 however they could inject someone else (in RP that would be a foundation member not another D-Class. If D-Class were allowed to breach 008 they would need to know where it is located and to some degree what it does, all in RP of course. This could allow CI to give such information to D-Class in order for them to breach it which both will bring passive and active roleplay.

All in all I actually agree that D-Class should be allowed to breach SCP-008 after asking staff whether or not they have a valid reason for it.

 

[Emilia Foddg]

Honestly... Is there any situation in which injecting yourself with 008 is a valid breach?

I don't think there is. Can we like adjust the 008 syringe SWEP to remove the ability to inject yourself? I know the SWEP is an adaptation of something from.... Was it MRP? I forget. But I feel like having the actual ability to do something we're not allowed to do is more hassle than it's worth, especially since these are 008 (fail)breaches we're talking about.

 

[Zen]

Honestly... Is there any situation in which injecting yourself with 008 is a valid breach?

I don't think there is. Can we like adjust the 008 syringe SWEP to remove the ability to inject yourself? I know the SWEP is an adaptation of something from.... Was it MRP? I forget. But I feel like having the actual ability to do something we're not allowed to do is more hassle than it's worth, especially since these are 008 breaches we're talking about.

At the very least, it should be changed so that accidentally injecting yourself isn't possible. Like, a confirm prompt or something. I think rn if you right-click by accident while holding it, it just insta-injects yourself.

 

[Sule Goodman]

At the very least, it should be changed so that accidentally injecting yourself isn't possible. Like, a confirm prompt or something. I think rn if you right-click by accident while holding it, it just insta-injects yourself.

I will say , a "are you sure?" pop up would be great. Theres been times my brain went stupid and during sampling I've almost injected myself instead of the D class.

 

[Puma 'Providence']

Just make a pop up like what Sule said that says something like “oh less than 12 MTF online so you can’t pick this up as a d-class”

 

[Fexxyzin]

Staff arent on 24/7. USA has has problems with lack of staff for a while and this is simply something from lack of manpower. UK staff hop on sometimes to help out but they cannot be relied on.

That’s true, no server has 24/7 staff coverage, including this on. But the solution to that could be limiting breaches to high-pop rounds (e.g. 12+ MTF online, and certain hours of the day where more staff members are present), not banning entire RP scenarios. If staff presence is inconsistent, it makes more sense to apply those rules instead of permanently removing the option.

---

Logs are already very clear and precise, there is a limit on what you can do and you have to go up the chain of command, gather opinions and a lot of things before making a decision. Additionally, staff like to wait to bring people into sits so we can talk to them and get their side of the story and they arent always online.

Yes and that’s exactly why they’re effective when used. If it takes time to gather all sides of a story, that’s part of the process. No system is perfect, but that doesn’t justify blanket bans.

Rare breaches are meant to test the Foundation, not exist in perfect control. If something goes wrong once in a while, it’s not failure, it’s a chance to learn and improve how everyone in the site handles the situation, creating RP scenarios in the future (like briefings, trainings and drills).

---

Are you seriously calling an SCP-008 breach an rp possibility? Thats one of the worst arguments I've ever heard.

Why? SCPs exist to create tension, fear, and response. Containment breaches are a core part of SCP lore and gameplay (this includes the SCP-RP server), they're not out of place. SCP-008 is dangerous, yes, but that's the point. So is SCP-076, 682, or even Type-Green in the wrong hands, yet all of those are used in RP and can be breached by Class-D.

Calling SCP-008 breaches “not RP” ignores the fact that RP often involves disaster, escalation, and reaction. A D-Class sacrificing himself to release SCP-008 with high pop, oversight and following the rules could be one of the most intense and interesting, breach the site as seems. It’s all about how it's done.

---

E-11 aren't known on the UK server to be extremely active, and its not fair for anybody to be guarding the containment chamber 24/7 and getting bored just to protect the chamber from pesky d-class who b-line down there and claim metagame when they get killed for killing half the site staff.

That’s a behavioral issue, not an issue with the concept itself. Nobody is asking for 008 to be freely accessible. A properly set up breach would:

• Require multiple layers of effort (escaping, hacking, navigating),
• Be rare due to the 12-MTF rule,
• Still be punishable if abused.

If a D-Class kills half the site and screams “metagame” when he dies, he might be completely right, he as all the rights to question if he was “metagamed” or not.

---

Yet again, causing a massive breach and wasting hours of staff time and player time cleaning up some d-class's mess on the daily is NOT roleplay. Causing chaos (to promote roleplay, ie causing crimes and getting tribunalled, etc) and giving the middle finger to server health are completely different.

Yes, under current rules. But if the rule changes to allow 008 breaches under specific conditions, those rules would naturally be adjusted too. Players wouldn’t just go around randomly injecting others it would require planning, risk, and timing.

Also, if a Class-D injects himself, that’s not breaking any rule. That’s playing a deranged, self-sacrificing character, which fits the SCP universe perfectly. A containment breach should be something the Foundation fights to stop, not something that’s never allowed to begin with.

---

Injecting a member of your team with 008 purposefully is against server rules.

This one should be one of the rules that would naturally adjust, all Class-D members shouldn’t be considered as a team, but more likely to be in a “marriage of convenience”, they would’t be allowed to kill or act against each other for no reason, but if for exemple someone was snitching to the guards or is a trustee with a work permit (what could be seen as betrayal’d by other Class-D’s) it would make them viable to infected with 008.

I’ll go a bit a further and please correct me if i’m wrong here, but I’ve heard people saying that Class-D are part of the Foundation faction, what in my eyes is complete bullshit, despite being in the same faction in the selecte character menu, I argue that they have very different opinions, objectives and goals, making them completely different “factions”.

 

[Sule Goodman]

---

Why? SCPs exist to create tension, fear, and response. Containment breaches are a core part of SCP lore and gameplay (this includes the SCP-RP server), they're not out of place. SCP-008 is dangerous, yes, but that's the point. So is SCP-076, 682, or even Type-Green in the wrong hands, yet all of those are used in RP and can be breached by Class-D.

Calling SCP-008 breaches “not RP” ignores the fact that RP often involves disaster, escalation, and reaction. A D-Class sacrificing himself to release SCP-008 with high pop, oversight and following the rules could be one of the most intense and interesting, breach the site as seems. It’s all about how it's done.

---

The reason why people say 008 isnt RP - is.... well it isnt. It completly halts any ongoing roleplay, can take up to 2 hours to combat with spores rebreaching it constantly. Its nearly impossible to have decent roleplay with zombies runnin around. I'm not saying SCps themself are RP, but having a nearly uncontainable breach daily, completely ruins RP.

 

[Driver]

 

[Aphex]

honestly i’d be fine with this if the decontam airlock cant be hacked with less that 90 players or sumth

 

[Doug 'TrippleD']

That’s true, no server has 24/7 staff coverage, including this on. But the solution to that could be limiting breaches to high-pop rounds (e.g. 12+ MTF online, and certain hours of the day where more staff members are present), not banning entire RP scenarios. If staff presence is inconsistent, it makes more sense to apply those rules instead of permanently removing the option.

---

Yes and that’s exactly why they’re effective when used. If it takes time to gather all sides of a story, that’s part of the process. No system is perfect, but that doesn’t justify blanket bans.

Rare breaches are meant to test the Foundation, not exist in perfect control. If something goes wrong once in a while, it’s not failure, it’s a chance to learn and improve how everyone in the site handles the situation, creating RP scenarios in the future (like briefings, trainings and drills).

---

Why? SCPs exist to create tension, fear, and response. Containment breaches are a core part of SCP lore and gameplay (this includes the SCP-RP server), they're not out of place. SCP-008 is dangerous, yes, but that's the point. So is SCP-076, 682, or even Type-Green in the wrong hands, yet all of those are used in RP and can be breached by Class-D.

Calling SCP-008 breaches “not RP” ignores the fact that RP often involves disaster, escalation, and reaction. A D-Class sacrificing himself to release SCP-008 with high pop, oversight and following the rules could be one of the most intense and interesting, breach the site as seems. It’s all about how it's done.

---

That’s a behavioral issue, not an issue with the concept itself. Nobody is asking for 008 to be freely accessible. A properly set up breach would:

• Require multiple layers of effort (escaping, hacking, navigating),
• Be rare due to the 12-MTF rule,
• Still be punishable if abused.

If a D-Class kills half the site and screams “metagame” when he dies, he might be completely right, he as all the rights to question if he was “metagamed” or not.

---

Yes, under current rules. But if the rule changes to allow 008 breaches under specific conditions, those rules would naturally be adjusted too. Players wouldn’t just go around randomly injecting others it would require planning, risk, and timing.

Also, if a Class-D injects himself, that’s not breaking any rule. That’s playing a deranged, self-sacrificing character, which fits the SCP universe perfectly. A containment breach should be something the Foundation fights to stop, not something that’s never allowed to begin with.

---

This one should be one of the rules that would naturally adjust, all Class-D members shouldn’t be considered as a team, but more likely to be in a “marriage of convenience”, they would’t be allowed to kill or act against each other for no reason, but if for exemple someone was snitching to the guards or is a trustee with a work permit (what could be seen as betrayal’d by other Class-D’s) it would make them viable to infected with 008.

I’ll go a bit a further and please correct me if i’m wrong here, but I’ve heard people saying that Class-D are part of the Foundation faction, what in my eyes is complete bullshit, despite being in the same faction in the selecte character menu, I argue that they have very different opinions, objectives and goals, making them completely different “factions”.

I dont get how any roleplay is obtained from a zombie virus killing half the site, ruining roleplay situations and planned events. It destroys, delays and cancels a lot more roleplay than it could create. And thats not even including the massive roleplay reset (site wide amnestication) after it, or the hours of torment that can also happen which results in an alpha warhead detonation.

honestly i’d be fine with this if the decontam airlock cant be hacked with less that 90 players or sumth

This seems a bit more realistic and allows for people to properly fight back against it and avoid low pop breaches and much less roleplay harm.

 

[Langstädtler]

I will say , a "are you sure?" pop up would be great. Theres been times my brain went stupid and during sampling I've almost injected myself instead of the D class.

Yeah that happens to me to, the ammount of times i drank the Medicine i was about to give someone is not something i wanna talk about

 

[Joe 'Gluttony' bardon]

-Support
just no

 

[Fexxyzin]

I dont get how any roleplay is obtained from a zombie virus killing half the site, ruining roleplay situations and planned events. It destroys, delays and cancels a lot more roleplay than it could create. And thats not even including the massive roleplay reset (site wide amnestication) after it, or the hours of torment that can also happen which results in an alpha warhead detonation.

This seems a bit more realistic and allows for people to properly fight back against it and avoid low pop breaches and much less roleplay harm.

I understand your concern, but I think you're viewing the worst possible outcome as the standard, when in reality, SCP-008 breaches can be controlled, rare, and even supportive of broader RP if handled right.

Yes, an 008 breach can cause chaos, but chaos isn’t the opposite of RP, it’s a part of it. A dangerous containment failure forces the site to react MTF and ERT gets deployed, Command has to organize, researchers go into lockdown, medics treat the infected, and so on. That's not the death of RP, that is RP, just a more urgent form of it.

About it "ruining" planned events, that’s an execution issue, not a problem with 008 itself. The breach could easily be time-locked, approved by staff beforehand, or disallowed during scheduled events. That’s something the rules can control. We already pause or limit certain events when major things happen on the server, it’s nothing new.

The site-wide amnestication isn’t a loss of RP either. If anything, it’s a great way to reset the tone of the server and give players a reason to engage in post-breach activities like:

• Emergency drills
• Internal investigations
• Staff briefings
• Promotion of new procedures

Those are all RP moments that only happen when something dramatic has occurred. A clean, perfect site round after round doesn't create long-term interest. High stakes events, even rare ones, are what people remember.

And finally, yes, if someone griefs with 008 or breaks the rule while doing it, punish them. But don't punish the entire playerbase.

The solution isn’t banning risk, it’s managing it.

 

[DanielRLS]

-Support where you get the 4% form