Denied Ruling Change (6.5 SCP-008) - Allow D-Class Type Blue to breach 008 (No Other D-Class)

This suggestion has been denied and will not receive development.
Status
Not open for further replies.

Emilia Foddg

Trial Game Master
Trial Game Master
Donator
Jul 15, 2023
1,035
221
41
What does this suggestion change/add/remove:
The suggestion is to make the necessary changes to the rules for 008 breaches, to allow for D-Class Type Blue (and only Type Blue, no other D-Class) to be able to cause a breach of SCP-008, on account of not only how rare a D-Class TB is, but also the likelihood of them ever making it out of D-Block and down to 008 within their lifetime, is extremely low.
First off, I am not suggesting that D-Class TB be able to cause a breach by injecting themselves. That should remain against the rules as an invalid form of 008 breach.
They should be able to do so with a hostage. My understanding is that under the current rules, they are able to deliver a vial to CI and cause a breach that way, but it would make general RP sense that they should also be able to threaten a breach by holding a hostage in the 008 CC, ala how CI are able to do so.

Currently, the rules regarding who can breach 008 and how, are restricted to F, CI and GOC - Only able to with 12 or more MTF members on, only able to inject someone of the opposite faction to cause a breach, with MC&D, SCPs & D-Class being completely ineligible. My understanding is that there's also a restriction on how often 008 can breach, as well? Not entirely sure about that one, someone can correct me on that. My point is, the current restrictions are stringent and with good reason, for balance purposes. It would be too much if any D-Class were able to cause a breach.

