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

Bluespace Event NFZ announcements #2302

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

blackknight954
Copy link

About the PR

I added an additional line of text to the Syndicate Cache and NT Vault announcements stating that there is a three hundred meter NFZ around said entities, and failing to comply would result in persecution

Why / Balance

There are very frequent debates regarding the eligabilities of NFZ's around events, but these are two that are basically universally agreed that they should have NFZ's around them, This would hopefully cause people to stop having a jab at NFSD over these events having NFZ's

How to test

Load up a test server,

trigger the event

Witness the new text that was added.

Media

Changes to Cache announcement
image
Changes to Vault announcement
image

Requirements

Breaking changes

There should not be any.

Changelog

  • Tweak: Updated the NT Vault and Syndicate Cache spawn announcements to include a line about an NFZ being in effect, and to stay clear of the structure.

…he and NT Vault to include information about a no fly zone in the announcement.
@blackknight954 blackknight954 changed the title Updates the announcement regarding the bluespace events Syndicate Cac… Updated the announcement regarding the bluespace events Syndicate Cac… Oct 23, 2024
@blackknight954 blackknight954 changed the title Updated the announcement regarding the bluespace events Syndicate Cac… Bluespace Event NFZ announcements Oct 23, 2024
@Leander-0
Copy link
Contributor

I think the correct word would be prosecution, persecution is a whole different can of worms, about the "three hundred meters" i would say just make it "300m" to make the message a little smaller and help the slow readers.

besides that i think either the SOP or the space law should also reflect this changes for the bluespace events too but i can do those changes later.

@blackknight954
Copy link
Author

I think the correct word would be prosecution, persecution is a whole different can of worms, about the "three hundred meters" i would say just make it "300m" to make the message a little smaller and help the slow readers.

besides that i think either the SOP or the space law should also reflect this changes for the bluespace events too but i can do those changes later.

Made those changes, today I learned the difference between persecute and prosecute.

Copy link
Contributor

@whatston3 whatston3 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've made suggestions to shorten the text given, as well as the ending text, for both of the events.

Honestly, the guidance coming down from Centcomm makes sense (doing something? too bad, this is valuable, you're on guard duty now). I'm not really fond of the range being a fixed amount in the text itself rather than a "guard this, figure out how, but feel free to do XYZ" prompt. Wouldn't "A No Fly Zone may be declared." do the job?

Resources/Locale/en-US/_NF/bluespace-events/events.ftl Outdated Show resolved Hide resolved
Comment on lines +4 to 5
station-event-bluespace-cache-start-announcement = A Syndicate transport has been intercepted from FTL and will soon arrive nearby. Guard the armored weapons cache until NanoTrasen can retrieve it for a reward. A No Fly Zone of 300 meters has been established. Failure to comply will result in prosecution
station-event-bluespace-cache-end-announcement = We have successfully retrieved the Syndicate weapons cache from your sector and have reimbursed your nearby Frontier Outpost accordingly.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
station-event-bluespace-cache-start-announcement = A Syndicate transport has been intercepted from FTL and will soon arrive nearby. Guard the armored weapons cache until NanoTrasen can retrieve it for a reward. A No Fly Zone of 300 meters has been established. Failure to comply will result in prosecution
station-event-bluespace-cache-end-announcement = We have successfully retrieved the Syndicate weapons cache from your sector and have reimbursed your nearby Frontier Outpost accordingly.
station-event-bluespace-cache-start-announcement = A Syndicate weapons cache is inbound to the sector. The area 300m around the cache is a No Fly Zone. Station accounts will be rewarded for guarding the cache.
station-event-bluespace-cache-end-announcement = We have retrieved the Syndicate weapons cache from your sector. Station accounts have been remunerated.

Co-authored-by: Whatstone <166147148+whatston3@users.noreply.github.com>
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