I'm trying to create some custom unit attributes (for a large number of units), but I need to be able to modify them. Using behaviors has really gotten me nowhere as you can't seem to modify their values on the fly without massive amounts of pre-set values. Is there any way to create attributes (just a set of numbers on each unit) without using behaviors?
Seems like you're asking for a quick escape route. Do you have any good reasons for not using Behaviors. Not spending more than 20 minutes on figuring it out doesn't count as a "good reason". ;)
I'll help you with using the Behaviors correctly, though:
You create the attribute Behaviors you want. Obviously you have done this already.
You create a Behavior for each Behavior type you have made named "Add 1 point in <Behavior Name>".
In the "Add" Behaviors set "Stats - Maximum Stack Count" and "Stats - Maximum Stack Count Per Caster" to 99999.
Double-click on "Behavior - Modification +". In the window popping up click the Behavior tab. Under "Attribute Changes" (first entity) add the respective attribute base type (NOT the "Add" Behaviors) and set "Points" to 1.
The number of Behavior (buff) stacks on unit now determines the amount of points in a specific attribute. And even though I named it "Add..." you can also use this Behavior for removing attribute points by simply reducing the stack count on the unit.
The buffs was where I gave up. From my understanding, applying a buff repeatedly does nothing, only the first time. I tried using the Add 1 (Buff) to (unit) trigger, but it only applied once, no matter how many times I activated it. Do the buffs have to have a certain setting to allow them to stack?
Seems like you're asking for a quick escape route. Do you have any good reasons for not using Behaviors. Not spending more than 20 minutes on figuring it out doesn't count as a "good reason". ;)
I'll help you with using the Behaviors correctly, though:
You create the attribute Behaviors you want. Obviously you have done this already.
You create a Behavior for each Behavior type you have made named "Add 1 point in <Behavior Name>".
In the "Add" Behaviors set "Stats - Maximum Stack Count" and "Stats - Maximum Stack Count Per Caster" to 99999.
Double-click on "Behavior - Modification +". In the window popping up click the Behavior tab. Under "Attribute Changes" (first entity) add the respective attribute base type (NOT the "Add" Behaviors) and set "Points" to 1.
The number of Behavior (buff) stacks on unit now determines the amount of points in a specific attribute. And even though I named it "Add..." you can also use this Behavior for removing attribute points by simply reducing the stack count on the unit.
Good luck :)
Setting stack count to -1 works better. It makes it not have a max count. Setting to 99999 means it is possible to get to that level.
I'm trying to create some custom unit attributes (for a large number of units), but I need to be able to modify them. Using behaviors has really gotten me nowhere as you can't seem to modify their values on the fly without massive amounts of pre-set values. Is there any way to create attributes (just a set of numbers on each unit) without using behaviors?
@KrayzBlu: Go
Seems like you're asking for a quick escape route. Do you have any good reasons for not using Behaviors. Not spending more than 20 minutes on figuring it out doesn't count as a "good reason". ;)
I'll help you with using the Behaviors correctly, though:
The number of Behavior (buff) stacks on unit now determines the amount of points in a specific attribute. And even though I named it "Add..." you can also use this Behavior for removing attribute points by simply reducing the stack count on the unit.
Good luck :)
@Kafoso: Go
The buffs was where I gave up. From my understanding, applying a buff repeatedly does nothing, only the first time. I tried using the Add 1 (Buff) to (unit) trigger, but it only applied once, no matter how many times I activated it. Do the buffs have to have a certain setting to allow them to stack?
@KrayzBlu: Go
Stats - Maximum Stack Count
Setting stack count to -1 works better. It makes it not have a max count. Setting to 99999 means it is possible to get to that level.
@7MM3: Go
Thanks
@wOlfLisK: Go
True that.