You need ot have 2 buttons and two abilities. One for applying the behavior, and another one for removing it. The applying ability command need a visibility requirement "number of instances of the behavior on unit equals zero". The removing ability' command need "number of instances of the behavior on unit more than zero".
So, when a unit owns the behavior, it only has the remove button, and vice versa.
And your behavior need to have max stack = 1 if you want to avoid stacks.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
You need ot have 2 buttons and two abilities. One for applying the behavior, and another one for removing it. The applying ability command need a visibility requirement "number of instances of the behavior on unit equals zero". The removing ability' command need "number of instances of the behavior on unit more than zero".
So, when a unit owns the behavior, it only has the remove button, and vice versa.
And your behavior need to have max stack = 1 if you want to avoid stacks.