broma-arma / BromA-Framework-A3-Addon

The addon version of the BromA Framework for ArmA 3.
5 stars 9 forks source link

Tasks - Priority issues #184

Closed Coryf88 closed 2 weeks ago

Coryf88 commented 2 years ago

Only Primary is relevant for winning/failing a mission. Secondary and Optional are the same, with the only difference being that Secondary tasks are set as cancelled instead of failed when the task is failed.

It would make sense that Secondary should also be required to win a mission, but won't fail a mission if the task fails. The documentation seems to imply that is how it should work.

Perhaps another priority should also be added to cover the case of wanting the opposite. I.e. Task fails mission, but not required to win. Though, I'm not sure what the name of such a priority would be nor an example for its use. Abortive. "Keep X alive"

The labelling of a priority in-game is also not very self-descriptive. Currently a prefix of "(!)" is used for Primary, nothing for Secondary, and "(OPTIONAL)" for Optional. Instead, prefix task name with "(P) ", "(S) ", "(O) ", or "(A) " for Primary, Secondary, Optional, or Abortive, respectively. Also, prepend the task description with a description of what the priority means. E.g. "<i>(A)bortive: Not required to win and can fail the mission.</i><br />"