Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bluey SOP Modification #70

Closed
wants to merge 2 commits into from

Conversation

SixplyDev
Copy link
Contributor

Description

Bluey now prioritizes the nuke disk first, NTR & Captain second, and then the other heads of staff third


TODO

  • Adjust Bluey priorities in SOP

Changelog

🆑 ShirouAjisai

  • tweak: Adjusted Blueshield priorities in SOP

Bluey now prioritizes the nuke disk first, NTR & Captain second, and then the other heads of staff third
@CerberusWolfie
Copy link
Contributor

Is this for situations where the Captain doesn't have the disk? The BSO should never have the disk unless the Heads of Staff are dead and there are no alternatives to holding them.

@SixplyDev
Copy link
Contributor Author

SixplyDev commented Jan 29, 2025

Is this for situations where the Captain doesn't have the disk? The BSO should never have the disk unless the Heads of Staff are dead and there are no alternatives to holding them.

Yes, this is basically for situations where the disk is up in the air & the decision has to be made between the disk and someone else. I feel like the disk is a lot more important & should be secured first and foremost. People can be recovered afterwards. The intention is not for the Blueshield to be in possession of the disk 24/7.

@CerberusWolfie
Copy link
Contributor

Is this for situations where the Captain doesn't have the disk? The BSO should never have the disk unless the Heads of Staff are dead and there are no alternatives to holding them.

Yes, this is basically for situations where the disk is up in the air & the decision has to be made between the disk and someone else. I feel like the disk is a lot more important & should be secured first and foremost. People can be recovered afterwards. The intention is not for the Blueshield to be in possession of the disk 24/7.

You should clarify this then. This will be easily misinterpreted as securing the disk in possession.

Clarified that the Blueshield should only have the disk when there's no suitable command to secure it. It should be immediately relinquished when a suitable command member has been located.
@Sarahon
Copy link
Contributor

Sarahon commented Jan 29, 2025

Tell me, when is there EVER not a single person better to take the nuke disk?

@SixplyDev
Copy link
Contributor Author

The point isn't that there's "not ever a person" but the fact that the nuke disk is unsecured & should be first secured above all else.

@Sarahon
Copy link
Contributor

Sarahon commented Jan 29, 2025

The point isn't that there's "not ever a person" but the fact that the nuke disk is unsecured & should be first secured above all else.

If it's unsecured, then BSO takes it to give it to somebody, Just that simple.

@SixplyDev SixplyDev closed this Jan 30, 2025
@SixplyDev SixplyDev deleted the erm.-sop-fuckery branch January 30, 2025 19:50
@SixplyDev
Copy link
Contributor Author

Remaking repo & branch

@SixplyDev SixplyDev mentioned this pull request Jan 30, 2025
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants