You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 28, 2020. It is now read-only.
For review purposes, it would be nice if a subset of markers would be logged to the AAR. Markers are often used to mark the overall plan as well as contact reports, which would be useful feedback during review (did all elements head the right way? Did we kocate spotted enemies correctly?).
Logging side and global markers would likely be sufficient.
The text was updated successfully, but these errors were encountered:
@mistergoodson the above PR is now merged. Next CBA version will allow you to react on created/deleted map markers. Though this event will also fire for auto generated markers (e.g. when using a BlueForceTracking Script/Mod). You might want to make logging map markers an option or add a whitelist/blacklist for certain map markers.
For review purposes, it would be nice if a subset of markers would be logged to the AAR. Markers are often used to mark the overall plan as well as contact reports, which would be useful feedback during review (did all elements head the right way? Did we kocate spotted enemies correctly?).
Logging side and global markers would likely be sufficient.
The text was updated successfully, but these errors were encountered: