What does this suggestion change/add/remove:
Trial the following for at least a week:In "6.06 SCP Specific Rules," alter SCP-008's other rules section to allow for SL+ auth for D-Class TB to be able to initiate an 008 breach - Provided this breach is not caused by injecting either themselves or a D-Class hostage. Self-injection should remain against the rules as an invalid form of 008 breach.
From:
To something more along the lines of:D-Class may not directly remove a syringe from SCP-008's containment chamber with the intention of breaching it.
It should be stressed that as a result, D-Class should not end up rioting or escaping with the express intent to eventually cause a 008 breach. This is to serve as as a fallback in the event that D-Class riot to escape and in the interest of surviving to later escape, somehow end up being pushed towards/into HCZ as a result. In such situations, these provisions should enable 008 to be a potential option, provided that the rioting D-Class have a TB and get SL+ auth. Further adjustments to the rules may be needed to clarify this.D-Class may not directly remove a syringe from SCP-008's containment chamber with the intention of breaching it. With authorisation from Server Leadership, a D-Class Type Blue may be permitted to do so.
In such situations, D-Class Type Blues may only breach SCP-008 by injecting it into a Foundation, CI or GOC hostage. A D-Class Type Blue may not inject either themselves or a D-Class hostage in order to breach SCP-008. All other normal rules regarding SCP-008 breaches still apply.
If it is determined that D-Class start escaping with the intention of causing an 008 breach, the trial should be considered to have failed.
If this is still a concern, consider delaying it in favour of changes to 008-related logging, so that Staff can better evaluate circumstances surrounding an 008 breach and better mitigate these kinds of instances of abuse.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.
Has something similar been suggested before? If so, why is your suggestion different?:
I originally put forward an idea along these lines almost three years ago, the intent there being to bring D-Class TB in-line with other factions hostile to the Foundation in terms of being able to breach 008 without being entirely restricted by ruleplay. In that suggestion, I was very explicitly crystal-clear about the idea that it should only be possible for the TB to be able to breach it, and not any other D-Class. I still hold the general stance I outline in that suggestion, which I will further elaborate in the last section. This suggestion was denied for:
After further deliberation, I agree with the general reasoning and the concern over potential disruption - But I feel this stance is somewhat overly cautious. In an attempt to remedy this, and as a significant divergence from the original suggestion (aside from this is after the rules revamp), I have added the SL+ auth requisite and statements regarding riot intentions.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.
Last year, @"Businessman" opened a far more radical suggestion asking for all D-Class to be able to breach 008 by simply removing the stipulation altogether.
This resulted in what I can only describe as the single biggest community meltdown I've seen on any suggestion, ever. It raised numerous points of discussion, all of which are relevant, and all have been addressed in the last section. This suggestion was denied for:
This resulted in what I can only describe as the single biggest community meltdown I've seen on any suggestion, ever. It raised numerous points of discussion, all of which are relevant, and all have been addressed in the last section. This suggestion was denied for:
I agree with the standpoint on harm, but not about sense. This rule in its entirety is ruleplay - Justified ruleplay - But ruleplay nonetheless. Regardless, I agree on the point that this should not be extended to all D-Class. The resulting risks are simply too high to reasonably mitigate and poses too much harm to the server's gameplay loops in the form of constant breaches. However, I still hold the opinion that it's the best suggestion this subforum will ever see. It posed an excellent question that I feel was ultimately answered incorrectly, by the community and Staff both.SCP-008 is a high risk SCP that causes significant disruption to Roleplay if there are constant breaches to the point SSL have had to moderate CI in relation to how many breaches can occur as this has harmed core gameplay loops, there is 0 logical reason in roleplay why a D-Class would release this virus as its completely antithetical to their goal of escaping the foundation, with a death chance of 99.99%, thus disallowing any chance of escape.
This would cause too much disruption and destabilisation of roleplay to allow this to be extended to D-Class outside of the fact that it doesnt make sense.
Possible Positives of the suggestion (At least 2):
- + D-Class get another potential riot outcome - Particularly if they end up failing to escape the Foundation and end up being pushed further inwards, then Foundation as a result have to deal with the miniscule possibility of an 008 breach, rather than relying on "They can't do that because it'd be against the rules."
- + Increased parity between D-Class and factions hostile to Foundation
- + Another method of creating hostage situation RP between D-Class and Foundation
- + Possible CI raid objective
- + Reduced ruleplay
- + Knock-on effect of future RP creation
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)
Possible Negatives of the suggestion:
- - Difficult to enforce whether a riot was for the express purpose of 008 breach, rather than having to resort to it, additionally difficult to auth
- - Increased failbreaches - As a result of either D-Class becoming emboldened to attempt 008 breaches when rioting, or otherwise misinterpreting the rule change which does admittedly make 008 breaching more complex and harder to understand
- - Potential minor increase in 008 breaches
- - Abuse
Based on the Positives & Negatives, why should this suggestion be accepted:
I think it's high time we re-open this discussion. Let's get some of the tedium out of the way first, by going over and addressing the wealth of past discussion, particularly what everyone's frothed at the mouth over when it comes to this (and will likely do so again regardless of what I have to say here), presented in large text so that you just look stupid if you do ignore it:#1: "008 breaches already suck for Foundation & the server in general, this is going to be abused with more constant and frequent 008 breaches, like on UK back when we had weeks of frequent 008 breaches, resulting in an unplayable server and server health dropping off the deep end."
I can kind of see the concern on UK if it's Johnson or Aki, one of the good CI TBs hopping on D-Class TB - Albeit this still completely ignores the fact that even then, from the moment they spawn in D-Block they still need to:
It becomes more a point of contention if said riot was assisted by a CI raid - At that point... Fair? But you're splitting hairs - UK CI are so experienced at breaching 008 and are pretty sensible with how they handle it that I don't think it'd be that much of a problem. If anything, it could be a fun alternative to a normal 008 breach raid for F players, at least for the people directly involved with it, and up until the point that it's breached, at which it's kinda just the same as any other 008 breach. Chances are it would be considered as an alternate, if not harder form of 008 breach raid, rather than a progression on from a D-Block raid.
And my understanding of the situation between US F and US CI is that US F are the best defenders alive - They probably wouldn't even notice a difference regardless of how far anything progresses.
This change would just not make things as dire as you seem to believe it would be. I doubt you'd notice any increase in 008 breaches at all. Maybe the confirmation bias kicking in when it first happens and have an immediate thing to blame like 'Aha, I knew it, letting them be able to breach 008 was a terrible idea.'
This is just hysteria and probably a reflex resulting from the past experience of frequent 008 breaches - I don't see this creating that type of insane, blown-out-of-proportion frequency like you all seem so desperate to believe. And I was there for those frequent 008 breaches. If UK E-11 still have their list of who has what medals, check it and see who you find under the Pest Control medal. That was during that time, and funnily enough, for an 008 breach I helped cause. The reason I'm so sure about this is because I'm not only aware of the current state of the server, but because I've seen all sides of the breach. There being no avenue for D-Class is simply needless ruleplay.
- Survive standard D-Class TB procedure and make it out of D-Block having started a riot that progresses outward
- End up absolutely having to go to Lower HCZ as part of the riot
- Survive basically every onsite combative responding to your riot between LCZ and LHCZ
- Obtain a hostage & SL+ auth for the breach for when negotiations fall through
It becomes more a point of contention if said riot was assisted by a CI raid - At that point... Fair? But you're splitting hairs - UK CI are so experienced at breaching 008 and are pretty sensible with how they handle it that I don't think it'd be that much of a problem. If anything, it could be a fun alternative to a normal 008 breach raid for F players, at least for the people directly involved with it, and up until the point that it's breached, at which it's kinda just the same as any other 008 breach. Chances are it would be considered as an alternate, if not harder form of 008 breach raid, rather than a progression on from a D-Block raid.
And my understanding of the situation between US F and US CI is that US F are the best defenders alive - They probably wouldn't even notice a difference regardless of how far anything progresses.
This change would just not make things as dire as you seem to believe it would be. I doubt you'd notice any increase in 008 breaches at all. Maybe the confirmation bias kicking in when it first happens and have an immediate thing to blame like 'Aha, I knew it, letting them be able to breach 008 was a terrible idea.'
This is just hysteria and probably a reflex resulting from the past experience of frequent 008 breaches - I don't see this creating that type of insane, blown-out-of-proportion frequency like you all seem so desperate to believe. And I was there for those frequent 008 breaches. If UK E-11 still have their list of who has what medals, check it and see who you find under the Pest Control medal. That was during that time, and funnily enough, for an 008 breach I helped cause. The reason I'm so sure about this is because I'm not only aware of the current state of the server, but because I've seen all sides of the breach. There being no avenue for D-Class is simply needless ruleplay.
#2: "This would cause low-pop/downtime 008 breaches, at stupid times of day"
Not only would this need to be authed now, but the other rules for 008 breaches still need to be followed. You need the requisite amount of MTF on and you need a valid hostage.
If you think D-Class won't follow this when no Staff are on, they already follow the existing rules, which is the primary thing that stops them other than IIRC there being a pop minimum to even hack the syringe keypad in the first place. If TB being given a method through which they may breach 008 causes other D-Class to start breaking rules, the problem isn't with any rule.
If you think D-Class won't follow this when no Staff are on, they already follow the existing rules, which is the primary thing that stops them other than IIRC there being a pop minimum to even hack the syringe keypad in the first place. If TB being given a method through which they may breach 008 causes other D-Class to start breaking rules, the problem isn't with any rule.
#3: "This will be metagamed by TBs instantly knowing where 008 is and going straight for it"
If one guy rushes to the CC, not only are they not getting auth for an 008 breach, but they're also probably gonna get a warn, especially if they follow through with a blatant failbreach attempt. Even though the first thing D-Class do when getting out is going straight for 914, this is completely different as even though 914 is a core part of the D-Class gameplay loop, but 008 is so much further out of their way that you can basically ONLY be breaking rules when doing this, even with these changes. Current enforcement can handle this just fine.
But as I state in a prior suggestion, 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
But as I state in a prior suggestion, 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

