Behavior: my veterancy behavior
compare: equal to
unit: caster
value: 1
Used as validator on a morph ability (autocast validator as well as validator array) that is supposed to instantly (autocast) morph the unit into another type as soon as it reaches level 1.
But, well, as expected, that just doesn't work.
Depending on the validator settings, the unit either morphs the very second it enters the map, or it never ever even thinks about morphing.
My current conclusion is that that validator type it broken and, instead of counting the level, it only "counts" (as yes / no) whether or not the unit has that behavior.
Of course, I'm probably wrong.
Any help?
Edit:
After setting it to "not equal to 1" it works???
Which is... great? I guess. But why?
Im not quite sure why it is but sometimes when I am working on a map it has the validators backwards, so instead of it having to be true, it has to be false or the other way around.
Well, there's also some stuff on behaviors like "this behavior won't be disabled if this vlalidator doesn't return false".
Good luck figuring it out.
And that's for the things with help text.
And, yes, later on that same unit, at a higher level, morphs one more time.
Sure enough, with the same idea that not testing for the wrong level won't do it... works just fine with a similar condition.
If you want to count veterancy levels for a morph, just use the automatic flag and give it a requirement that counts the levels (same as learning abilites level skipping). For testing if the validator works, just have a buff that adds +1 to the max shield via the Unit - Modification - Vital Max Bonus field and the validator under disable.
Behavior: my veterancy behavior
compare: equal to
unit: caster
value: 1
Used as validator on a morph ability (autocast validator as well as validator array) that is supposed to instantly (autocast) morph the unit into another type as soon as it reaches level 1.
But, well, as expected, that just doesn't work.
Depending on the validator settings, the unit either morphs the very second it enters the map, or it never ever even thinks about morphing.
My current conclusion is that that validator type it broken and, instead of counting the level, it only "counts" (as yes / no) whether or not the unit has that behavior.
Of course, I'm probably wrong.
Any help?
Edit:
After setting it to "not equal to 1" it works???
Which is... great? I guess. But why?
@celerisk: Go
Im not quite sure why it is but sometimes when I am working on a map it has the validators backwards, so instead of it having to be true, it has to be false or the other way around.
Well, there's also some stuff on behaviors like "this behavior won't be disabled if this vlalidator doesn't return false".
Good luck figuring it out.
And that's for the things with help text.
And, yes, later on that same unit, at a higher level, morphs one more time.
Sure enough, with the same idea that not testing for the wrong level won't do it... works just fine with a similar condition.
Let's just hope Blizzard will never "fix" that.
If you want to count veterancy levels for a morph, just use the automatic flag and give it a requirement that counts the levels (same as learning abilites level skipping). For testing if the validator works, just have a buff that adds +1 to the max shield via the Unit - Modification - Vital Max Bonus field and the validator under disable.
Contribute to the wiki (Wiki button at top of page) Considered easy altering of the unit textures?
https://www.sc2mapster.com/forums/resources/tutorials/179654-data-actor-events-message-texture-select-by-id
https://media.forgecdn.net/attachments/187/40/Screenshot2011-04-17_09_16_21.jpg