Event - Button pressed bug

[M0RT]

This event fires every time player presses the button, even if he doesn't fulfill requirement (and therefore the button is greyed out). I don't know if it is a bug or intension, but I see no point in detecting failed button presses. Also, there seems to be no way of detecting whether the "press" was successful or not.

What I actually needed was to detect button press on "change command card" buttons, this seems to be the only way, or is there some other?

 

[Muhahahahaaa]

i could offer you a workaround.
don't use command cards, use different units which morph into each other. means the button for a submenu(commandcards) would be a morph skill which can be easily detected by trigger.

 

[M0RT]

Thanks, but that seems like a lot of work, considering I will need this same functionality for a couple of units, it would be a nightmare.
Unless... I have a couple of "basic" units that morph into the same set of secondary units, just without changing actor. The only problem would be how to morph back into the specific unit.

EDIT: I reported this bug, along with panels crash on battle.net forums, so there is a slight chance someone will notice it.

 

[Muhahahahaaa]

depends on the submenu function, some submenus automaticlly close after using a skill, so you make the unit morph back by trigger else use the cancel button of submenues as morph back button.

 

[M0RT]

The problem is that it would need some sort of general morph back, to whatever the unit was before, and I don't know if it is possible. Otherwise I would need to create a set of abilities, one for each base unit, and somehow determine which one to show.

 

[Muhahahahaaa]

since you can give every unit endless skills and they are not shown to the user at all it doesn't matter.
you could save which unit it was before in a custom value for example.

 

[M0RT]

Yeah if i used triggers to disable/enable the correct "cancel button" it might work... but still, a lot of work for a little effect.. I think I'll just wait for the next patch, hoping they will fix it.

 

[Muhahahahaaa]

not really much work since you dont need new actors for the units
the triggering is done quite fast aswell, done in 2 hours.

 

[Dr Super Good]

You need to write your own validation check. If a button is disabled you can set a flag (boolean) and use a condition to make sure the button will not run anything.

You have to do this anyway as hackers can send button press orders at any time even if the button should not be pressable (but exists). A lot of SC2 maps suffer from this and is proved by how you can trigger a button multiple times by pressing fast (due to lag) even though the action makes the button dissapear from screen.