#4: "How would they get the requisite 'advanced' IC knowledge of what it is and how to use it?"
This for some reason, is the most common argument I saw against this, and simultaneously the most braindead. If you look at the big, heavy security area at the bottom of HCZ with warning signs, end up hacking your way in, getting into the room and you find syringes? You really don't need to put 2 and 2 together to be able to come to the conclusion of "the people keeping this thing locked up would really not someone getting injected with whatever's in these syringes." Like, what...? What 'knowledge' is needed here?!
I'm genuinely trying to wrap my head around this logic and I just don't see it. This line of thinking is just slop. At this point, just leave your downvote and -Support and move along.
And even IF they're blatantly metagaming or FailRPing, that's most likely gonna be caught when they try and get auth for the breach
I'm genuinely trying to wrap my head around this logic and I just don't see it. This line of thinking is just slop. At this point, just leave your downvote and -Support and move along.
And even IF they're blatantly metagaming or FailRPing, that's most likely gonna be caught when they try and get auth for the breach
#5: "This makes 0 sense, is against their goal of escape and doesn't make sense for them to be able to do" / "Why would they intentionally breach something perceived as world-ending and dangerous in RP?"
Actual partial reasoning for a prior denialBeing against their goal of escape - Yes. That's why I specify in no uncertain terms that it should be a resort and not a primary objective. All D-Class should realistically know about 008 is that if they come across its area in Atrium, it would (and should) be as a result of being pushed back further into the facility in the interest of staying alive; Seeing this thing that's locked up with tight security and if they manage to get to it, see that it's just a syringe.
They wouldn't know about its destructive effects and wouldn't have any way of knowing besides being leaked to by CI or someone else. They'd just know that this is something that's under heavy security and would probably be bad for their captors if it got out, so it would end up being a last-ditch effort to leverage breaching it to try and get out alive.
And even if they did know... These are death-row convicts. You really think they're gonna be so socially-minded as to not release the deadly zombie virus? No.
Granted for balance reasons, it should never be all D-Class that get access to this. There needs to be a compromise to allow some way of the one hostile faction to F that is specifically ruleplayed against breaching 008, to be able to do so. You can workshop it to be even more restrictive if you want, but at the end of the day, the only thing that doesn't make sense here is the fact that the rules prevent this outright. This IMO is one of the weaker arguments against this.
They wouldn't know about its destructive effects and wouldn't have any way of knowing besides being leaked to by CI or someone else. They'd just know that this is something that's under heavy security and would probably be bad for their captors if it got out, so it would end up being a last-ditch effort to leverage breaching it to try and get out alive.
And even if they did know... These are death-row convicts. You really think they're gonna be so socially-minded as to not release the deadly zombie virus? No.
Granted for balance reasons, it should never be all D-Class that get access to this. There needs to be a compromise to allow some way of the one hostile faction to F that is specifically ruleplayed against breaching 008, to be able to do so. You can workshop it to be even more restrictive if you want, but at the end of the day, the only thing that doesn't make sense here is the fact that the rules prevent this outright. This IMO is one of the weaker arguments against this.
#6: "If a TB gets the ability to get 008, all they will need to do is just bullet freeze and inject someone."
- This exact scenario without any further nuance would still be a failbreach following this suggestion's changes - Additionally, the play of just "running in, grabbing syringe, running out and jabbing the next person you see with 008" would most likely not be authed by SL+ without exceptional reasoning.
- This series of events implies they didn't enter with a hostage, implying they would need to then further leave the CC in order to accomplish this. Usually when CI raid into 008's CC, they end up getting trapped in there and have to open negotations. The same thing would generally happen with TBs. If the TB manages to get out, this constitutes a failure to protect the CC.
- Oh no, Bios and hazmats with Scrantons! How do I fight back aga
inst such awesome power?!
#7: The invisible ruling that D-Class are for all intents and purposes, not allowed to breach SCPs - "A D-Class must have a valid RP reason to breach an SCP"
Real past statement by a present member of SL...I'm just gonna present the original exchange here, because the revelations here are still kinda mind-blowing, even after a year:

