-
-
Notifications
You must be signed in to change notification settings - Fork 553
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
Fixes a runtime with SecurEye and updates bodycamera descriptions #4103
Fixes a runtime with SecurEye and updates bodycamera descriptions #4103
Conversation
if(!active_camera) | ||
show_camera_static() | ||
return | ||
else if (active_camera.loc == null) | ||
show_camera_static() |
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.
any reason not to slap an OR here instead?
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.
The reason it's staggered like this is because if no active camera is selected, the reference would be set to null, and this was causing runtimes when active_camera was null (because null.loc would throw a runtime)
This should check if active_camera is not null first, and then evaluate if the location is null
Truth be told, I could've made lines 179 through 181 their own if function instead of chaining it up with the if function starting at line 176, but the behavior is functionally the same
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.
ok gotcha sounds fine
…iptest-ss13#4103) <!-- Write **BELOW** The Headers and **ABOVE** The comments else it may not be viewable. --> <!-- You can view Contributing.MD for a detailed description of the pull request process. --> ## About The Pull Request This PR should fix a runtime that had been popping up with bodycameras during their testmerges. It should also fix part of the description for them that I'd erroneously made bold. ## Why It's Good For The Game Runtimes are not good, and the description was a little confusing in what words were made bold. A single missing character causes untold havoc yet again. ## Changelog :cl: fix: fixed securEye runtime fix: fixed bodycamera description typo /:cl: <!-- Both :cl:'s are required for the changelog to work! You can put your name to the right of the first :cl: if you want to overwrite your GitHub username as author ingame. --> <!-- You can use multiple of the same prefix (they're only used for the icon ingame) and delete the unneeded ones. Despite some of the tags, changelogs should generally represent how a player might be affected by the changes rather than a summary of the PR's contents. -->
About The Pull Request
This PR should fix a runtime that had been popping up with bodycameras during their testmerges. It should also fix part of the description for them that I'd erroneously made bold.
Why It's Good For The Game
Runtimes are not good, and the description was a little confusing in what words were made bold. A single missing character causes untold havoc yet again.
Changelog
🆑
fix: fixed securEye runtime
fix: fixed bodycamera description typo
/:cl: