Make natural breaches disable the ability to hack out SCPs temporarily!

Dec 25, 2023
515
137
61
What does this suggestion change/add/remove:
When a natural breach occurs, non-SCPs abilities lose the ability to hack out to breach any SCPs using a TE-5 for 45 minutes.

Notes:
  • SCP-035 would not be affected by this idea, it should be allowed to breach out SCPs using TE-5
  • This would activate at the start of the natural breach. meaning if a natural breach somehow lasts 45 mins then CI could hack out right after it ends (if Foundation can't clean a natural breach in 45 minutes, I blame them fully).
  • This would directly be indicated by some kind of words or images on the SCP boxes that show they're unable to be breached

Has something similar been suggested before? If so, why is your suggestion different?:
No idea.

Possible Positives of the suggestion (At least 2):
  • Less situations of natural breaches directly into CI breaches
  • More time to RP
  • Less uninteresting / unfun fights (most SCPs aren't the most fun to fight against)

Possible Negatives of the suggestion:
  • Less SCP breaches overall (a good thing for anyone who isn't on the site of the SCPs)
Based on the Positives & Negatives, why should this suggestion be accepted:
See all of the above.

It is to stop those (many) situations where there is a natural breach into a CI breach very quickly (or right at the same time) which causes a hyper-inflated and unfun breach to fight that very quickly is no longer a situation normal combative can handle and either takes a long time or requires ERT/Nuke to handle, or similar situations in which breaches into CI breaches result in very little RP being able to be done due to the short gap.
 
Last edited:
the problem cannot be content anymore. So much has been done with no improvements Im convinced its the players, not the game
You right - but said players are in a faction built to cause combative actions that stop RP and choose within that idea to do breach raids.

To be straight here, this isn't about "lack of content" but rather content that I feel harms other content and server enjoyment.

I thought breaches weren't too bad atm
Natural breaches? I mostly enjoy them, I'm not even that heavily against CI breaches as I can enjoy them often too - it's just when they're together or one right after another that messes it all up (or I guess just generally during good RP, but that's not solvable this way).

It is good to have a short breach from RP or whatever E-11 duties I'm doing to fight a breach, however when that turns into a massively long breach or 2 breaches one after each other that makes it no longer feel fun.
 
Last edited:
  • Love
Reactions: Emilia Foddg
If you don't want CI to breach scp the best thing to do is lockdown primary and make secondary the new primary
-support

What?

I mean I agree with you, I think primary should be permanently double closed and secondary should be guarded instead - but to be 1000% honest this won't fix it and make the the SCP chambers an insane fortress.

CI will still make it through because those 6~ CI that get to 914 or train vents can rush down and wipe out the (certainly less than 6, probably with worse weapons too overall) guards that are stood at secondary just to make it into HCZ anyways. Alternatively, they could just breach LCZ SCPs.
 
What?

I mean I agree with you, I think primary should be permanently double closed and secondary should be guarded instead - but to be 1000% honest this won't fix it and make the the SCP chambers an insane fortress.

CI will still make it through because those 6~ CI that get to 914 or train vents can rush down and wipe out the (certainly less than 6, probably with worse weapons too overall) guards that are stood at secondary just to make it into HCZ anyways. Alternatively, they could just breach LCZ SCPs.
bump the hacking level up for each scp that is actively breached!!!!
 
What?

I mean I agree with you, I think primary should be permanently double closed and secondary should be guarded instead - but to be 1000% honest this won't fix it and make the the SCP chambers an insane fortress.

CI will still make it through because those 6~ CI that get to 914 or train vents can rush down and wipe out the (certainly less than 6, probably with worse weapons too overall) guards that are stood at secondary just to make it into HCZ anyways. Alternatively, they could just breach LCZ SCPs.
Yes, but it also give e11 the opportunity to call it out, better fighting position and takes CI stealth which is one of its biggest strength they unless E11 can't scream in the radio that ci are rading
 
the problem cannot be content anymore. So much has been done with no improvements Im convinced its the players, not the game
It isn't content I'm pretty sure most of these breach raids now where nuke has gone off has mainly been because
1. We have a good 079
2. Everyone deals with the breached SCPs instead of us in 079
3. We see nu-7 like once or twice and usually without jugg we've seen jugg come like once to an 079 hold so
4. Breaching 2 SCPs before 079 is hacked out (7722, 682 usually) and when we've done it as he can still breach SCPs even if 3 are breached and he breaches usually 106, unkillable unless they get a d class past all the killing machines, TG or 8837 which use a breach tool on the other TG or 8837 whichever gets breached first and all of those together usually kill everything and 079 can still breach things when the 20m or whatever the cooldown is off so as long as the SCPs/CI stop people from getting into 079 it's impossible to win.
 
The number of More and more SCP breach halting suggestions that are up and being discussed is more concerning than the main issue that is presented.

it is rare to see a back to back breach atlest on the USA, most breaches have an average of 2h delay after one is RCed.

it still happens because of GOI hacking them out.
i dont see how we as Content or SSL can restrict this more. without severely harming the other side.
 
  • Like
Reactions: Emilia Foddg
The number of More and more SCP breach halting suggestions that are up and being discussed is more concerning than the main issue that is presented.

it is rare to see a back to back breach atlest on the USA, most breaches have an average of 2h delay after one is RCed.

it still happens because of GOI hacking them out.
i dont see how we as Content or SSL can restrict this more. without severely harming the other side.

I really do think Auburn said it best, the current systems are fine. It's absolutely the players.
 
Yes, but it also give e11 the opportunity to call it out, better fighting position and takes CI stealth which is one of its biggest strength they unless E11 can't scream in the radio that ci are rading

E-11 calling CI going through secondary doesn't change much tbh - CI will often make it down into HCZ (or further) before E-11 can respawn and respond from their bunks and almost certainly faster than the people in light can respond (because elevators slow).

With how it currently works, if CI can get to and breach 1 SCP then that single SCP often will clear the way for the CI to move back out it's chamber and go to another - and in situations where it doesn't clear all of the Foundation it still results in a situation of a powerful amount of CI vs a small or weaker amount of Foundation.

bump the hacking level up for each scp that is actively breached!!!!
Not too bad of an idea tbh, although I am shit at hacking comparing to some CI so perhaps this wouldn't phase them as much (0 idea here).

-Support
The cooldown being 45 minutes (should be 15-30 minutes)
This is fair imo, 45 minutes was just a general idea and if this was to be accepted and the timer reduced then I wouldn't feel bad for it.

i dont see how we as Content or SSL can restrict this more. without severely harming the other side.
I had a longer message, I will shorten it: If the idea of "breaches one after another or in short time" is severely harming the other side then perhaps that harm should be considered as a reasonable action.
 
  • Like
Reactions: Tiffany Lilly
I had a longer message, I will shorten it: If the idea of "breaches one after another or in short time" is severely harming the other side then perhaps that harm should be considered as a reasonable action.
in my previous post, i meant halting the ability to hack scps out more, which will limit GOI/D-class not Foundation, harming their gameplay loop.

if we compare breaches from a year ago and before that, how hard have we nerfed the SCP breach system how much nerfs and buff have come along. What most people want is to just limit it more and more, there should be back to back breaches but it should be a rare thing,

there should be a nuke or ERT call ins but it should be rare,

Breaches to my opinion are way better then before, less halting RP on average and quicker dealt with/ RCed

i cant vouch for UK side but I dont believe the arguement of breaches one after another or in short time is severely harming foundation, isnt really a argument that holds merits in the rarety of this happening. Does it happen yes, is it at that time a concern yes, But should we limit GOI and other personnel to hack them out no.

there can be 3 breaches SCPs out at a time by hacking, if more then 3 are out players cant hack out others.

combine it with a breach tool the amount can now reach 6 scps ( excluding double scps like 9k and 939).

079 has a severe nerf on the amount he can breach and the time per try/action.

and then Content is still discussing limiting scp hacking under x player count.. and more things.

I cant see how i can justify something like this.
 
  • Like
Reactions: Sneefo