Content Suggestion ERT slight change

[Sule Goodman]

What does this suggestion change/add/remove:[/B
Slight changes with ERT structure

1. Slot 1 (both playing as , and on the invite system) Appears as
- ERT Captain [NAME] instead of just ERT Operative [NAME]

2. ERT added to Foundation hierarchy (Sr level 4, as they report directly under SA & SC OR Jr Lv 4s naturally, but Sr level 4 under direct orders)

3. Expanded ERT Call Permissions:
- ECA and OSA should have the ability to call ERT manually.

4. Manual Call Deployment Time reduced to 3 minutes:
- Match the ERT manual deployment time with the automated calls 3 minute ETA.

5. ERT receive hacking alerts.
- Familiar with the SCU and E-11 jobs. ERT should also receive the "Hacking in [Location] alerting them of SCPs being hacked out.

6. ERT team per 3 008-2 instances.
- I believe it takes 8 008-2 instances for a SINGLE team of ERT. this would change it from 8 per team, to 6 for all 3 teams.
Has something similar been suggested before? If so, why is your suggestion different?:
- For some of the things probably, but haven't seen any myself.

Possible Positives of the suggestion (At least 2):
1. Players unfamiliar with the team structure / loadout can easily be able to identify the ERT captain role.

2 . I would argue, ERT deserves a spot on the hierarchy as they are Lv 4 ( soon to be added biometric Cl 4 as listed on the dev tracker). The inital announcement when ERT got released ( the only somewhat official "lore" i can find on ERT, states that they are the foundations most elite MTF, and Official hierarchy placement reinforces their important and strengths RP immersion.

3. Probably going to the most argued and Ill list the negatives below but, I've seen assistants on more than SA / SC. And having to rely on staff at times to call ERT (or wait the 20+ minutes for an auto call which usually is just when SCPs are on surface by then). I know adding 2 more phones into the assistant offices, or just giving them access to call them could be extra but having more people who can call for help in a desperate time would be extremely nice.

4. The announcement to an ERT call is "ETA 3 minutes" both for the auto deployment and the manual deployment. I know its an "ETA" but i don't see 5 minutes being required, 3 is more than enough to get the entire team on site. A quicker ERT deployment generally just benefits the entire foundation

Possible Negatives of the suggestion:
- Could be considered "unneeded"
- Potentially "overpowered" specifically with 3 & 4. With ERT being deployed faster naturally and 4 more people on site being able to call them (ECA & OSA)

Based on the Positives & Negatives, why should this suggestion be accepted:
The ERT naming to include Captain isn't really anything major. Though, for 2 specifically, not really anything to big. As its a group of a maximum of 9 people, who only are on site for breaches, and leave afterwards. There isn't really any "lore" or "canon" on ERT despite that their the foundations most elite MTF group so seeing them apart of the hierarchy would actually be interesting to see for them to be built on slightly.

In terms of 3 & 4. I know this will be the most argued. But ERT being the "last resort" before a surface breach / Nuke having assistants of SA / SC (who sometimes just doesn't even call them in time, which I understand as SA / SC get busy with important things) having them be able to call them whether on their own accord or under SA / SC orders, would be VITAL. And furthermore, having ERT deploy 2 minutes early , a faster and quicker deployment could directly prevent late responses. Resulting in avoidable surface breaches, resulting in just an overall longer breach.

For 5 & 6. For 5 - I don't see the issue with ERT knowing of a hacking alert. Seeing its gonna lead into a breach if not responded quickly enough, and ERT are on site to DEAL with the breach. I see no reason why they cannot have an alert system to hacking attempts. And for 6, I find 8 instances per team to be an extreme under number. As 8 instances alone can easily turn into 20+, and if an ERT team is called to soon, in hopes to get a quick response to the outbreak, It can result in to little units to respond. I think 3 per team is much more fair.


In summary, This suggestion proposes several improvements to ERT - ranging from a simple slot name change to reducing deployment. I believe these changes can improve ERT response and give ERT a slightly more clear spot in lore.

Thanks for reading it all if you have.

 

[Change Z. "The Coward"]

1. Slot 1 (both playing as , and on the invite system) Appears as
- ERT Captain [NAME] instead of just ERT Operative [NAME]

Makes sense +support

2. ERT added to Foundation hierarchy (Sr level 4, as they report directly under SA & SC OR Jr Lv 4s naturally, but Sr level 4 under direct orders)

They are technically level 3.5s like AO enlisted they have none bio Cl4's+/-Support

3. Expanded ERT Call Permissions:
- ECA and OSA should have the ability to call ERT manually.

Hello no, bad idea... some of the assistants I have seen. -Support

5. ERT receive hacking alerts.
- Familiar with the SCU and E-11 jobs. ERT should also receive the "Hacking in [Location] alerting them of SCPs being hacked out.

Actually makes sense +support

6. ERT team per 3 008-2 instances.
- I believe it takes 8 008-2 instances for a SINGLE team of ERT. this would change it from 8 per team, to 6 for all 3 teams.

I feel like if 008 is out it and for ERT to be called it would already pass this number.

 

[Sule Goodman]

They are technically level 3.5s like AO enlisted they have none bio Cl4's+/-Support

I had a prior suggestion to get them bio cl4 , which was accepted so. They technically are bio cl 4s, just awaiting the update

 

[Auburn]

1) Good idea, i think it would be possible but not sure. Would have to check
2) ERT are deliberately outside of the heirarchy. They arent placed because we dont want to run into a situation where someone tries to arrest one, or detain one, or give conflicting orders to them, etc. At max they follow the instruction of site admin+ but thats the only COC they follow.
3) No thats not their job. Assistants wouldnt have that authority in RP
4) is it different? I thought the ETA was the same regardless of how its called in. Afaik i think its randomly 120 or 180 seconds
5) Good idea. Approved!
6) I think 008 already has a special condition for calling in ERT

 

