-
Notifications
You must be signed in to change notification settings - Fork 557
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
Consistent LZ names. #5079
Consistent LZ names. #5079
Conversation
Pretty based |
Well i'd argue this makes the "Landing Zone" in the name redundant |
Shouldn't it be consistent the other way around? Like removing the LZ1-2 indicators and focusing more on the Landing Zone location and title? |
The name edits will only show up in the dropship console and remote consoles, having good flavor names is nice but if the pilot doesnt know which is LZ1 and which is LZ2 it can lead to confusion. If the lz1 or lz2 objects are not assigned a custom name, they default to Landing Zone 1, or Landing Zone 2, respectively. Hence why the only changes here are for LZs that have custom names. |
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.
lgtm
About the pull request
Alters the lz1/lz2 names of each map placed object to have LZ1 or LZ2 in the front of the name, that way there's never any confusion over which is which when looking at the DS consoles. "We're going to LZ2" should never be a point of confusion for new POs anymore.
Explain why it's good for the game
Information good.
Testing Photographs and Procedure
Screenshots & Videos
Put screenshots and videos here with an empty line between the screenshots and the
<details>
tags.Changelog
🆑
maptweak: Standardized the names of LZs to include the name of the LZ.
/:cl: