- Feb 26, 2023
- 285
- 70
- 61
What does this suggestion change/add/remove:
Putting forward a short list of problems regarding SCP-096:
1. Breaches can be stopped outright - Currently, SCP-096's breach is simply spawning a picture of its face in a random(?) location on the map. Any component Foundation player destroying this picture completely wastes the average 2+ hours of breach queue that the SCP-096 player spent sitting there. No other existing breach-able SCP works this way; breaches are guaranteed for them, as their chamber doors "malfunction" and automatically open. Why isn't this same logic applied to SCP-096 breaches? This also calls into question why the face picture spawns facing downwards: would having it spawn facing upward be any more realistic than having a picture of its face spawn randomly?
2. The Bucket - The almighty bucket, a necessary kryptonite to SCP-096. I understand the function the bucket serves is preventing perpetual re-viewing of SCP-096's face on his way to his next targets, but not how easy it is to apply the bucket. Realistically, NOBODY would probably be able to place a bucket on SCP-096's head while its in motion.
Edit: As the addition of TYPE-GREEN SCPs have generally made breaches longer, and SCP-096 will likely no longer breach by himself, the bucket remains untouched.
3. Forced Self-Recontainment - Perhaps the most disappointing realization you can have as an SCP-096 player can have is to have your last target sit in your containment chamber, forcing you to kill all of your other remaining targets and recontain yourself. The other is to drop everything and go to kill that lone individual before you continue on your spree; not very roleplay-accurate, and likely to get the SCP-096 player reported and warned for FailRP. It's essentially a guaranteed strategy for recontainment, with no possible ways to for the 096 player to counter it.
For each of these perceived problems, here's a respective solution to each that wouldn't heavily favour SCP-096:
1. 096's chamber doors fail when auto-breached just like any other breach-able SCP, and may walk out following the existing minute rule. (doesn't leave his breach entire up to chance)
2. Buckets may only be placed on 096 while un-enraged.
Edit: As the addition of TYPE-GREEN SCPs have generally made breaches longer, and SCP-096 will likely no longer breach by himself, the bucket remains untouched.
3. If 096 is "baited" into its cell, given that the chamber remains open, it may walk out of its chamber following the existing minute rule.
Possible Positives of the suggestion (At least 2):
1. Improves realism and consistency surrounding SCP-096's own gameplay mechanics, as well as extending 096's lore-accurate containment procedures and weight of his breaches, making the experience more enjoyable for players who choose to play as 096.
2. The changes mostly work to balance out 096 gameplay by not heavily favoring the SCP player while addressing the lack of sustained contribution SCP-096 has on breaches.
3. Better synergy with other SCPs due to 096 breaching at roughly the same time with other SCP players, allowing for harder-hitting combos that succeed based on collaboration.
4. Differentiates 106 and 096 containment methods more clearly and accurately according to SCP lore (no casualties technically need to be incurred).
5. Foundation personnel get more chances to witness d-block massacres.
Possible Negatives of the suggestion:
1. 096 breaches will be more difficult to recontain due to the fact that there will be little that can be done to stop 096 from viewing other's faces once he's out (although this would incentivize combatives to make the effort to "seal off" areas within 096's predicted path).
2. Initial confusion and player reports caused by SCP-096's recontainment being communicated but not actually being properly contained.
3. More overall coordination by MTF forces will be required to prevent large-scale 096 breaches (but that's what NCOs and COs are for!).
Based on the Positives & Negatives, why should this suggestion be accepted:
I believe that each part of this suggestion should be individually judged and approved, but that overall, these changes will bring a more enjoyable and engaged experience for all involved players. Each positive and negative have their own merits, and I predict that these changes essentially uprooting the existing behaviour of an entire SCP is unlikely to be entirely accepted by the community, but it will enhance the fairly accurate lore on CG SCPRP. I haven't made these suggestions with the intention of making it more frustrating to combat SCPs overall, but to balance out 096 and allow it to rival the power of similar-level SCPs. In conclusion, this change will attempt to raise the skill ceiling for 096 players by reducing reliance on random factors (suggestion 1) and making the overall experience more roleplay-oriented and procedurally-intensive/accurate according to lore (suggestions 2 & 3).
If you have read up to this point so far, thank you for your time, and I hope you can at least consider the beneficial implications such a change.
Putting forward a short list of problems regarding SCP-096:
1. Breaches can be stopped outright - Currently, SCP-096's breach is simply spawning a picture of its face in a random(?) location on the map. Any component Foundation player destroying this picture completely wastes the average 2+ hours of breach queue that the SCP-096 player spent sitting there. No other existing breach-able SCP works this way; breaches are guaranteed for them, as their chamber doors "malfunction" and automatically open. Why isn't this same logic applied to SCP-096 breaches? This also calls into question why the face picture spawns facing downwards: would having it spawn facing upward be any more realistic than having a picture of its face spawn randomly?
2. The Bucket - The almighty bucket, a necessary kryptonite to SCP-096. I understand the function the bucket serves is preventing perpetual re-viewing of SCP-096's face on his way to his next targets, but not how easy it is to apply the bucket. Realistically, NOBODY would probably be able to place a bucket on SCP-096's head while its in motion.
Edit: As the addition of TYPE-GREEN SCPs have generally made breaches longer, and SCP-096 will likely no longer breach by himself, the bucket remains untouched.
3. Forced Self-Recontainment - Perhaps the most disappointing realization you can have as an SCP-096 player can have is to have your last target sit in your containment chamber, forcing you to kill all of your other remaining targets and recontain yourself. The other is to drop everything and go to kill that lone individual before you continue on your spree; not very roleplay-accurate, and likely to get the SCP-096 player reported and warned for FailRP. It's essentially a guaranteed strategy for recontainment, with no possible ways to for the 096 player to counter it.
For each of these perceived problems, here's a respective solution to each that wouldn't heavily favour SCP-096:
1. 096's chamber doors fail when auto-breached just like any other breach-able SCP, and may walk out following the existing minute rule. (doesn't leave his breach entire up to chance)
2. Buckets may only be placed on 096 while un-enraged.
Edit: As the addition of TYPE-GREEN SCPs have generally made breaches longer, and SCP-096 will likely no longer breach by himself, the bucket remains untouched.
3. If 096 is "baited" into its cell, given that the chamber remains open, it may walk out of its chamber following the existing minute rule.
Possible Positives of the suggestion (At least 2):
1. Improves realism and consistency surrounding SCP-096's own gameplay mechanics, as well as extending 096's lore-accurate containment procedures and weight of his breaches, making the experience more enjoyable for players who choose to play as 096.
2. The changes mostly work to balance out 096 gameplay by not heavily favoring the SCP player while addressing the lack of sustained contribution SCP-096 has on breaches.
3. Better synergy with other SCPs due to 096 breaching at roughly the same time with other SCP players, allowing for harder-hitting combos that succeed based on collaboration.
4. Differentiates 106 and 096 containment methods more clearly and accurately according to SCP lore (no casualties technically need to be incurred).
Possible Negatives of the suggestion:
1. 096 breaches will be more difficult to recontain due to the fact that there will be little that can be done to stop 096 from viewing other's faces once he's out (although this would incentivize combatives to make the effort to "seal off" areas within 096's predicted path).
2. Initial confusion and player reports caused by SCP-096's recontainment being communicated but not actually being properly contained.
3. More overall coordination by MTF forces will be required to prevent large-scale 096 breaches (but that's what NCOs and COs are for!).
Based on the Positives & Negatives, why should this suggestion be accepted:
I believe that each part of this suggestion should be individually judged and approved, but that overall, these changes will bring a more enjoyable and engaged experience for all involved players. Each positive and negative have their own merits, and I predict that these changes essentially uprooting the existing behaviour of an entire SCP is unlikely to be entirely accepted by the community, but it will enhance the fairly accurate lore on CG SCPRP. I haven't made these suggestions with the intention of making it more frustrating to combat SCPs overall, but to balance out 096 and allow it to rival the power of similar-level SCPs. In conclusion, this change will attempt to raise the skill ceiling for 096 players by reducing reliance on random factors (suggestion 1) and making the overall experience more roleplay-oriented and procedurally-intensive/accurate according to lore (suggestions 2 & 3).
If you have read up to this point so far, thank you for your time, and I hope you can at least consider the beneficial implications such a change.
Last edited:
Donator
Community Sup.
Content Team
Group Moderator