Well, this would be rediculuously easy if you just wanted to increase its damage/health/shields by a flat amount each kill. But since you want %s, thats a whole different ball game, primarily because behaviors stack multiplicatively not additively. The trigger you mentioned would be simple:
Event: Unit Property Changes: Kills change.
Action: Add 1 Behavior to Triggering Unit
Where Behavior is a stackable Buff Type behavior that would increase damage/health/shields. The problem I mentioned now becomes apparent; if you want it to be % based and you want it to stack additively, i.e. 1 stack is 1%, 2 stacks is 2% etc you will have to make a behavior for every % and have the trigger remove the previous behavior and add the next one. Otherwise, if you want it to just increase by a flat amount, say, 1 damage, 10 hp and 10 shields then the trigger I mentioned above will work just fine.
EDIT: Also, this should be in the trigger forum not here.
I wanted to try out a simple trigger but I do not know the sc2 trigger syntax well enough to make it.
If a unit gets a kill then increase it's damage/health/shields/Yscale 1%
Would anyone care to explain how to do this?
@ceefa: Go
Well, this would be rediculuously easy if you just wanted to increase its damage/health/shields by a flat amount each kill. But since you want %s, thats a whole different ball game, primarily because behaviors stack multiplicatively not additively. The trigger you mentioned would be simple:
Event: Unit Property Changes: Kills change. Action: Add 1 Behavior to Triggering Unit
Where Behavior is a stackable Buff Type behavior that would increase damage/health/shields. The problem I mentioned now becomes apparent; if you want it to be % based and you want it to stack additively, i.e. 1 stack is 1%, 2 stacks is 2% etc you will have to make a behavior for every % and have the trigger remove the previous behavior and add the next one. Otherwise, if you want it to just increase by a flat amount, say, 1 damage, 10 hp and 10 shields then the trigger I mentioned above will work just fine.
EDIT: Also, this should be in the trigger forum not here.
@peranzormal: Go
Thanks for the quick response and for pointing me toward the right forum