I'm just messing around with requirements for the first time and it isn't very intuitive. And I can't seem to find a tutorial.
1. The "Count Ability"-thing measures the level of an ability, it doesn't count how often the ability is used. Right?
2. How would I have to set up a requirement so stuff only happens if a unit does NOT have a certain behavior? I saw the "Behavior allowed", should I use that? Or should I use "Count behavior"? Both seem like they could work.
1. If you want to check how many times the ability is used, it should be something like this:
-Greater Than Or Equal To
-Count ability [...] Completed at Unit
-Constant x
2. This can be done through validators. Use the type ''Unit Compare Behavior Count''.
1. The "Count Ability"-thing measures the level of an ability, it doesn't count how often the ability is used. Right?
This is correct. If you want to keep track of execution count, let the ability apply behavior stacks and check those, or try to realize your desired behavior via charges.
Quote:
2. How would I have to set up a requirement so stuff only happens if a unit does NOT have a certain behavior? I saw the "Behavior allowed", should I use that? Or should I use "Count behavior"? Both seem like they could work.
I would prefer Count Behavior == 0. Behavior Allowed would probably also return true, if all requirements for the behavior are met, but it is simply not applied to the unit.
Hey there
I'm just messing around with requirements for the first time and it isn't very intuitive. And I can't seem to find a tutorial.
1. The "Count Ability"-thing measures the level of an ability, it doesn't count how often the ability is used. Right?
2. How would I have to set up a requirement so stuff only happens if a unit does NOT have a certain behavior? I saw the "Behavior allowed", should I use that? Or should I use "Count behavior"? Both seem like they could work.
1. If you want to check how many times the ability is used, it should be something like this:
-Greater Than Or Equal To
-Count ability [...] Completed at Unit
-Constant x
2. This can be done through validators. Use the type ''Unit Compare Behavior Count''.
This is correct. If you want to keep track of execution count, let the ability apply behavior stacks and check those, or try to realize your desired behavior via charges.
I would prefer Count Behavior == 0. Behavior Allowed would probably also return true, if all requirements for the behavior are met, but it is simply not applied to the unit.
Aight, Thanks :)