Rule Suggestion ERT knowledge of breaches upon Deployment

Rule suggestions will be reviewed by Superadmins, this may take longer than standard content suggestions.
Mar 6, 2025
238
41
41
What does this suggestion change/add/remove:
- Allow ERT to know what SCPs are breached on site upon deployment
Main point : ERT MANUAL CALL + Auto deployment & Exfil orders

- Someone PHONES ERT, telling them "X number of SCPs are breached." In response, ERT sends 1 team per breach (maximum 3). Realistically, ERT WOULD KNOW what SCPS are breached. As I would argue, the person making said call is giving them a full list. + Arguably, ERT auto deployment would be based on a system recognizes that multiple containment chambers failed , and have remained failed for X amount of time. Also, knowing what SCPs are breached. (This would also validate exfil for being used IC that no other breaches have occurred, and the containment status for ALL scps is set back to normal)

Has something similar been suggested before? If so, why is your suggestion different?:
Probably not

Possible Positives of the suggestion (At least 2):
- ERT knowing what SCPS are on deployment makes the Emergency Response team... an actual response team prepared for any threat
- During low pop hours / breaches, when all foundation members GET ERT , ERT won't have to wonder "What's breached" & risk a metagaming warning for simply assuming what scps are breached.
- Slight build on ERT lore and functions (I know their kept out of hierarchy and lore though I would find it interesting for a SLIGHT showcase of the technology they utilize being able to detect breaches via having a system that detects which SCPs are breached)


Possible Negatives of the suggestion:
- None really, will explain below.

Based on the Positives & Negatives, why should this suggestion be accepted:
Personally, I think its a little silly that ERT has to ask "what's breached" despite either being phoned in or having a system recognize a number of breaches that automatically alert them. Very small change though would be decent, giving slightly more lore to ERT and how they function + just giving a slight quality of life change letting ERT just get straight to it and not have to rely on asking whats breached.

They would still have to ask WHERE the breaches are located. So its not some massive powergame or anything.
 
-Support

It is a really simple way of roleplay for people to just interact with SCP's, and them to get knowledge on what SCP's are breached. Getting rid of this just removes a layer of roleplay for no real reason.
Also, how would silent breaches work, or breaches the Foundation itself isn't aware of? (E.G. 079 is out and no one knows, 682 breached 049 but he's been playing sneaky, etc).
 
-Support

It is a really simple way of roleplay for people to just interact with SCP's, and them to get knowledge on what SCP's are breached. Getting rid of this just removes a layer of roleplay for no real reason.
Also, how would silent breaches work, or breaches the Foundation itself isn't aware of? (E.G. 079 is out and no one knows, 682 breached 049 but he's been playing sneaky, etc).
-support agreed
 
-Support

It is a really simple way of roleplay for people to just interact with SCP's, and them to get knowledge on what SCP's are breached. Getting rid of this just removes a layer of roleplay for no real reason.
Also, how would silent breaches work, or breaches the Foundation itself isn't aware of? (E.G. 079 is out and no one knows, 682 breached 049 but he's been playing sneaky, etc).
-support agreed
 
-Support

It is a really simple way of roleplay for people to just interact with SCP's, and them to get knowledge on what SCP's are breached. Getting rid of this just removes a layer of roleplay for no real reason.
Also, how would silent breaches work, or breaches the Foundation itself isn't aware of? (E.G. 079 is out and no one knows, 682 breached 049 but he's been playing sneaky, etc).
What are you on about, There is no such thing as roleplay when scps are breached.
 
  • Like
Reactions: Niox