What?
In case you're somehow still lost, this is just pure, hard-to-enforce ruleplay. The puzzling implication being that one of D-Class's core gameplay loops sesms to just be straight-up FailRP? I don't understand how this got glossed over in the original discussion, but this is beyond the scope of this suggestion.
The intersection here between the Staff Ruling and the suggestion, is sort of equivalent to something along the lines of a change to CI raids being denied "because CI engaging in combat with Foundation in general is considered RDM." So I don't know how to reconcile this, as this ruling is its own issue. I just mostly don't understand how this even happened.
The primary goal of D-Class is to escape the facility. The only reason they can breach an SCP on their own accord is to cause a distraction while escaping.
As death row inmates, it absolutely makes sense that a hostile D-Class could be inimical enough to deliberately try to make things as painful/miserable as possible, especially for people who would be their captors.
In fact, past me in the suggestion I linked put it quite well, IMO:
D-Class do not (and IMO, should not) need "an actual reason" to breach anything. They can breach whatever they please (except 008 currently as per server rules, which again, I agree with to an extent, as established) for whatever reason they want. They are a hostile group to be kept in check and if they are not kept in check, then they will cause havoc. That is a big part of what D-Class is on the server.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.
Their ability to breach SCPs as you put it will require extra rule clarifications to be added to the suggestion. The current ruling does not allow for any of this with regards to breaching SCPs.
...What? What rules are currently in place that prevent D-Class from breaching SCPs? A quick readover of the current rules doesn't turn up anything that suggests D-Class can't breach SCPs. Am I interpreting this right? I feel like I may be seeing this wrong, but is the claim that a D-Class can't escape D-Block, then go to say, 173's CC, and breach it?
This is the current ruling by SL, however not explicitly stated in the rules. A D-Class must have a valid RP reason to breach an SCP e.g. they are conscripted by CI, or a single breach by themselves to distract the foundation while they escape.
Well then they can provide the valid RP reason when questioned. I agree on the idea of clamping down of things like metagaming, minging, NITRP and rampantly breaching SCPs for the express purpose of ruining roleplay - But the concept of valid RP reason is kinda vague and flexible? A lot of things can reasonably constitute a valid RP reason in most circumstances.
Like, if I breach an SCP as D-Class, get taken to a sit, asked why I breached the SCP, and respond with anything along the lines of "As a violent prisoner who was poking around the facility looking for places to hide from patrols, tools to escape, etc. I happened upon this thing that they're keeping locked up, and since I as a death-row inmate convicted of mass murder love killing people, I set it free so I could cause widespread death and destruction." and get warned for a failbreach as a result, I'm 100% taking that to a complaint.
That seems difficult to enforce, too.
...Is this just a US thing, or?
You're more than welcome to make a complaint if you feel that you were wrongfully warned in a case like this. The reasoning for each instance is considered on a case-by-case basis.
This should be the case for both servers.