Of course, if TBs were allowed, then that means that D-Class as a faction, could feasibly riot with TB support and make their way to the CC with significant effort, with the TB poised to cause a breach. This of course would be somewhat equivalent to a CI 008 raid in terms of both it making sense in RP, but also in terms of feasibility. Not every 008 raid makes it to 008 and causes a breach, instead getting repelled - a co-ordinated D-Class riot would be comparable to this, maybe even less, considering that D-Class are not typically a well-organised group - They would have to reasonably co-ordinate the riot, make it through GenSec out of D-Block, through anyone they encounter in LCZ, then through E-11 in HCZ, then needing the equipment and/or time necessary to make it through the CL4 doors into the 008 CC. If at any point during their attempt, they switch to subterfuge to try and make it to 008 CC (with TB included), it would switch over to a Code 1 and the obstacles presented in that situation would have to be overcome, in order to get into a position to potentially breach 008 (and the TB needs to live through all of that regardless of how it goes, since they would be the only one able to cause the breach. It can't just be any random D-Class).

The suggestion is simple - Adjust Rule 6.5 in a way that allows D-Class TBs (again, I can only stress this enough, only TB, no other D-Class) to be able to cause an 008 breach with a hostage. Has to be either a Foundation, CI or GOC hostage - Cannot be another D-Class. Other restrictions to 008 breaches should also apply under these circumstances. As it is, the rule is written as follows, from SCP-RP Rules:

6.5 SCP-008:
  • Picking up, holding, and injecting a SCP-008 sample counts as breaching SCP-008.
  • To breach SCP-008, there must be at least 12 MTF units active.
  • You may only inject someone of the opposite faction to breach SCP-008.
  • SCP-008 may not be breached by SCPs, Class-D, or MC&D. SCPs may not break the furthest airlock door in SCP-008s chamber, unless they are chasing someone.
And this suggestion aims to alter it so that it would read as follows, or at least similar to:

6.5 SCP-008:
  • Picking up, holding, and injecting a SCP-008 sample counts as breaching SCP-008.
  • To breach SCP-008, there must be at least 12 MTF units active.
  • You may only inject someone of the opposite faction to breach SCP-008.
  • SCP-008 may not be breached by SCPs, Class-D, or MC&D. SCPs may not break the furthest airlock door in SCP-008s chamber, unless they are chasing someone.
    • Class-D Type Blues are exempt from this, and may only breach SCP-008 by injecting it into a Foundation, CI or GOC hostage. A Class-D Type Blue may not inject either themselves or a Class-D hostage in order to breach SCP-008.


Has something similar been suggested before? If so, why is your suggestion different?:
Searching the suggestions forum has turned up no similar suggestions to this. The forum doesn't allow you to search "TB" and "008" individually and even together, but a search for "type blue 008" returns no 008-related suggestions regarding D-Class TBs. The likelihood of this suggestion being original is high.


Possible Positives of the suggestion (At least 2):
  • D-Class (especially TB) get another potential riot objective other than escaping the Foundation, however it requires a TB, co-ordination and for that TB to survive and make it to 008.
  • Another method of creating hostage situation RP between D-Class and Foundation, that would make in-RP sense to occur.
  • Possible CI raid objective - Infoleak 008 to D-Class, arm them and get them to riot all the way to 008. Lots of co-ordination and effort required to successfully pull off (still requires a TB in the first place), generally an extra thing for them to do, CI could breach 008 anyway, but if all CI die and D-Class w/ TB make it to 008, they can at least continue instead of being stopped because it's otherwise against the rules for D-Class to breach 008 (although, if the TB dies, then they have to stop anyway, plan ruined, see below).


Possible Negatives of the suggestion:
  • Since this would add another valid vector for 008 breaches, this invariably raises the possibility of a 008 breach at any given time and potentially the overall frequency of them.However, there are already strict limitations on the validity of 008 breaches, as well as the already mentioned, tiny likelihood of a D-Class TB escaping D-Block, getting down to 008, with a hostage, ready to threaten a breach - The increase in breaches would be minimal at best and likely entirely negligible, compared to the current state of affairs.
    • Although, this may make it easier for CI to breach 008 if they co-ordinate their efforts with D-Class TB as outlined above - But that would require a prepped CI raid to make it to D-Block and a TB to be active, even more unlikelihood to balance out the increased likelihood that CI assistance grants.
  • Scenario: Rule changed, D-Class riots with TB, somehow make it to 008, TB dies in the process. D-Class plan is ruined because womp womp, non-TB can't breach 008. Ruined roleplay at best, D-Class get frustrated and just failbreach it at worst. Standard failbreach protocol applies, might be frustrating to deal with if it gets frequent, but again, TBs are rare. Even as it is now, D-Class can still make the attempt, it would just be against the rules for any of them, even TB, to cause the breach - Wouldn't stop them from trying. Sure, the rule change might incite it a bit, but why is the rule change at fault for people otherwise breaking them? People's perceptions of the rules do not change the rules themselves.


Based on the Positives & Negatives, why should this suggestion be accepted:
It's another thing for D-Class TB to do that makes sense for them to be able to do given the circumstances, between the general rarity of TB, cohesion and general capability of D-Class to properly co-ordinate a riot that would successfully make it to 008 through all obstacles with TB still alive and against all other relevant mitigating factors - This should not realistically impact server health with the given difficulty of the feat; There is no reason to expect 008 breaches left and right because suddenly D-Block TBs are able to cause them.

There are enough barriers in the way for me to believe that this is a completely reasonable ask. Like, if you say that it would encourage D-Class (non-TB) in general just start trying to breach 008 as a result of this change, then any successful attempts by them would still be invalid. We have staff for a reason. If they start saying "well we can do it because TB can," then they're just wrong and getting a FailRP warning. Like, what's the -Support here? Genuinely, please let me know, I'm curious. I guess US wouldn't like it because my understanding is that US aren't as good as dealing with 008 breaches as UK for some reason? I really can't see a reason why this isn't a reasonable change.


Some things to consider before replying:
In a Discord discussion regarding TB being able to cause an 008 breach, the following RP point of "From a prisoner's perspective, between having a chance at escaping and causing the end of the world, it would make more sense that the former would be chosen" was raised. My response was that there is a roleplay case to be made here and it can entirely depend on the prisoner's disposition. These are death-row inmates after all - It is not unreasonable for someone who might love to kill, on discovering the existence of a deadly weapon, to want to use it for that purpose.

It was also raised that the TB is decaying, actively dying and that it doesn't matter if they escape, but the knowledge of whether it's curable or not is not truly known to the D-Class, IC. Foundation Thaumatologists don't decay, CI TBs don't decay(? I don't actually know if this one is true, could someone clarify this for me?) CI TBs do apparently decay. It's reasonable to assume that IC, a D-Class TB should seek GOC/CI's assistance in trying to cure their decay (however, on the topic of IC knowledge, they are unlikely to know about GOC IC, either). However, the speed at which TB is dying may make this infeasible. To this, I posited that it's not unreasonable for someone in TB's position to deliberate between 'taking a non-guaranteed chance at fixing decay' or 'just giving up and deciding to try and take everyone else with them.'
 
Last edited:

Jack "Fubar" Daniel

Active member
Feb 10, 2023
86
15
21
-Support
First off, nice suggestion, its nicely written out and not a quick soy suggestion for once. For me, it should stay as a CI only thing for it to breach; if d-class TB gets the ability to get 008 it will be a hell of a lot harder to stop, especially if the TB is good. If one manages to get a syringe, all they need to do once they have it, disguise of not even, is to bullet freeze and just inject someone. Just at the end of the day, allowing another class to raid for 008 if they learn about would just be a disaster especially during early mornings.
CI TBs don't decay(? I don't actually know if this one is true, could someone clarify this for me?)
Also they do decay
I guess US wouldn't like it because my understanding is that US aren't as good as dealing with 008 breaches as UK for some reason?
When like 80 percent of the breaches start in d-block/medbay its impossible to really contain, even when only 1 term of ert deployed for a lot of 008
 

Snowson

Active member
Jun 20, 2023
47
11
21
-support
Likely to be abused by metagame-type blues (Instantly knowing where the 008 cc is, what it does, how to use the syringe) despite having no in-character knowledge of 008
 

Emilia Foddg

Trial Game Master
Trial Game Master
Donator
Jul 15, 2023
1,035
221
41
Also they do decay
Thanks, edited.

Something i'd also like to add - Just to anyone that may believe it to feel weird that "TBs would be able to, but not regular D-Class", remember that TBs are considered very different to regular D-Class in a lot of terms, for instance, mechanically, they are immune to FearRP in a similar way to Thaumatologists and IC tend to be considered SCPs with high priority to terminate; Usually being considered an E-11 matter to assist with disposal. Among other potential differences I might be unaware of.

So if they're so different to regular D-Class in all these myriad ways, why are they also considered part of D-Class when it comes to breaching 008? There's a huge barrier to entry .
-Support
First off, nice suggestion, its nicely written out and not a quick soy suggestion for once. For me, it should stay as a CI only thing for it to breach; if d-class TB gets the ability to get 008 it will be a hell of a lot harder to stop, especially if the TB is good. If one manages to get a syringe, all they need to do once they have it, disguise of not even, is to bullet freeze and just inject someone. Just at the end of the day, allowing another class to raid for 008 if they learn about would just be a disaster especially during early mornings.

When like 80 percent of the breaches start in d-block/medbay its impossible to really contain, even when only 1 term of ert deployed for a lot of 008
But they would need to get back out of 008 CC in order to do that. Usually when CI raid into 008 CC, they end up getting trapped in there and have to open negotiations. My thinking here is that the same would generally happen with TBs. If the TB manages to get out of the CC, that's just a failure to protect the CC.

-support
Huh??
008 breaches already suck for the people and server
this is going to be so abused by lvl 500 dclass mains
The assertion of 'a good TB' being able to cause frequent 008 breaches with this feels like hyperbole to me. In my experience, TBs rarely get out of D-Block, let alone into HCZ. Someone's skill as TB may be able to make them put up a fight against the absolutely impossible monolith of a wall that is everything in their way to 008, but at peak times, I just don't see a TB accomplishing this, at least without CI assistance, more than at least once a month.

-support
Likely to be abused by metagame-type blues (Instantly knowing where the 008 cc is, what it does, how to use the syringe) despite having no in-character knowledge of 008
And yet the first thing a D-Class does when they get out, is dash straight for 914. I particularly enjoy the notion that a rule already being broken constitutes a good reason to not make a change already under the assumption that the rules were being followed, anyway. Fuck it, let everyone failbreach everything. Sky's the limit when you don't give a shit :skull:
 

Joris "Brexit" Bohnson

Active member
Sep 10, 2023
211
28
21
Major -Support

Nah. This is a bad idea.
A TB is annoying enough to deal with when they have combat support, and 008 breaches do not deserve to be frequent.

IF you want to shoot a horde of zombies, play CoD zombies
 

Skittles

Active member
Donator
Oct 20, 2022
644
137
21
-Support

008 breaches should stay as a test gone wrong or CI breaches it thing
 

Holland

Well-known Member
Donator
Aug 27, 2022
210
27
41
- Support

the reason D-class aren't allowed to breach it is for balance reasons same goes for TB. Making it so they can breach 008 will result in an unplayable server and a whole new way of Roleplay in a negative way.

Constant 008 breaches
 

Painter

Active member
Jun 18, 2023
437
85
21
[REDACTED]
-support

1. SCP-008 already breaches enough with CI, why let a powerful Type-Blue also breach it?

2. Deliver it to CI? How does a D-Class know what CI is?

3. How does a D-Class know what SCP-008 is? Even if they did, how would they know exactly where it is located in the facility?

4. Regardless of all other points, this isn’t a breach simulator. Why add more chances to breach an SCP that ruins RP for Foundation for 10-60 minutes and have non-combatives go sit on a wall for half an hour while combatives go and die repeatedly to SCP-008 until the nuke goes off.
 

Zen

Active member
Sep 16, 2023
485
146
21
+Support if you manage to get all the way to 008 as a TB, we deserve the breach.

Plus, I honestly don't think they happen that often. People are complaining like they happen every time they're online, but I haven't seen one in weeks. Maybe it depends on what time you're usually on, I guess.
 

Blackknight95

Super Administrator
Super Administrator
SCP-RP Staff
Group Moderator
Jun 7, 2022
341
52
21
21
Suggestion Denied


Hello Geldo,

Superadmins discussed this last night, and we agree that this change will be denied due to the fact that 008 can and often does interrupt RP on a large scale up to multiple hours at a time. 008 is something that almost always results in an RP reset, and having it strictly controlled by only allowing CI to breach it is a way to prevent a lot more 008 breaches than there are now.

Regards,
SCPRP SSL team.​
 
Status
Not open for further replies.