-
Notifications
You must be signed in to change notification settings - Fork 510
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
base: master
Are you sure you want to change the base?
Conversation
…he and NT Vault to include information about a no fly zone in the announcement.
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. |
There was a problem hiding this 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?
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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>
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
Changes to Vault announcement
Requirements
Breaking changes
There should not be any.
Changelog