As a way to address #22 and #42, as well as making it easier for new users to actually get set up, I suggest a system that uses "categories" (or "behaviors"). The user would be able to create a new category by giving it a name and assigning priorities to it as if it were any other ability. Then, rather than assigning priorities to each ability individually, there would be an option on each ability to assign it to use a category's behaviors.
I don't know whether it would be feasible to just make a category one more option in the targeting dropdown. That would allow for more customization, but would also likely make programming it more complicated. Having it be either/or of category vs individual list is probably sufficient.
This covers the goal of #22 by allowing a quick way to apply the same targeting list to multiple abilities, with the advantage that changing the category's behavior would also immediately update it for every ability set to that category. It also directly covers #42 without needing any special case logic for revives - it'd just be another category, and then the user could set each revive into that category.
As a way to address #22 and #42, as well as making it easier for new users to actually get set up, I suggest a system that uses "categories" (or "behaviors"). The user would be able to create a new category by giving it a name and assigning priorities to it as if it were any other ability. Then, rather than assigning priorities to each ability individually, there would be an option on each ability to assign it to use a category's behaviors.
I don't know whether it would be feasible to just make a category one more option in the targeting dropdown. That would allow for more customization, but would also likely make programming it more complicated. Having it be either/or of category vs individual list is probably sufficient.
This covers the goal of #22 by allowing a quick way to apply the same targeting list to multiple abilities, with the advantage that changing the category's behavior would also immediately update it for every ability set to that category. It also directly covers #42 without needing any special case logic for revives - it'd just be another category, and then the user could set each revive into that category.