Senior Game Master
Donator
What does this suggestion change/add/remove:
Disable auto-breaching under 40 players. Breach queues will become "suspended" until the 40 player threshold is met. Time will pause once it dips below 40 players and resume when the threshold is met again.
Has something similar been suggested before? If so, why is your suggestion different?
No.
Possible Positives of the suggestion (At least 2):
- Preserves server health below 40 players.
- Frequently D-Class or CI breach SCPs anyways during low pop. This gives a tiny nerf to an auto-breach happening on top of SCPs already being breached (happens all the time during low pop on US)
Possible Negatives of the suggestion:
- Not many, really - unless it's a slow morning for CI raids/D-Class escapes in which case playing an SCP to wait to be breached is kinda pointless.
Based on the Positives & Negatives, why should this suggestion be accepted?
Over the past 2 months I've been on during low pop hours (5am EST to 11am EST) and consistently nearly every morning D-Class have escaped and disguised due to the extremely low population of gensec, or CI has raided at the bare minimum MTF. Having this change where auto-breaches are suspended would essentially allow SCPs to continue to be breached without severely screwing over the site when they are breached. Several times as well, SCPs may be breached by D-Class or CI to have an auto breach happen on top of that. When that happens with less than 10 combatives on site, it triggers code black scenarios.
Disable auto-breaching under 40 players. Breach queues will become "suspended" until the 40 player threshold is met. Time will pause once it dips below 40 players and resume when the threshold is met again.
Has something similar been suggested before? If so, why is your suggestion different?
No.
Possible Positives of the suggestion (At least 2):
- Preserves server health below 40 players.
- Frequently D-Class or CI breach SCPs anyways during low pop. This gives a tiny nerf to an auto-breach happening on top of SCPs already being breached (happens all the time during low pop on US)
Possible Negatives of the suggestion:
- Not many, really - unless it's a slow morning for CI raids/D-Class escapes in which case playing an SCP to wait to be breached is kinda pointless.
Based on the Positives & Negatives, why should this suggestion be accepted?
Over the past 2 months I've been on during low pop hours (5am EST to 11am EST) and consistently nearly every morning D-Class have escaped and disguised due to the extremely low population of gensec, or CI has raided at the bare minimum MTF. Having this change where auto-breaches are suspended would essentially allow SCPs to continue to be breached without severely screwing over the site when they are breached. Several times as well, SCPs may be breached by D-Class or CI to have an auto breach happen on top of that. When that happens with less than 10 combatives on site, it triggers code black scenarios.
Last edited:
