If you repeatedly hide an ability, you need to show it just as many times for it to show back up again. i.e. take a queen and hide transfusion via triggers twice, then show it once - it won't be on the command card ... if you show it once more it will show up again. I've submitted a broken map example :)
Why are you hiding and showing abilities with trigger? You should be doing this from the command card properties or the ability or the button for the ability.
you can apply dummy behaviors to units and use this dummy behavor to control whether or not to show the ability
basically set the ability up so its hidden when the dummy behavior is on the unit.
Rollback Post to RevisionRollBack
Skype
KageNinpo = SN
My Libraries
DialogLeaderboard & TeamSort
My Projects
SPACEWAR Tribute
Infinite TD
Because dummy behaviours require quite a bit more data entry than a simple abstract trigger. With a trigger I have the code right in front of me cleanly laid out vs a tangled web of data that does the same thing ;)
Also note that the hidden abilities are highly dependant on units stored in variables so it's not a simple native data toggling or anything
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
If you repeatedly hide an ability, you need to show it just as many times for it to show back up again. i.e. take a queen and hide transfusion via triggers twice, then show it once - it won't be on the command card ... if you show it once more it will show up again. I've submitted a broken map example :)
I wonder, if its intended that way, I had trouble with this in the past, but it can easily make right with some additional triggering.
Why are you hiding and showing abilities with trigger? You should be doing this from the command card properties or the ability or the button for the ability.
you can apply dummy behaviors to units and use this dummy behavor to control whether or not to show the ability
basically set the ability up so its hidden when the dummy behavior is on the unit.
@SouLCarveRR: Go I had problems with that too and even with this bug its easier just make that trigger.
@SouLCarveRR: Go
Because dummy behaviours require quite a bit more data entry than a simple abstract trigger. With a trigger I have the code right in front of me cleanly laid out vs a tangled web of data that does the same thing ;)
Also note that the hidden abilities are highly dependant on units stored in variables so it's not a simple native data toggling or anything