Hi, in my map I have a custom build ability used for a Drop Pod training method (similar to Warp Train but I didn't want to use that as I didn't want the Warp Gate button) on the Barracks.
However, this is only meant to be available if you have an Orbital Command, but for some reason the Button for opening the Drop submenu refuses to pay any attention to requirements. I have tried setting the requirement on the unit's command card and on the ability itself, and a combination of the two yet it still pays no attention :( what's stranger is the requirements for units you can drop in work. I know I could make all the units also require an Orbital Command, but I'd much rather have the ability to disable or hide the Submenu's button itself.
Anyone got any ideas why it is ignoring the requirement field?
The only way to affect the button of the submenu is to affect all ability commands within the submenu. You might also have to check the "Submenu Full Validation" flag for the submenu button
Dang. Oh and I did check that box but sadly it did not apply the requirement to the submenu button.
Thanks anyway :) guess I'll try and figure out a workaround... wonder if I could make a dummy button on the same space appear like a Disabled button? Hmmm *makes mental note*
So... this afternoon while testing something else in my map I noticed the menu is now obeying the requirement. Not idea what if anything I did to fix it or if Blizz fixed it so build menus will obey requirements. Either way I'm not complaining :)
Would appear to be, just wish I knew what I did (if it was me and not Blizz patching stuff) that solved it. So yeah feel free to lock the thread please :) thanks
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Hi, in my map I have a custom build ability used for a Drop Pod training method (similar to Warp Train but I didn't want to use that as I didn't want the Warp Gate button) on the Barracks.
However, this is only meant to be available if you have an Orbital Command, but for some reason the Button for opening the Drop submenu refuses to pay any attention to requirements. I have tried setting the requirement on the unit's command card and on the ability itself, and a combination of the two yet it still pays no attention :( what's stranger is the requirements for units you can drop in work. I know I could make all the units also require an Orbital Command, but I'd much rather have the ability to disable or hide the Submenu's button itself.
Anyone got any ideas why it is ignoring the requirement field?
Thanks
@Kanitala: Go
Any ideas?
The only way to affect the button of the submenu is to affect all ability commands within the submenu. You might also have to check the "Submenu Full Validation" flag for the submenu button
@Kueken531: Go
Dang. Oh and I did check that box but sadly it did not apply the requirement to the submenu button.
Thanks anyway :) guess I'll try and figure out a workaround... wonder if I could make a dummy button on the same space appear like a Disabled button? Hmmm *makes mental note*
You mean appear over the submenu and have a texture that looks grey? Might work.
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
@DrSuperEvil: Go
So... this afternoon while testing something else in my map I noticed the menu is now obeying the requirement. Not idea what if anything I did to fix it or if Blizz fixed it so build menus will obey requirements. Either way I'm not complaining :)
So Solved?
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
@DrSuperEvil: Go
Would appear to be, just wish I knew what I did (if it was me and not Blizz patching stuff) that solved it. So yeah feel free to lock the thread please :) thanks