Content Suggestion E-11 Containment Specialist Rework

Content Suggestions will be reviewed by Content Team weekly, please allow time as not everything can be reviewed at once.
Jul 6, 2025
5
0
11

What does this suggestion change/add/remove:

The current E-11 Containment Specialist is lacking a real unique identity within E-11's roster with it being more of a direct upgrade from E-11 Operative but worse than E-11 Biohazard Specialist. This rework proposes turning the role into an HCZ Containment Engineer, focused on recontainment support and infrastructure repair. Right now, HCZ often remains broken during breaches due to a lack of competent techies (majority of which are E-11 swapping jobs to fix HCZ), and policies to Class-A them after work (often gets ignored) only worsen the issue with Class-A's being scarce. Letting E-11 handle these tasks makes sense, they’re trained, available, and already operating in the zone with knowledge of all SCPs hence removing the need for Class-A'ing reducing the chances of info breaches. This change not only gives the Specialist a clear, practical role but also adds a unique utility aspect to the whole E-11 regiment, setting it apart from other combat focused units like Nu-7 or DEA. From a logistical and an in-practice standpoint, it's an oversight to let CL1/2 personnel be in the same vicinity as SCPs like 008, 035, or 682 making this a logical change.

Current E-11 Containment Specialist:
- Anomaly Containment Beam
- Decontamination Foam Applicator
- SCP Containment Restraints
- Erad (Primary)
- M9 (Secondary)
- Personnel Tablet
- Scranton Reality Anchor
- Quarantine Placer
- Gestures
- Weapon Checker
- TE-5 E.T.D (Hacking Device)
- Radio

Proposed E-11 Containment Specialist:
- Anomaly Containment Beam
- Decontamination Foam Applicator
- SCP Containment Restraints
- Erad (Primary)
- M9 (Secondary)
- Personnel Tablet
- Scranton Reality Anchor
- Quarantine Placer
- Gestures
- Weapon Checker
- TE-5 E.T.D (Hacking Device)
- Radio
- Repair Tool

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

Yes, similar ideas have been suggested before, but they often propose major overhauls with multiple new classes to E-11. This suggestion takes a more grounded approach by focusing on refining an existing role. E-11 doesn’t need a full combat class lineup, unlike other regiments, our focus isn’t purely on PvP or heavy defense, but on containment and utility. This change strengthens that identity without overcomplicating the roster.

Possible Positives of the suggestion (At least 2):

Improved HCZ Maintenance: Assigning containment and repair duties to the E-11 Containment Specialist ensures HCZ infrastructure can be consistently maintained during breaches, reducing info breaches and enhancing overall containment efficiency.

Unique Role Identity: This change gives the Containment Specialist a defined purpose, setting them apart from standard Operatives and Biohazard Specialists, reinforcing E-11’s specialized identity as more than just a HCZ Combat Regiment.

Possible Negatives of the suggestion:

Role Overlap with Techies: Introducing engineering responsibilities to E-11 may cause overlap with existing techie roles, potentially leading to redundancy if boundaries are not clearly defined.

Possible Undermining of Containment Focus: Shifting part of the Specialist’s focus to engineering tasks may dilute their core purpose which is SCP recontainment, potentially weakening their effectiveness in that critical role during chaotic breach scenarios. However, with some simple guidelines and priorities set in place, I don't see this as a major issue.

Based on the Positives & Negatives, why should this suggestion be accepted:

Despite some potential drawbacks, this suggestion addresses a real gap in HCZ maintenance and gives the Containment Specialist a clear, functional identity beyond being a reskinned E-11 Operative. It enhances E-11’s utility and reinforces their lore driven role in recontainment, without requiring a full class overhaul. With proper role clarity, the benefits: improved infrastructure stability and a more unique E-11 regiment outweigh the manageable downsides.

1752305715676.png
 
