Is there a way to make a button "un-clickable"

[TheFailTrain]

I was just wondering if it is possible to disable a button to make it "un-clickable" for a set duration of time. While working on my click macros I had an idea for an addon that would disable buttons for a set duration of time and then enable them again. Basically you could have a spam macro that was:

/click button1
/click button2
/click button3

Once button1 was clicked it would disable (for the duration of a cooldown) and then enable when that cooldown was up. I have been looking around but I can't seem to find an answer on if its possible to make a button "un-clickable".

[Allestaria]

LOl I know a not so good way to do it..

Write a macro something like /castsequance reset=15 Frostbolt, fostbolt.

Miss spell the second command. It will reset in 15 seconds but the key will become useless because of the miss spelled command.
You will see the red ? until it resets.

I know I know.. poor way of taking a mistake and turn it into what you actually want without another addon to do so!

[Solon]

I feel that this would step beyond the boundaries into automation. I wouldn't use it. Neat idea to get around the spirit of the rules though.

/castsequence reset=15 Frostbolt, fostbolt

This would not provide any benefit to a spam macro at all. The 15 seconds for reset requires you to not trigger, click, or /click call the macro for 15 seconds.

[Ualaa]

I know I can enable/disable mapped keys in IS Boxer.

So we could have a "spam" mapped key/macro basically.
On each step (successive spam) it will hit/activate other mapped keys.
So you might have the spam key, hit three different mapped keys in succession.

And then you can have another mapped key, toggle any of these clicked keys on and off.
While the mapped key is on, its hotkey will activate it.
When it is disabled, pressing the hotkey will not do anything, it acts as if it were a destroyed macro.
I was using the toggling of mapped keys, for Eclipse Procs.

I'm not sure that you'd want to disable/enable a given key for "x" seconds.
Well, if you have a toggle which you control yourself, and use a countdown etc, that is fine.
But if you want the software to do the timing for you, not sure you want to go down that route.

[Ughmahedhurtz]

I feel that this would step beyond the boundaries into automation. I wouldn't use it. Neat idea to get around the spirit of the rules though.

This. What you're talking about would very definitely be considered an exploit by Blizzard if you could even do it.

[Allestaria]

I'm not sure what you all are talking about. But making a cast sequance macro is nothing new. And is used by more people then you know.

The reset time is nothing new either. Like a lot have said. If blizzard doesn't want it they wouldn't allow it.
Misspelling a word is not a huge thing.
If you are focusing on the reset time. that can be changed to target/combat. Or would you say that is not right either? Because if that is the case a LOT of people are breaking the rules.
There is no automation either.
Doing a reset timer is not automation. I have been using a reset time for 2 years now. Its not any different then putting in target/combat.
If blizzard didn't allow it it wouldn't be useable.

[Khatovar]

But what you are talking about will not work for what the OP wants and does not work the way you believe it does. As Solon says, reset=15 will not make the macro reset after 15 seconds no matter what. It will make the macro lock up on an invalid spell {just like using Nill, or Null} until you STOP trying to trigger the macro in any way shape or form for 15 seconds.

You cannot ask the game to make if-then decisions, such as "If this spell is on cooldown, then make this button unclickable." You cannot ask the game to make decisions, such as "enable/disable this action every x seconds". They must be actions you make yourself and trigger manually, as Ualaa does with Keymap toggles.

If the OP wants to block a spell until the cooldown is up, then they should use commas for general timing or manual toggles.

[Ughmahedhurtz]

I'm not sure what you all are talking about. But making a cast sequance macro is nothing new. And is used by more people then you know.

The reset time is nothing new either. Like a lot have said. If blizzard doesn't want it they wouldn't allow it.
Misspelling a word is not a huge thing.
If you are focusing on the reset time. that can be changed to target/combat. Or would you say that is not right either? Because if that is the case a LOT of people are breaking the rules.
There is no automation either.
Doing a reset timer is not automation. I have been using a reset time for 2 years now. Its not any different then putting in target/combat.
If blizzard didn't allow it it wouldn't be useable.

Read the original post again. Adding arbitrary delays to a button to get around a mechanic that was specifically disabled a couple of patches ago to prevent this exact behavior is just about the best example of an exploit I've seen recently. You might get away without a ban when they fix it (assuming it is even possible to do the Disable_Button_For_X_Seconds thing in an addon) but I would advise against risking all your accounts on Blizzard's forbearance.

[Allestaria]

You all take things way to serious. Take a chill pill and see what is ment to be a opps I screwed up on a spelling and found out what happens.

[Khatovar]

What, exactly, is "too serious" about keeping what we do legit and giving out valid information on how things work?