As I'm sure some of you already know, this is in the ability template:
var class<X2TargetingMethod> TargetingMethod; // UI interaction class. Specifies how the target is actually selected by the user
var class<X2TargetingMethod> SecondaryTargetingMethod; // Same as Targeting Method, but this gets used if we want a separate target method after we select/confirm an ability.
There is some commented out code in some hud UI for it, and the tactical input has a state for it, but it is currently non-functional. The intent is when an ability activation wants two distinct pieces of information from the player, like say, a destination and then a direction. Any interest in resurrecting this?
As I'm sure some of you already know, this is in the ability template:
There is some commented out code in some hud UI for it, and the tactical input has a state for it, but it is currently non-functional. The intent is when an ability activation wants two distinct pieces of information from the player, like say, a destination and then a direction. Any interest in resurrecting this?