[Sule Goodman]

1) Good idea, i think it would be possible but not sure. Would have to check
2) ERT are deliberately outside of the heirarchy. They arent placed because we dont want to run into a situation where someone tries to arrest one, or detain one, or give conflicting orders to them, etc. At max they follow the instruction of site admin+ but thats the only COC they follow.
3) No thats not their job. Assistants wouldnt have that authority in RP
4) is it different? I thought the ETA was the same regardless of how its called in. Afaik i think its randomly 120 or 180 seconds
5) Good idea. Approved!
6) I think 008 already has a special condition for calling in ERT

4- it is different, automatic ERT call is 3 minutes. Manual is 5. Would be nice to have it set to 3 minute for either case

5- yayy

6 - From what i see publiclly, 008 is 1 team PER 8 instances.... which is just hell

The rest i understand, thanks for responding, genuinely means a lot

 

[Evil]

4- it is different, automatic ERT call is 3 minutes. Manual is 5. Would be nice to have it set to 3 minute for either case

5- yayy

6 - From what i see publiclly, 008 is 1 team PER 8 instances.... which is just hell

The rest i understand, thanks for responding, genuinely means a lot

By the time ERT spawns in, either all the 008 will be dead, or there will be an army of -2. Three teams should be called in, so I don't know what the point is in lowering it to 6. There will be no difference -support. just suggest that " If 8 instances of 008 have breached, then 3 teams of ERT will automatically be called in."

- ECA and OSA should have the ability to call ERT manually.

they will call ert over 1 scp in the name of RP -support
Reason above for the hierarchy for ERT -support

Everything else makes sense so +support

 

[Sule Goodman]

By the time ERT spawns in, either all the 008 will be dead, or there will be an army of -2. Three teams should be called in, so I don't know what the point is in lowering it to 6. There will be no difference -support. just suggest that " If 8 instances of 008 have breached, then 3 teams of ERT will automatically be called in."

Honestly a much better idea tbh

 

[Merrick Travolta]

1) Good idea, i think it would be possible but not sure. Would have to check
2) ERT are deliberately outside of the heirarchy. They arent placed because we dont want to run into a situation where someone tries to arrest one, or detain one, or give conflicting orders to them, etc. At max they follow the instruction of site admin+ but thats the only COC they follow.
3) No thats not their job. Assistants wouldnt have that authority in RP
4) is it different? I thought the ETA was the same regardless of how its called in. Afaik i think its randomly 120 or 180 seconds
5) Good idea. Approved!
6) I think 008 already has a special condition for calling in ERT

ERT's deployment time in message vs actual timer is different when manually called and occasionally when auto called.

as for option 6. if it does, it's not great. I believe we had a large 008 outbreak I had to call ERT for and only got 2 teams despite being atleast 10 instances and several spores.

 

[Sule Goodman]

ERT's deployment time in message vs actual timer is different when manually called and occasionally when auto called.

as for option 6. if it does, it's not great. I believe we had a large 008 outbreak I had to call ERT for and only got 2 teams despite being atleast 10 instances and several spores.

in Chat, it will say 3 minutes ETA , the only time i've seen a 2 minute deployment is if its an automatic call with less than 3 SCPs. (Less teams, less time, lowest at 120 i've seen).

Imo i believe it should just be to set 3 minutes for any set of team. More than fair compared to the 5 minutes.

And for 6 , i can tell you, its 8 instances per team, you can check the change log for that