Content Suggestion SCP-173 FIX

Content Suggestions will be reviewed by Content Team weekly, please allow time as not everything can be reviewed at once.
Lupo Machettie

Lupo Machettie

New Member
Jun 28, 2026
3
2
1
What does this suggestion change/add/remove: This change will allow SCP-173 to have a chance to fight against ERT by allowing SCP-173 to do 1/4 of their health with an attack so it will take on average 20 seconds to kill an ERT by them selves but still a vary slim chance when they are grouped up

Has something similar been suggested before? If so, why is your suggestion different?: 173 was bugged allowing him to instantly kill ERT but they "fixed" the bug making 173 instantly lose when ERT spawn

Possible Positives of the suggestion (At least 2): Give 173 A fighting chance against ERT AND not waste the hours spent in breach queue of someone that enjoys the SCP-173

Possible Negatives of the suggestion: ERT aren't instantly winning against 173 and some might be killed if they try to solo 173

Based on the Positives & Negatives, why should this suggestion be accepted: It should be accepted to allow 173 to do something when ERT wave comes in instead of watching themselves get destroyed and re-contained with 0 counter play
 
Upvote -1 Downvote
-Support

ERT is supposed to help end a breach faster, I believe that if there's ERT called and only 173 out enough has been done with a breach and it's time to wrap it up to get back to nominal status RP.
 
+Support
I don't agree with the exact proposed implementation, but I still think ERT being outright immune to 173 is stupid, I'd be fine with smth like TP attacks dealing only so much damage so it needs multiple hits to kill, but outright being able to stop 173 is dumb
Skittles said:
ERT is supposed to help end a breach faster, I believe that if there's ERT called and only 173 out enough has been done with a breach and it's time to wrap it up to get back to nominal status RP.
Click to expand...
I mean yeah, instakill is too OP against ERT - But with my idea here or even anything that gives 173 even the slightest amount of counterplay, if a whole-ass wave of ERT still fails against only 173, then that's a massive skill issue and the breach deserves to go on longer IMO
 
  • Like
Reactions: Skittles
- Support

ERT are a soft-nuke they are meant to force the end of a prolonged breach
if you been breached long enough to warrant their deployment , you probably had your fun and the site needs to return to regular RP

Also im pretty sure this got denied twice already
 
Jello_on_mello said:
- Support

ERT are a soft-nuke they are meant to force the end of a prolonged breach
if you been breached long enough to warrant their deployment , you probably had your fun and the site needs to return to regular RP

Also im pretty sure this got denied twice already
Click to expand...
I mean currently the only way 173 can get the Site to deploy ERT is on low pop (if theres even someone to auth ERT)... But at least give him some damage to them

Before current breach queue, when CI breached other SCPs and queue could overlap, sometimes 173 would breach through queue and then ERT showed up due to prolongued CI breach of the usuals 682, 076, 8837.... On those scenearios ERT just surrounds you and you get recontained in less than 1 minute (not fun when you waited 2+ hours). Old 457 also suffered from this since his sprint was a limited ability.
 
werta600 said:
I mean currently the only way 173 can get the Site to deploy ERT is on low pop (if theres even someone to auth ERT)... But at least give him some damage to them

Before current breach queue, when CI breached other SCPs and queue could overlap, sometimes 173 would breach through queue and then ERT showed up due to prolongued CI breach of the usuals 682, 076, 8837.... On those scenearios ERT just surrounds you and you get recontained in less than 1 minute (not fun when you waited 2+ hours). Old 457 also suffered from this since his sprint was a limited ability.
Click to expand...
So.... a lowpop 173 is just straight up the most cancerous breach to play against , and is more than worthy of being beaten back in to its CC after the 20min required for ERT deployment pass

CI caused breaches and SCP queue don't really have much overlap
a Scp being breached just stops the queue from moving
and CI cant breach SCPs if 3 are already out anyways

173 is in desperate need of a full rework , yes
but don't nerf the thing meant to prevent breaches from becoming disastrous on server health
so one peanut looking SCP can feel a bit better to play
 
Jello_on_mello said:
So.... a lowpop 173 is just straight up the most cancerous breach to play against , and is more than worthy of being beaten back in to its CC after the 20min required for ERT deployment pass

CI caused breaches and SCP queue don't really have much overlap
a Scp being breached just stops the queue from moving
and CI cant breach SCPs if 3 are already out anyways

173 is in desperate need of a full rework , yes
but don't nerf the thing meant to prevent breaches from becoming disastrous on server health
so one peanut looking SCP can feel a bit better to play
Click to expand...

In most cases ERT is still going to make quick work of 173, even on low pop servers when they are called. This was just to give 173 even a small chance of killing at least one and not feel like your just watching the end of your 2+ hour sometimes even 6 hour wait time go up in smoke. The way it is now there only needs to be ONE ERT to fully contain 173, even if he still has 20 Thousand health and being in that situation would make you never even want to touch 173 ever again. I offered this change to try and combat that exact situation
 
  • Like
Reactions: Emilia Fοddg
Jello_on_mello said:
So.... a lowpop 173 is just straight up the most cancerous breach to play against , and is more than worthy of being beaten back in to its CC after the 20min required for ERT deployment pass

CI caused breaches and SCP queue don't really have much overlap
a Scp being breached just stops the queue from moving
and CI cant breach SCPs if 3 are already out anyways

173 is in desperate need of a full rework , yes
but don't nerf the thing meant to prevent breaches from becoming disastrous on server health
so one peanut looking SCP can feel a bit better to play
Click to expand...
its not a nerf, every SCP should be able to combat human job players, regardless if they are ERT, Juggs or whatever

This would allow 173 to at least damage ERT, and considering 173 can attack once every 5 seconds, its not even a nerf to ERT
 
  • Like
Reactions: Lupo Machettie
You must log in or register to reply here.
Top Bottom
Back