Content Suggestion 096 Suggestion

[Headjuice]

Currently, it’s possible to place a bucket on SCP-096 even while he is in his enraged state — sometimes immediately after he kills his first target. This allows players to stop him unfairly, even as he’s running through people during his rampage.


As an E-11 player, I’ve personally always waited until SCP-096 calmed down before attempting to bucket him — simply because it’s fairer for the SCP player.
Also Blindfolding 096 should be not allowed for this is the bucket ....

Problem:


Little counterplay for SCP-096: He often loses his rage after one kill, before he can reach other targets.
Breaks immersion: A rampaging SCP violently killing people shouldn’t be stopped by someone placing a bucket on his head mid-sprint.
Balance issue: The current mechanic makes SCP-096 too easy to neutralize.

Suggested fix:
Bucket Spawn Limitation:
Only one bucket exists at a time on the map.
It spawns in a randomized location each time (to prevent camping).

Spawn Cooldown:
After a bucket is used, the next one only spawns after a 5-minute cooldown.
This prevents constant re-bucketing and encourages thoughtful use.

Disable bucket interaction while enraged: Bucketing should only be possible once SCP-096 is fully calm again.
Alternatively:
Brief post-kill immunity to bucketing, allowing a short window for follow-up kills before being contained.

 

[Sneefo]

follow format or this will be instantly denied king

 

[Sule Goodman]

- support

one bucket is aids.

 

[Emilia Foddg]

Currently, it’s possible to place a bucket on SCP-096 even while he is in his enraged state — sometimes immediately after he kills his first target. This allows players to stop him unfairly, even as he’s running through people during his rampage.

As an 096 main, I fully get this frustration. I hate when this happens.

As an E-11 player, I’ve personally always waited until SCP-096 calmed down before attempting to bucket him — simply because it’s fairer for the SCP player.

Based

Also Blindfolding 096 should be not allowed for this is the bucket

???

Little counterplay for SCP-096: He often loses his rage after one kill, before he can reach other targets.

Yes.

Breaks immersion: A rampaging SCP violently killing people shouldn’t be stopped by someone placing a bucket on his head mid-sprint.

Okay.

Balance issue: The current mechanic makes SCP-096 too easy to neutralize.

You can't just say 'perchance'.

Suggested fix:
Bucket Spawn Limitation:
Only one bucket exists at a time on the map.
It spawns in a randomized location each time (to prevent camping).

Spawn Cooldown:
After a bucket is used, the next one only spawns after a 5-minute cooldown.
This prevents constant re-bucketing and encourages thoughtful use.

No. Even assuming that you're just referring to the site overall (Because if you mean the entire map, wtf are F going to do if the bucket spawns in CI or GOC base? You know they have buckets too, right?), this is entirely too much and too weird. Why wouldn't there be buckets in the places that there are now? You've started this out with an argument for 'what makes sense' and proposed something that makes no sense off of that.

Disable bucket interaction while enraged: Bucketing should only be possible once SCP-096 is fully calm again.

This I feel would be a little too much - I wouldn't mind a softer solution such as making bucketing while enraged dependant on RNG; Say you're trying to bucket 096 as he's running through the site, if you get him, the bucket has maybe something like a 80% chance to actually land - If it fails, it force-drops the bucket from the player.

Alternatively/in addition, you could have the bucket durability constantly drain at a moderate pace while 096 is enraged and sprinting. This is also fair, doesn't make bucketing while enraged the breach killer that it is, and would make sense to be something that happens in line with your given reasoning.

Brief post-kill immunity to bucketing, allowing a short window for follow-up kills before being contained.

No. This is entirely too much and again, counter to your reasoning of 'what makes sense'.
-Support

 

[dougdougjones]

As an 096 main, I fully get this frustration. I hate when this happens.

Based

???

Yes.

Okay.

You can't just say 'perchance'.

No. Even assuming that you're just referring to the site overall (Because if you mean the entire map, wtf are F going to do if the bucket spawns in CI or GOC base? You know they have buckets too, right?), this is entirely too much and too weird. Why wouldn't there be buckets in the places that there are now? You've started this out with an argument for 'what makes sense' and proposed something that makes no sense off of that.

This I feel would be a little too much - I wouldn't mind a softer solution such as making bucketing while enraged dependant on RNG; Say you're trying to bucket 096 as he's running through the site, if you get him, the bucket has maybe something like a 80% chance to actually land - If it fails, it force-drops the bucket from the player.

Alternatively/in addition, you could have the bucket durability constantly drain at a moderate pace while 096 is enraged and sprinting. This is also fair, doesn't make bucketing while enraged the breach killer that it is, and would make sense to be something that happens in line with your given reasoning.

No. This is entirely too much and again, counter to your reasoning of 'what makes sense'.
-Support

Bros yapping but I agree

 

[Murlon]

+support for "Disable bucket interaction while enraged"

 

[Walter532]

+support for "Disable bucket interaction while enraged"

Lore wise it makes sense but ingame it would be an infinite loop of him killing people 70% of the time