Quick fix for getArea #710
Merged
Conversation
This file contains 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
|
https://community.bistudio.com/wiki/triggerArea
|
|
Worth noting there is now a BI function which does this too: https://community.bistudio.com/wiki/BIS_fnc_getArea Perhaps the CBA version should be deprecated |
|
Yes, this looks like it could be gently deprecated. Please add a deprecation comment in the header (see arrays/fnc_join.sqf for the format) |
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.
somewhere along the line "triggerArea" started returning z values, making the return array size 6. This causes problems for other functions using the area format so this change simply removes the 6th element of the array.