Content Suggestion Breach Queue Pause timer

[Reposted_]

What does this suggestion change/add/remove:
Set a 30-40 minute timer once an SCP has been breached to restart the Breach Queue.

Has something similar been suggested before? If so, why is your suggestion different?:
Many people (myself included) have requested various forms of breach changes but to my knowledge no-one has asked to set a timer on the Breach pause.

Possible Positives of the suggestion (At least 2):
Allows for SCPs who tend to take significant time to be recontinued, or even be properly breached in the first place (035 and 966) to be played without frustrating other players in queue. As well as restarting the breach queue if an SCP is captured by CI or GOC and take a significantly longer time to be recontained or destroyed by one of them.

Possible Negatives of the suggestion:
If a breach lasts for 2+ hours an SCP may breach during another SCP's breach which might be an issue with less players. But this can be solved by not enabling the timer at lower player counts.

Based on the Positives & Negatives, why should this suggestion be accepted:
This would help solve the frustration that many SCP players have with the breach queue pause that has caused many to angrily leave the server or swap off of SCP which leaves them frustrated at whatever wasted time they spent on a SCP while also minimizing the issues that such a request may cause.

 

[Marvin Garden]

I feel like it would be easier to just make it so if all SCPs are cuffed the queue resumes

 

[Emilia Fοddg]

+/- Neutral +Support
I prefer Marvin's solution. That kind of logic already exists for ERT exfil, no reason it shouldn't apply to the Breach Queue, too

 

[Reposted_]

I feel like it would be easier to just make it so if all SCPs are cuffed the queue resumes

+/- Neutral
I prefer Marvin's solution. That kind of logic already exists for ERT exfil, no reason it shouldn't apply to the Breach Queue, too

While it does solve the return trip or when CI or GOC have scps it doesn't solve the issue of certain SCP's breaches taking significantly longer than most other breaches. Im not saying this is a bad idea, and do think it would be a good addition. Just that it overlooks the other problem I mentioned

 

[Comet Tiggle]

I feel like it would be easier to just make it so if all SCPs are cuffed the queue resumes

Stop being a genius, we need suggestions smh

 

[Emilia Fοddg]

While it does solve the return trip or when CI or GOC have scps it doesn't solve the issue of certain SCP's breaches taking significantly longer than most other breaches. Im not saying this is a bad idea, and do think it would be a good addition. Just that it overlooks the other problem I mentioned

I think it would pose too much of a problem to RP to expect all breaches to only take a specific amount of time before the breach queue continues - A big part of the entire reason the pause was introduced in the first place was to allow for enough time for RP to happen after being interrupted by a breach. Whereas generally RP starts back up when SCPs are cuffed anyway, give or take a minute or two; So that's a reasonable assumption to make - But punishing F for 'a breach taking too long' is unreasonable. Marvin's solution is most likely the best compromise you'll get in this manner.

My personal recommendation on the matter for disgruntled SCP players is to get an 096 whitelist, as the picture can spawn randomly outside of needing the breach queue to do so.

 

[Reposted_]

as the picture can spawn randomly outside of needing the breach queue to do so.

Oh I always thought it was an O5 fucking with people XD.

I think it would pose too much of a problem to RP to expect all breaches to only take a specific amount of time before the breach queue continues - A big part of the entire reason the pause was introduced in the first place was to allow for enough time for RP to happen after being interrupted by a breach.

That is why I suggested the timer to be 30-40 minutes as that is a long enough delay imo if an scp breaches the whole time to prevent SCP breaches to truly harm RP to such an extent.

But punishing F for 'a breach taking too long' is unreasonable.

I agree and yet when on occasion I play 035 many other scp players begin to complain in chat about the extended breach pauses periods. A long timer before the queue restarts gives the longer breaches time scp's to do their thing while also alleviating the scp's in queues complaints on the breach duration.

Marvin's solution is most likely the best compromise you'll get in this manner.

I 100% agree that Marvin's idea should be added, but that doesn't mean it should be the only change to the pause.

 

[Emilia Fοddg]

That is why I suggested the timer to be 30-40 minutes as that is a long enough delay imo if an scp breaches the whole time to prevent SCP breaches to truly harm RP to such an extent.

I agree and yet when on occasion I play 035 many other scp players begin to complain in chat about the extended breach pauses periods. A long timer before the queue restarts gives the longer breaches time scp's to do their thing while also alleviating the scp's in queues complaints on the breach duration.

I 100% agree that Marvin's idea should be added, but that doesn't mean it should be the only change to the pause.

Honestly, I don't really disagree - Personally I'd be fine with both. My thoughts are more along the lines of how Content might see it. By all means, push for the delay to resume idea, but with how everyone's conditioned regarding breaches, I don't think you're going to convince them no matter what length of time you set for the queue timer to continue.