What?
In case you're somehow still lost, this is just pure, hard-to-enforce ruleplay. The puzzling implication being that one of D-Class's core gameplay loops sesms to just be straight-up FailRP? I don't understand how this got glossed over in the original discussion, but this is beyond the scope of this suggestion.
The intersection here between the Staff Ruling and the suggestion, is sort of equivalent to something along the lines of a change to CI raids being denied "because CI engaging in combat with Foundation in general is considered RDM." So I don't know how to reconcile this, as this ruling is its own issue. I just mostly don't understand how this even happened.
#8: "This strays too far into ruleplay instead of roleplay."
I mean, the suggestion is asking to loosen existing ruleplay. Yes, it's more complex in that you have to fulfil all these specific conditions for balances' sake before being able to breach the SCP - But as things stand right now, the rule is that you just can't do it at all. As I state, this brings D-Class into parity with other hostile factions' capabilities against the Foundation.
I for one, would love a ruleplay-less solution, but given that 008 is 008, you kinda can't. And also, this is to do with an SCP breach - You can roleplay around it as I quoted in the positives, but in it at its core, there's no roleplay. Almost every imposed restriction on D-Class is consistently rule-based. In which case, you should aim for what has the most sensible allowances over not. With that in mind, I would argue that having there being zero circumstances whatsoever is less favourable. "These specific hostile people don't get to do the thing because we said so" hardly constitutes good reasoning.
I for one, would love a ruleplay-less solution, but given that 008 is 008, you kinda can't. And also, this is to do with an SCP breach - You can roleplay around it as I quoted in the positives, but in it at its core, there's no roleplay. Almost every imposed restriction on D-Class is consistently rule-based. In which case, you should aim for what has the most sensible allowances over not. With that in mind, I would argue that having there being zero circumstances whatsoever is less favourable. "These specific hostile people don't get to do the thing because we said so" hardly constitutes good reasoning.
#9: "In the past, D-Class have failbreached 008 in low pop, with the resulting breach taking over an hour to get resolved, and the entire day for Staff to investigate what happened."
This exchange took place as part of the 'Allow all D-Class to breach 008' suggestion, but despite this being only for TBs, is relevant here, too
I think a better approach would just be about why they don't get any circumstance whatsoever. The known stance on this is that it'd just be 'too disruptive', but under the conditions I've laid out in the suggestion, I don't think it would be.
In the context of people doing this shit where they straight up failbreach and cause problems, yeah. I can agree with needing more mitigation before considering opening anything up, even slightly.
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.
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.
Admittedly, I'm not sure why I didn't interject here in the original thread, because I was with the reasoning up until the implication that an 008 breach is an RP scenario. The hostage situation leading up to it, sure, but the breach itself... No. 008 being out and thriving is anti-roleplay, through and through. You're not taking it any other direction.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.
I think a better approach would just be about why they don't get any circumstance whatsoever. The known stance on this is that it'd just be 'too disruptive', but under the conditions I've laid out in the suggestion, I don't think it would be.
In the context of people doing this shit where they straight up failbreach and cause problems, yeah. I can agree with needing more mitigation before considering opening anything up, even slightly.
#10: Regarding UK CI's OOC agreement to limit 008 raids

