Content Suggestion Reactor Hacking Alert System

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

Porkchop

Civil Gamers Expert
One Year Club Advent 2024 Advent 2025
Dec 25, 2024
39
14
61
Sweden
What does this suggestion change/add/remove:
Add a hacking sound or notification when a reactor turbine is being hacked. This would be similar to the SCP hacking system (e.g., a voice line like “Hacking in reactor”).

The purpose is to give E11 a chance to respond before a turbine is destroyed. Currently, CI can enter the reactor and disable turbines without E11 being aware, especially if they are occupied fighting SCPs. This change would provide an early warning so combatives can respond in time.

There are two possible implementations:
  1. A global notification to all combatives (similar to SA area alerts)
  2. A more realistic option where only E11 and CU receive the notification (similar to SCP hacking alerts)


Has something similar been suggested before? If so, why is your suggestion different?:
No, I couldn't find anything.

Possible Positives of the suggestion (At least 2):
  • Gives E11 and combatives time to respond before turbines are destroyed
  • Improves gameplay balance between CI and E11
  • Reduces frustration and sudden losses due to lack of information


Possible Negatives of the suggestion:
  • Makes it harder for CI to successfully sabotage the reactor

Based on the Positives & Negatives, why should this suggestion be accepted:
This change would improve fairness and response opportunities for E11 without completely removing CI’s ability to sabotage the reactor. It adds counterplay rather than preventing the action entirely.
 
Upvote -6 Downvote
Major -Support
Speaking as a former E-11 CPT & Nu7 CPL, this would not only be a bad change, but as others have said, is already a thing to an extent. There is already procedure in place for both E-11 and Nu7 response when CI are hacking reactor. Usually when they are, chances are it's already a known C1 and we're already sweeping for them. Increasing the amount of information Foundation gets in this scenario would just be whaling on CI's gameplay loop for the sake of whaling on CI's gameplay loop. As far as I'm concerned this specifically is a solved problem.

Speaking personally as one of the E-11 that CI put cat ears on that one time (yes really, it was extremely funny) the main issue that comes from CI reactor raids is that reactor is a very good hold location for CI with a single choke point entrance. There isn't no counterplay, but it's just an annoying hold location from F perspective. At this time, I don't really believe that anything needs to be done about reactor in any capacity - The annoyance of dealing with it as a hold location is the penalty for letting them even get there in the first place. Reactor should be a significant priority area to check when dealing with CI raids that are suspected to be going toward HCZ, and CI reactor holds are the consequence of failing to successfully handle it. The gameplay loop is stable.
 
You must log in or register to reply here.
Top Bottom
Back