What does this suggestion change/add/remove
This suggestion would make it so the maximum breach count scales with server population instead of what it is right now where once you hit 60 players you can mass breach everything. The theoretical max breach count allows for 9 SCPs to be breached at the same time as long as there's more than 65 players on the server (1st breach as 035, 3 from 035 hacking out scps with breach tools 3 from those scps breach tools, 4 from the hacked SCPs breach tools and 035's, and 035 dragging 096 out of his CC). During downtime, this leaves about 1 scp for every 6-8 people to handle which is just completely unreasonable. When you factor in for other GOIs, D class, afk people, and non-combatants, the actual ratio is more like 1.5-2.5 combative foundation for every SCP out, with around 1-4 MTF total to handle 9 SCPs during downtime. These nine SCP breaches frequently lead to nukes even during time the server is full, and the lack of people on the server during downtime essentially makes 4AM-10AM ish non stop breach simulator.
A theortical scale for this could be three SCPs at 50 players, then 1 for every 10 past that point, this will also include both 035 and 096 to the breach count making it more reasonable to breach 035 and 096 during high pop and discourage it during low pop. It would also factor in for the people on the SCP unlike the old scale which didn't factor SCPs into the calculation. This would also calculate total SCP breaches compared to now where the system is divided between hacking and breach tool uses.
Has something similar been suggested before? If so, why is your suggestion different?
Couldn't find anything recent from the October update.
Possible Positives of the suggestion (At least 2)
- Would allow a much more reasonable scale of SCP breach power vs people fighting the breach
- Prevent downtimes constant breach RP.
- Gives foundation a fighting chance to actually recontain breaches during down time without staff intervention.
- Overall beneficial for server health
Possible Negatives of the suggestion
- Likely would take a bit of time to properly implement as scaling it properly would need to be tested overtime.
- SCP mains will be mad they can no longer kill farm as much.
This suggestion would make it so the maximum breach count scales with server population instead of what it is right now where once you hit 60 players you can mass breach everything. The theoretical max breach count allows for 9 SCPs to be breached at the same time as long as there's more than 65 players on the server (1st breach as 035, 3 from 035 hacking out scps with breach tools 3 from those scps breach tools, 4 from the hacked SCPs breach tools and 035's, and 035 dragging 096 out of his CC). During downtime, this leaves about 1 scp for every 6-8 people to handle which is just completely unreasonable. When you factor in for other GOIs, D class, afk people, and non-combatants, the actual ratio is more like 1.5-2.5 combative foundation for every SCP out, with around 1-4 MTF total to handle 9 SCPs during downtime. These nine SCP breaches frequently lead to nukes even during time the server is full, and the lack of people on the server during downtime essentially makes 4AM-10AM ish non stop breach simulator.
A theortical scale for this could be three SCPs at 50 players, then 1 for every 10 past that point, this will also include both 035 and 096 to the breach count making it more reasonable to breach 035 and 096 during high pop and discourage it during low pop. It would also factor in for the people on the SCP unlike the old scale which didn't factor SCPs into the calculation. This would also calculate total SCP breaches compared to now where the system is divided between hacking and breach tool uses.
Current Max Breach Scale | New Max Breach Scale |
0-65= 5 | 0-50 = 3 |
65+ = 9 | 51-60 = 4 |
61-70 = 5 | |
71-80 = 6 | |
81-90 = 7 | |
91-100 = 8 | |
100+ = 9 |
Has something similar been suggested before? If so, why is your suggestion different?
Couldn't find anything recent from the October update.
Possible Positives of the suggestion (At least 2)
- Would allow a much more reasonable scale of SCP breach power vs people fighting the breach
- Prevent downtimes constant breach RP.
- Gives foundation a fighting chance to actually recontain breaches during down time without staff intervention.
- Overall beneficial for server health
Possible Negatives of the suggestion
- Likely would take a bit of time to properly implement as scaling it properly would need to be tested overtime.
- SCP mains will be mad they can no longer kill farm as much.