Jul 6, 2025
5
0
11
get a tech expert, this is literally denying them RP
Had a situation where a Techie threatened to Info Breach 682 over trapping himself in 682's CC, from a functional standpoint, why would the Foundation let CL2 personnel have access to sensitive information not to mention the strain on Class A supplies. Its just not a sound solution imo. On top of that, the majority of techies that do properly do their job are just E-11 swapped onto Techie, save the time and energy by just doing it in house 🤷
 
Last edited:
Had a situation where a Techie threatened to Info Breach 682 over trapping himself in 682's CC, from a functional standpoint, why would the Foundation let CL2 personnel have access to sensitive information not to mention the strain on Class A supplies. Its just not a sound solution imo.
It's almost like the current form of E&TS doesn't make sense and people have suggested ways to fix this multiple times. This is not a solution, this is just making things worse in a different way.
 
  • Like
Reactions: Sneefo
Jul 6, 2025
5
0
11
It's almost like the current form of E&TS doesn't make sense and people have suggested ways to fix this multiple times. This is not a solution, this is just making things worse in a different way.
While it's a respectable opinion, again this doesn't address the fact that the current E-11 Containment Specialist Job has no real identity that sets it apart from the rest of E-11, an E-11 Operative can acquire the same loadout through dispensers and majority of E-11 just play the class if Biohazard Specialist is full as that utility it gives is infinitely more useful in most situations.
 
Nov 6, 2022
50
17
111
-Support

They are already set apart from the E-11 Bio/Op by spawning with scrantons and a beam. Your "unique role identity" just gives the CS a repair tool. Lol. Ask for a tech to come down and repair. And if every techie on site is currently feral (very common) just flag on techie yourself.
 
Jul 6, 2025
5
0
11
-Support

They are already set apart from the E-11 Bio/Op by spawning with scrantons and a beam. Your "unique role identity" just gives the CS a repair tool. Lol. Ask for a tech to come down and repair. And if every techie on site is currently feral (very common) just flag on techie yourself.
Already is the case with most E-11 having to swap jobs after the breach. The whole idea of this adjusted Containment Specialist is fixing DURING the containment breach, say a 682 is in a 3-way breach and rushes primary bulk. A techie/engie won't get to those until after the ENTIRE CB is over leaving E-11 to scramble in LCZ because one SCP opened the flood gates without much in the way to stop em. Now say instead of rewarding rushing LCZ, we punish them by letting the door hit them on the ass on the way out. Not only have they completely isolated themselves in LCZ but the rest of the breach (In HCZ presumably) is cut off from their biggest tank with E-11 able to isolate the other SCP threats via fixing primary bulk. I'm proposing turning a lost cause which HCZ typically turns into because one bulk gets broken into a salvageable situation.
 
Had a situation where a Techie threatened to Info Breach 682 over trapping himself in 682's CC,
okay, RP it out, its a RP server.

from a functional standpoint, why would the Foundation let CL2 personnel have access to sensitive information not to mention the strain on Class A supplies.
well, they don't. Sure, they know 682 has a chamber, and based on past breaches likely know its a huge lizard, but they dont know all the sensitive information. Don't see why they would.
And Class A is easy af to get, i dont play US but if theres a "strain", people need to go on surface and scavenge.

On top of that, the majority of techies that do properly do their job are just E-11 swapped onto Techie, save the time and energy by just doing it in house 🤷
insane self snitch. Interacting with other people? CL2's as well? How could I stoop so low!
 
Had a situation where a Techie threatened to Info Breach 682 over trapping himself in 682's CC, from a functional standpoint, why would the Foundation let CL2 personnel have access to sensitive information not to mention the strain on Class A supplies.
That's not how clearance knowledge works. What you are and aren't allowed to know is a form of RP in itself - Not a strict OOC guideline to be stringently enforced and content changes made around preventing lower clearances access to higher clearance information. There are absolutely valid circumstances in which personnel of low clearance would be, even temporarily, be permitted access to high clearance information.

This idea would just make people overly reliant on the "E-11 Techs" for high clearance areas, objects and information.