That's just good management. And of course, US CI aren't even getting close to breaching 008 because they're not good enough at the game, skill issue lmao.
I don't see how it's relevant to the infinitesimally small chance that a D-Class TB, after a player wins the RNG lottery to flag on, and within their drastically short lifetime, gets past F's D-Block TB protocol, gets into HCZ, gets a hostage, gets into 008, and gets SL+ approval for a breach.
What more do you need?
EDIT: I should clarify if it wasn't obvious, thata D-Block raid with the intent of progressing into an 008 raid, is still an 008 raid. You're not curveballing anything by approaching the 008 raid a different way
#11: "If you want less ruleplay, why not just let D-Class RDM each other for the most minor of reasons, they have no reason to be allied, since they don't know each other."
Honestly going over these discussions, the biggest thing I see from people is this weird "the sky is falling" type assertion that if this were to happen, 008 would be breached every other femtosecond and the servers explode in some kind of comical fireball.SCP-008 is dangerous, but that’s exactly what makes it valuable in RP. Fear and chaos are what drive high-stakes, memorable, and fun situations. The unpredictability of events is what keeps players engaged and gives life to the server.
Some people argue that Class-D wouldn’t “intentionally” breach a world-ending threat. But this assumes all Class-D act rationally, which is simply not true, either in lore or in roleplay. Many D-Class are unstable, desperate, mentally broken, or even unaware of what SCP-008 really is. Not every action needs to follow strict logic, it just needs to make sense in character.
Others say such a breach would be “extreme” or “uncontrollable”. But the server already has systems and rules in place to manage powerful SCPs. SCP-008 isn’t some unstoppable apocalypse, it’s dangerous, yes, but it can be contained with coordination. That’s the point. And that’s where the fun comes in.
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".
CI have a week cooldown on breaching 008 for a reason, if D Class can breach it that means there could be infinite amount of 008 breaches ie multiple per day or whatever and at that point you may as well remove the cooldown from CI breaching it - which would just be stupid for the gameplay loop
...Like, looking back over all this is... What? Most of the time, when I'm able to escape as a D-Class, I just get shot and die.I get where you're coming from, but that logic assumes D-Class breaches would happen frequently, which isn't realistic given the conditions being proposed.
CI have a cooldown because they have tools, coordination, and access that make breaching 008 much easier and more repeatable. D-Class, on the other hand, would logicly have a much harder time.
The idea that it would lead to "infinite breaches" just doesn't hold up. It would be a rare, high-effort situation that happens maybe once a few mounth , if that, and would still be subject to punishment if abused.
Can someone genuinely teach me how to be good at game so I can just leave D-Block at will and go breach SCPs please
It's all so boiled down to the point that it makes me look sane. I get that people will act on the petty desire just to failbreach 008 to piss people off. Hell, I wanna do it. But like... How?
Pls
Regardless, 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, the need for 12+ MTF to be on, the need for them to have a valid hostage to inject, PLUS the added need of getting SL+ auth - 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 once again 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. I still don't know what the -Support is here other than the idea that everyone seems to have that "this would make 008 breaches constant and frequent, rocks fall, we all die."
There's also the angle of TB's decay, the fact that they're 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, but CI TBs do 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.'
...Do you all just wanna come over to the world where 008 doesn't breach as often as you seem to think it does? I can arrange transport, but you'll need to pay your own fares
Last edited:
Donator
Platform Team
Game Master
Programming Team
Junior Developer