Laser - Fix PLD rangefinding being dependent on the designation laser#10994
Merged
PabstMirror merged 2 commits intoacemod:masterfrom Jul 7, 2025
Merged
Conversation
PabstMirror
approved these changes
Jul 7, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When merged this pull request will:
Since many modern PLDs are marketed with an eye-safe RF, and designation lasers generally not being eye-safe, it follows that the 2 features are independent from one another.
I also added the laser code indicator that was previously only implemented on the NATO designator. It would look more in line with the baseline UI with a box around the laser code, but my GUI modding abilities are insufficient (feedback appreciated).