Content Suggestion Stop/Change 096 Bucket Removing the Picture

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

What does this suggestion change/add/remove:

Currently, any active 096 picture is removed the moment 096 is bucketed. This suggestion asks for this specific function to be removed, allowing any extant 096 picture to remain after 096 is bucketed to be subsequently swept for and destroyed by players.

If this is too much (Or there is concern regarding prevention of infinite rebreach via a stuck picture or something), alternatively consider removing it on cuff instead - Or additionally consider removing the picture after some kind of short duration rather than instantly - Whether this be some time following being cuffed or following being bucketed.

EDIT: I think that ideally a timer implementation would follow the logic of -
  1. On bucket (or cuff), start the timer

  2. The amount of time passes

  3. When the time is up, check if still bucketed/cuffed

  4. If so, remove picture

And additionally to compensate, make bucket health always maximum, instead of being random like it is now.

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

Cursory search reveals nothing similar. There have been numerous 096 suggestions, but nothing asking for this specific change about the bucket removing the picture.

I do have another active suggestion asking for sweeping balance changes to all SCPs, which includes an idea relating to 096 pictures, but the main premise of that suggestion extends beyond the scope of just 096 pictures - Plus does not particularly conflict with this idea.

Possible Positives of the suggestion (At least 2):

  • + Encourages players dealing with 096 to sweep for and destroy 096 pictures more (IMO an underused feature, because of how buckets remove the picture), instead of purely relying on the bucket and just waiting for 096 to kill all remaining targets before RC

  • + Allows for the majority of 096 breaches to be more enjoyable for 096 - Rather than just being "be breached, leave CC, be bucketed immediately after exiting HCZ, kill one or two people and then be RC'd" which I find is how most 096 breaches tend to go

  • + (UK) Potentially more use of Code 4s

  • + Generally makes more sense that the bucket doesn't magically remove the cognitohazard

  • + Makes 096 more fearsome and varied to play against, given its strict rules for play

Possible Negatives of the suggestion:

  • - Difficulty of implementation depending on approach

  • - Bucket nerf = breach buff + Imbalance

  • - Changes may result in buggy behaviour, which carries significant server health concerns

  • - Spawn trapping issues with certain picture locations, such as a CS spawn basically trapping Researchers in RSD Wing (Honestly, just remove this and similar locations. There's no need for such a damaging location to be part of 096 picture spawns)

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

From my perspective as an 096 main and former E-11 CPT is that 096 breaches are trivial to RC, primarily because buckets are so powerful in that they instantly remove the picture when bucketing 096. I've lost count of the amount of times I've reached the top of HCZ prim and immediately there has always been some CM or GSD or E-11 or whoever ready with a bucket to bucket me (Both servers). Which is fine as a gameplay tactic IMO (Unless they're bodyblocking which is hard to prove/not do in the first place, because rubberbanding), but this almost always means that by the time I reach LLCZ (Or """Delta Wing""" for you US players), there is only ever 1 target who has seen the picture - And will only ever be 1 target to kill for the remainder of that breach, because all vectors to see 096's face have been removed, while 096 already has at least 1 person on them ready to RC them.

This is also still an issue in cases where other SCPs are breached alongside 096 (or they are the one(s) getting 096 out), as 096's limitations make co-operation between SCPs infeasible. When enraged, 096 is so much faster than other SCPs that if the defenders aren't overwhelmed, they can easily cut off 096 from the other SCP(s) and recontain them (which I don't really have an issue with, this is simply good tactics) and when no longer enraged, the combination of 096 having to stay in place for a short time and 096's slow speed leave the other SCP(s) with the options of either stick with 096 and try to defend at the risk of being RC'd faster, or abandon 096 entirely and continue with the breach, leaving 096 to be swiftly and easily RC'd.

I recall a recent mass breach in which there was a whole slew of breached SCPs and I was the 096 among them - We all went up primary and completely rolled the giant firing line waiting to greet us, which in the aftermath left me having to stick around for a little bit after killing my last target and everyone else just filtering into LCZ to continue the breach - Which, unsurprisingly, resulted in me being immediately RC'd by the next person to show up. Situations like this are unavoidable in cases where the other SCPs breach 096 themselves, but can (and IMO, should) be mitigated in cases where 096 had a picture spawned, but was removed because 096 got bucketed.

All in all, no matter which way you slice it, the bucket instantly removing 096's picture is my biggest gripe with 096 breach mechanics as they are now. I get why it exists as a balance measure to prevent constant rebreaches and annoyance on the part of F players, but in my experience I feel that it's a measure that overcompensates and makes 096 breaches less fun than they could be.

IMO, players should just learn to sweep for 096 pictures as a part of dealing with 096 breaches. I've had a few recent breaches on US where I think they seem to think that what this suggestion's asking for is already the case? Where I was bucketed and then as I was being RC'd, people were saying "there's an 096 pic somewhere in there" from where I was being RC'd from, despite the fact that the picture had been removed the instant I was bucketed. And that makes sense, I think that from a recontainment perspective, if you don't intrinsically know that the the bucket removes the picture (which also feels metagamey?), then you'd find the bucket removing the picture unintuitive.

Additionally take into account that, if the bucket doesn't remove the picture immediately, then when bucketed - With new people seeing the picture, the bucketed 096 will basically be constantly drawn towards the picture, which would lead to it being found anyway. Keep in mind that 096 can only break a bucket when not enraged.

EDIT:

Something important to note from the replies was that this seems to be new knowledge for a lot of people, further reinforcing my point about it being unintuitive - Furthermore, consider that since people generally didn't know that the bucket removes the picture, there may have been a not-insignificant amount of time already lost sweeping for a picture that doesn't exist.
 
Last edited:
Honestly.. 096 needs to have 2 ways of his picture getting out.

A nice chance would be 079 can Past his picture onto a computer Stopping the need to open his doors and 096 slowly walk out.

And his picture can spawn on a computer in A set location like rsd wing or Medical center. And his normal picture can spawn as it is now.
 
  • Like
Reactions: Emilia Foddg